- Pharo-users - lists.pharo.org

Re: [Pharo-users] code formatting... adjust the formatting?

by sergio_101

awesome! thanks! On Thu, Jan 2, 2014 at 2:56 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > On 02 Jan 2014, at 19:49, sergio_101 <sergio.rrd(a)gmail.com> wrote: > > i accidentally posted this to the seaside group, so now i am posting it > back here to pharo.. > > i am currently using the code formatting in the browser in pharo 2.0... > > it seems to be a lot more aggressive than it has been in the past.. > > for instance, this: > > > gets formatted to: > > html anchor > url: '#'; > with: 'random link'. > > is there any way to: > > 1. keep the browser from splitting the call into multiple lines? > 2. narrow down the amount of spaces that make up a tab? > > Hello! > > There are actually 3 implementation for a code formatter in Pharo2â¦ this > means > it is a bit random which is used ;-) > > But Nautilus uses explicitly the selected formatter in the settings from > RB. > (In Pharo 1.4 it might have been the one of the old AST or the > non-configurable oneâ¦) > > (And, yes, itâs a *dumb* idea to have 3 implementations of anythingâ¦ > therefore, in Pharo3, > there is just oneâ¦) > > So: In the settings for âRefactoring Engineâ there is a sub-category > âConfigurable Formatterâ > > deselect > > New line after cascade > and > New line before first cascade > > â> formats without the multiple lines. > > The tab size is not changeableâ¦ that would be a general editor setting > which does not exist yet, > as far as I know. > > Marcus > > -- ---- peace, sergio photographer, journalist, visionary #BitMessage BM-2D8VWUJSS41RFKh1ec83preVabHrnniExa http://www.ThoseOptimizeGuys.com http://www.CodingForHire.com http://www.coffee-black.com http://www.painlessfrugality.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

Jan. 2, 2014

Re: [Pharo-users] code formatting... adjust the formatting?

by Marcus Denker

On 02 Jan 2014, at 19:49, sergio_101 <sergio.rrd(a)gmail.com> wrote: > i accidentally posted this to the seaside group, so now i am posting it back here to pharo.. > > i am currently using the code formatting in the browser in pharo 2.0... > > it seems to be a lot more aggressive than it has been in the past.. > > for instance, this: > > > gets formatted to: > > html anchor > url: '#'; > with: 'random link'. > > is there any way to: > > 1. keep the browser from splitting the call into multiple lines? > 2. narrow down the amount of spaces that make up a tab? > Hello! There are actually 3 implementation for a code formatter in Pharo2â¦ this means it is a bit random which is used ;-) But Nautilus uses explicitly the selected formatter in the settings from RB. (In Pharo 1.4 it might have been the one of the old AST or the non-configurable oneâ¦) (And, yes, itâs a *dumb* idea to have 3 implementations of anythingâ¦ therefore, in Pharo3, there is just oneâ¦) So: In the settings for âRefactoring Engineâ there is a sub-category âConfigurable Formatterâ deselect New line after cascade and New line before first cascade â> formats without the multiple lines. The tab size is not changeableâ¦ that would be a general editor setting which does not exist yet, as far as I know. Marcus

Jan. 2, 2014

code formatting... adjust the formatting?

by sergio_101

i accidentally posted this to the seaside group, so now i am posting it back here to pharo.. i am currently using the code formatting in the browser in pharo 2.0... it seems to be a lot more aggressive than it has been in the past.. for instance, this: html anchor url: '#'; with: 'random link'. gets formatted to: html anchor url: '#'; with: 'random link'. is there any way to: 1. keep the browser from splitting the call into multiple lines? 2. narrow down the amount of spaces that make up a tab? thanks! -- ---- peace, sergio photographer, journalist, visionary #BitMessage BM-2D8VWUJSS41RFKh1ec83preVabHrnniExa http://www.ThoseOptimizeGuys.com http://www.CodingForHire.com http://www.coffee-black.com http://www.painlessfrugality.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

Jan. 2, 2014

Re: [Pharo-users] Pharo private develoment

by Hilaire Fernandes

Le 02/01/2014 12:25, Norbert Hartl a Ã©crit : >> >> I use filetree and bitbucket for my private projects, and I use also >> metacello to build with them. > > I still didnât find the time to look into filetree. It is yet another > thing to learn. Can you commit to bitbucket from within pharo? And I use > metacello, too, for building my projects. > Out of curiosity I took a look at the Dale Filetree presentation slides: it is very neat. It recalls me years ago Free software hackers were complaining the source code was not easily visible from Squeak/Smalltalk. At least it is not the case anymore. -- Dr. Geo http://drgeo.eu

Jan. 2, 2014

FW: New in Graph-ET

by Daniel Aviv Notario

Fowarding what I posted on Pharo-devCheers! :-) From: daniel_avivnotario(a)hotmail.com To: moose-dev(a)iam.unibe.ch; pharo-dev(a)lists.pharo.org Subject: New in Graph-ET Date: Thu, 2 Jan 2014 11:40:40 -0300 Hi guys! It's been a while since I posted in this list. The reason why I'm posting is because I finally finished my exams (yay!) and now I have some time to spare developing Graph-ET. I noticed a lot of you have been trying it, thank you for that :) I will try and answer all your questions regarding Graph-ET in the next few days. Meanwhile, today I did a little work on Scatterplots, you can go play with that, here's an example for you: | diag col | col := OrderedCollection new. col add: (1@1). col add: (1@2). col add: (2@1). col add: (2@2). col add: (0.75(a)0.5) col add: (0.6(a)1.5) diag := GETDiagramBuilder new. (diag scatterplot) models: col; x: [ :mod | mod x ]; y: [ :mod | mod y ]; regularAxis. diag open It's really pretty basic, I think changing the size and shape of he object should be nice. In ESUG I was working in animations, but I dropped it, I'll try again soon, but not inmediatly. Other things I think I'll work is improving the axis values in the labels and various customizations and bug-fixing. Also, I would like to hear from you, what can I work on? I been recieving a lot of suggestions, and I'm glad. So if you have a request, doubt, complaint, comments or anything really you can contact me and I'll try and answer ASAP. Hope hearing from you!Daniel

Jan. 2, 2014

FW: Graph-ET Examples on Facebook

by Daniel Aviv Notario

Fowarding what I posted on Pharo-dev Cheers! :-) From: daniel_avivnotario(a)hotmail.com To: moose-dev(a)iam.unibe.ch; pharo-dev(a)lists.pharo.org Subject: Graph-ET Examples on Facebook Date: Thu, 2 Jan 2014 11:30:30 -0300 Hi! Weâve just put online some example about GraphET. GraphET is about drawing charts, graphs and histograms. It is built on top of Roassal, to let the user enjoy all the different interaction with the visualization. GraphET may be loaded using the following incantation: Gofer new smalltalkhubUser: 'ObjectProfile' project: 'GraphET'; package: 'ConfigurationOfGraphET'; load. (Smalltalk at: #ConfigurationOfGraphET) loadDevelopment https://www.facebook.com/media/set/?set=a.566523986767536.1073741839.340543… Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 2, 2014

Re: [Pharo-users] Pharo private develoment

by Benjamin

Smalltalkhub private project or bitbucket And I deployed my own Jenkins. Itâs as complicated as `sudo apt-get install jenkins` Ben On 01 Jan 2014, at 19:26, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > Pharo as a community has support to use its CI server, among other > goodies such as SmalltalkHub. > > But what if your code is not public and you want to have a central > repository and continuous builds? > > Has anybody ever wrote a guide to develop with Pharo in the context of > private development? > > So far I managed to work with a file based repo and a set of > workspaces to create a new working image or to prepare it for > deployment. But I want to automate it as much as I can. > > Regards! > > Esteban A. Maringolo >

Jan. 2, 2014

Re: [Pharo-users] Pharo private develoment

by Esteban Lorenzano

On 02 Jan 2014, at 13:42, Norbert Hartl <norbert(a)hartl.name> wrote: > > Am 02.01.2014 um 13:22 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > >> >> On 02 Jan 2014, at 12:25, Norbert Hartl <norbert(a)hartl.name> wrote: >> >>> >>> Am 02.01.2014 um 11:57 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: >>> >>>> >>>> On 02 Jan 2014, at 11:49, Norbert Hartl <norbert(a)hartl.name> wrote: >>>> >>>>> >>>>> Am 01.01.2014 um 19:26 schrieb Esteban A. Maringolo <emaringolo(a)gmail.com>: >>>>> >>>>>> Pharo as a community has support to use its CI server, among other >>>>>> goodies such as SmalltalkHub. >>>>>> >>>>>> But what if your code is not public and you want to have a central >>>>>> repository and continuous builds? >>>>>> >>>>>> Has anybody ever wrote a guide to develop with Pharo in the context of >>>>>> private development? >>>>>> >>>>>> So far I managed to work with a file based repo and a set of >>>>>> workspaces to create a new working image or to prepare it for >>>>>> deployment. But I want to automate it as much as I can. >>>>>> >>>>> I do what you want to do. I have a central server that I use for code storage and for the CI builds. Have a look at [1]. There you can read how you can easily create a http repository for monticello. I just create sub directories for every project on my server and the rest just works. >>>>> The next step would be to install jenkins and add [2]. The jenkins server then just uses the http repository you created before. >>>>> If you need help on this just ask. >>>> >>>> I use filetree and bitbucket for my private projects, and I use also metacello to build with them. >>> >>> I still didnât find the time to look into filetree. It is yet another thing to learn. Can you commit to bitbucket from within pharo? And I use metacello, too, for building my projects. >> >> is just another mc repository type, so no need to learn much. >> but you have a second step, because you do your âcommitsâ to a local repository, then you do the actual commit/push using source tree or command line. Is a bit annoying, but wellâ¦ at least all the authorisation stuff is made by others :) >> also, Thierry is doing gitfiletree so it will be better soon :) > > So, good to wait and use other stuff, hehe :) > >> >>> >>>> if you do not want to use file tree format, you can use ftp or even dropbox :) >>> >>> That might raise some difficulties integrating that into a jenkins setup. And to be honest I would avoid FTP where possible, there are other caveates with it and it has no advantage over http. >> >> I worked with ftp without any problem. Anyway, itâs your choice :) >> >>> >>>> there is no need to make anything different on your private development than you do in your public ones. >>>> >>> It would be good if that would be the case. But all things that are public accessible are not necessarily accessible in a private context. You chose bitbucket which offers private repos. I chose to install my own WebDAV server for mimicking the same. But that doesnât work in all the contextes someone might work in. >> >> like what? using filetree you delegate the authentication problemsâ¦ so if you can reach the place from command line, you avoid the problem at zero cost. >> > How do you give your jenkins server permission to get the sources from bitbucket. Having passwords for bitbucket or store the key somewhere on a server? you generate a credential in jenkins, and upload it to bitbucket >>> >>>> ah, and scripts from Lukas are very outdated (I mean, a LOT). >>>> is a lot easier to take http://ci.inria.fr/pharo-contribution (any job there) as an example on how to configure a jenkins job in few lines. >>>> >>> Well, then I want to let you know that Iâm using those scripts happily for years. What do I get from upgrading? I donât care about a few lines because I have my workflow. Having the doubled amount of lines doesnât make it worse. >> >> Maybe. People was using happily lots of things for years, yet things change. Improvement does not means always âold does not workâ, sometimes is ânewer is betterâ. >> New process is a lot simpler and does not require any external scriptâ¦ >> >> New process you just need to do: >> >> wget --quiet -O - get.pharo.org/30+vm | bash >> ./pharo Pharo.image config http://www.smalltalkhub.com/mc/Pier/Pier3/main ConfigurationOfPier3 --install=$VERSION --group=Tests >> ./pharo $JOB_NAME.image test --junit-xml-output "Pier.*" >> >> to install a configuration and run the testsâ¦ you cannot tell me that this is not an improvement, even if you already know how to use the older scripts. >> > I canât see what it does different to my approach. Donât get me wrong I like it when things become easier. But Iâm also in the need to plan the time to invest. I have a workflow and I cannot see anything that is better in your approach. So why invest the time and risk something not working? To me this is more like "if it ain't broke don't fix itâ. > But you are right, taking Estebans view it wouldnât be a good idea to learn an older workflow if a newer and easier is in place. thatâs my point :) > > Norbert > >>> >>> So I read his inquiry that he is willing to build his on stuff. The apache config in my post is nearly a drop-in solution. Having that you just use monticello as you (most likely) always did. Having an CI server on your own machine (easy to install) gives you the control you need and you can skip authorization settings between http repo and jenkins server which makes not only building easier but also publishing results without having the need to go over them and remove all sensible data. I would be glad if you would describe a private development workflow in detail. Without that it is hard to spot the drawbacks in your approach ;) >>> >>> Norbert >>> >>> >>>>> >>>>> Norbert >>>>> >>>>> [1] http://norbert.hartl.name/blog/2009/06/08/public-monticello-repository/ >>>>> [2] https://github.com/renggli/builder

Jan. 2, 2014

Re: [Pharo-users] Pharo private develoment

by Norbert Hartl

Am 02.01.2014 um 13:22 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > > On 02 Jan 2014, at 12:25, Norbert Hartl <norbert(a)hartl.name> wrote: > >> >> Am 02.01.2014 um 11:57 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: >> >>> >>> On 02 Jan 2014, at 11:49, Norbert Hartl <norbert(a)hartl.name> wrote: >>> >>>> >>>> Am 01.01.2014 um 19:26 schrieb Esteban A. Maringolo <emaringolo(a)gmail.com>: >>>> >>>>> Pharo as a community has support to use its CI server, among other >>>>> goodies such as SmalltalkHub. >>>>> >>>>> But what if your code is not public and you want to have a central >>>>> repository and continuous builds? >>>>> >>>>> Has anybody ever wrote a guide to develop with Pharo in the context of >>>>> private development? >>>>> >>>>> So far I managed to work with a file based repo and a set of >>>>> workspaces to create a new working image or to prepare it for >>>>> deployment. But I want to automate it as much as I can. >>>>> >>>> I do what you want to do. I have a central server that I use for code storage and for the CI builds. Have a look at [1]. There you can read how you can easily create a http repository for monticello. I just create sub directories for every project on my server and the rest just works. >>>> The next step would be to install jenkins and add [2]. The jenkins server then just uses the http repository you created before. >>>> If you need help on this just ask. >>> >>> I use filetree and bitbucket for my private projects, and I use also metacello to build with them. >> >> I still didnât find the time to look into filetree. It is yet another thing to learn. Can you commit to bitbucket from within pharo? And I use metacello, too, for building my projects. > > is just another mc repository type, so no need to learn much. > but you have a second step, because you do your âcommitsâ to a local repository, then you do the actual commit/push using source tree or command line. Is a bit annoying, but wellâ¦ at least all the authorisation stuff is made by others :) > also, Thierry is doing gitfiletree so it will be better soon :) So, good to wait and use other stuff, hehe :) > >> >>> if you do not want to use file tree format, you can use ftp or even dropbox :) >> >> That might raise some difficulties integrating that into a jenkins setup. And to be honest I would avoid FTP where possible, there are other caveates with it and it has no advantage over http. > > I worked with ftp without any problem. Anyway, itâs your choice :) > >> >>> there is no need to make anything different on your private development than you do in your public ones. >>> >> It would be good if that would be the case. But all things that are public accessible are not necessarily accessible in a private context. You chose bitbucket which offers private repos. I chose to install my own WebDAV server for mimicking the same. But that doesnât work in all the contextes someone might work in. > > like what? using filetree you delegate the authentication problemsâ¦ so if you can reach the place from command line, you avoid the problem at zero cost. > How do you give your jenkins server permission to get the sources from bitbucket. Having passwords for bitbucket or store the key somewhere on a server? >> >>> ah, and scripts from Lukas are very outdated (I mean, a LOT). >>> is a lot easier to take http://ci.inria.fr/pharo-contribution (any job there) as an example on how to configure a jenkins job in few lines. >>> >> Well, then I want to let you know that Iâm using those scripts happily for years. What do I get from upgrading? I donât care about a few lines because I have my workflow. Having the doubled amount of lines doesnât make it worse. > > Maybe. People was using happily lots of things for years, yet things change. Improvement does not means always âold does not workâ, sometimes is ânewer is betterâ. > New process is a lot simpler and does not require any external scriptâ¦ > > New process you just need to do: > > wget --quiet -O - get.pharo.org/30+vm | bash > ./pharo Pharo.image config http://www.smalltalkhub.com/mc/Pier/Pier3/main ConfigurationOfPier3 --install=$VERSION --group=Tests > ./pharo $JOB_NAME.image test --junit-xml-output "Pier.*" > > to install a configuration and run the testsâ¦ you cannot tell me that this is not an improvement, even if you already know how to use the older scripts. > I canât see what it does different to my approach. Donât get me wrong I like it when things become easier. But Iâm also in the need to plan the time to invest. I have a workflow and I cannot see anything that is better in your approach. So why invest the time and risk something not working? To me this is more like "if it ain't broke don't fix itâ. But you are right, taking Estebans view it wouldnât be a good idea to learn an older workflow if a newer and easier is in place. Norbert >> >> So I read his inquiry that he is willing to build his on stuff. The apache config in my post is nearly a drop-in solution. Having that you just use monticello as you (most likely) always did. Having an CI server on your own machine (easy to install) gives you the control you need and you can skip authorization settings between http repo and jenkins server which makes not only building easier but also publishing results without having the need to go over them and remove all sensible data. I would be glad if you would describe a private development workflow in detail. Without that it is hard to spot the drawbacks in your approach ;) >> >> Norbert >> >> >>>> >>>> Norbert >>>> >>>> [1] http://norbert.hartl.name/blog/2009/06/08/public-monticello-repository/ >>>> [2] https://github.com/renggli/builder

Jan. 2, 2014

Re: [Pharo-users] Pharo private develoment

by Esteban Lorenzano

On 02 Jan 2014, at 12:25, Norbert Hartl <norbert(a)hartl.name> wrote: > > Am 02.01.2014 um 11:57 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > >> >> On 02 Jan 2014, at 11:49, Norbert Hartl <norbert(a)hartl.name> wrote: >> >>> >>> Am 01.01.2014 um 19:26 schrieb Esteban A. Maringolo <emaringolo(a)gmail.com>: >>> >>>> Pharo as a community has support to use its CI server, among other >>>> goodies such as SmalltalkHub. >>>> >>>> But what if your code is not public and you want to have a central >>>> repository and continuous builds? >>>> >>>> Has anybody ever wrote a guide to develop with Pharo in the context of >>>> private development? >>>> >>>> So far I managed to work with a file based repo and a set of >>>> workspaces to create a new working image or to prepare it for >>>> deployment. But I want to automate it as much as I can. >>>> >>> I do what you want to do. I have a central server that I use for code storage and for the CI builds. Have a look at [1]. There you can read how you can easily create a http repository for monticello. I just create sub directories for every project on my server and the rest just works. >>> The next step would be to install jenkins and add [2]. The jenkins server then just uses the http repository you created before. >>> If you need help on this just ask. >> >> I use filetree and bitbucket for my private projects, and I use also metacello to build with them. > > I still didnât find the time to look into filetree. It is yet another thing to learn. Can you commit to bitbucket from within pharo? And I use metacello, too, for building my projects. is just another mc repository type, so no need to learn much. but you have a second step, because you do your âcommitsâ to a local repository, then you do the actual commit/push using source tree or command line. Is a bit annoying, but wellâ¦ at least all the authorisation stuff is made by others :) also, Thierry is doing gitfiletree so it will be better soon :) > >> if you do not want to use file tree format, you can use ftp or even dropbox :) > > That might raise some difficulties integrating that into a jenkins setup. And to be honest I would avoid FTP where possible, there are other caveates with it and it has no advantage over http. I worked with ftp without any problem. Anyway, itâs your choice :) > >> there is no need to make anything different on your private development than you do in your public ones. >> > It would be good if that would be the case. But all things that are public accessible are not necessarily accessible in a private context. You chose bitbucket which offers private repos. I chose to install my own WebDAV server for mimicking the same. But that doesnât work in all the contextes someone might work in. like what? using filetree you delegate the authentication problemsâ¦ so if you can reach the place from command line, you avoid the problem at zero cost. > >> ah, and scripts from Lukas are very outdated (I mean, a LOT). >> is a lot easier to take http://ci.inria.fr/pharo-contribution (any job there) as an example on how to configure a jenkins job in few lines. >> > Well, then I want to let you know that Iâm using those scripts happily for years. What do I get from upgrading? I donât care about a few lines because I have my workflow. Having the doubled amount of lines doesnât make it worse. Maybe. People was using happily lots of things for years, yet things change. Improvement does not means always âold does not workâ, sometimes is ânewer is betterâ. New process is a lot simpler and does not require any external scriptâ¦ New process you just need to do: wget --quiet -O - get.pharo.org/30+vm | bash ./pharo Pharo.image config http://www.smalltalkhub.com/mc/Pier/Pier3/main ConfigurationOfPier3 --install=$VERSION --group=Tests ./pharo $JOB_NAME.image test --junit-xml-output "Pier.*" to install a configuration and run the testsâ¦ you cannot tell me that this is not an improvement, even if you already know how to use the older scripts. > > So I read his inquiry that he is willing to build his on stuff. The apache config in my post is nearly a drop-in solution. Having that you just use monticello as you (most likely) always did. Having an CI server on your own machine (easy to install) gives you the control you need and you can skip authorization settings between http repo and jenkins server which makes not only building easier but also publishing results without having the need to go over them and remove all sensible data. I would be glad if you would describe a private development workflow in detail. Without that it is hard to spot the drawbacks in your approach ;) > > Norbert > > >>> >>> Norbert >>> >>> [1] http://norbert.hartl.name/blog/2009/06/08/public-monticello-repository/ >>> [2] https://github.com/renggli/builder

Jan. 2, 2014