February 2013 - Pharo-users

ESUG at Google Open Source Blog

by Carla F. Griggio

Hello everybody! Last Friday the Google Open Source Blog published a post about ESUG's GSOC 2012. Have a look! http://google-opensource.blogspot.fr/2013/02/some-small-talk-with-esug.html Congratulations once again to everybody that participated :) Cheers! Carla

Feb. 20, 2013

Re: [Pharo-users] Slices and monticello - add to package... or add package to ... ? + procedure

by Sean P. DeNigris

Thanks for updating this, phil! philippeback wrote > I was educating myself on slices. Maybe I'll be able to contribute a > bit properly one of these days. It's actually sooo easy now... much has been streamlined... philippeback wrote > All right, I can understand but this feels like unnatural to be on a > repository and ask to "Add to package..." where what I want to do is > to add the package to the repository. I agree that this part of the UI is counter-intuitive, but the good news is, you don't have to do this step for slices anymore. The inbox is added automatically. philippeback wrote > Select your package-cache repository on the right hand pane. This step is no longer necessary. philippeback wrote > You will be prompted for a log message (for each one of them ?) There's just one commit message for the whole slice. philippeback wrote > Make sure to give the number of the issue your SLICE addresses in the > comment. Interesting. I never do that. Why is it necessary? philippeback wrote > Right click the repository and select "Add to package..." (this will > associate the package to the repository). Again, not necessary. Also, why save to the package cache first? I always save directly to the inbox and I'm pretty sure is automatically saves to the cache as well... Cheers, Sean -- View this message in context: http://forum.world.st/Slices-and-monticello-add-to-package-or-add-package-t… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Feb. 19, 2013

Re: [Pharo-users] Slices and monticello - add to package... or add package to ... ? + procedure

by Camillo Bruni

thanks! I'll try to update the entry in the wiki On 2013-02-19, at 12:51, phil(a)highoctane.be wrote: > I was educating myself on slices. Maybe I'll be able to contribute a > bit properly one of these days. > > Reading from http://code.google.com/p/pharo/wiki/HowToContribute. > > Creating a slice in my own package-cache is all fine. > > Now, to add it to the PharoInbox, I watched the screencast: > http://www.pharocasts.com/2010/03/how-to-contribute-to-pharo.html > > There is this thing were we need to go to the PharoInbox repo in the > right pane on monticello. > > The right click and select the Add to package.. option and then select > the slice. > > All right, I can understand but this feels like unnatural to be on a > repository and ask to "Add to package..." where what I want to do is > to add the package to the repository. > > I understand that this is required to have the repository associated > with the package so that I can save the package to one of its > associated repositories. > > Maybe "Associate with package..." may be more helpful. > > Also the procedure on HowToContribute is not right anymore. As the UI changed. > > There is my version: > > # How to make a slice > > Slice: Your modification affect more than one package: you have to > create a SLICE package in your package cache > A SLICE is just a package with dependents ones, so you have to > indicate the dependent packages. > > ## Procedure > Open the Monticello browser. > > You should see one or more packages marked as modified (they have an > asterisk before their name). > > Select your package-cache repository on the right hand pane. > > Create the new SLICE (click on the ''+SLICE'' button) and follow the > instructions. > > > ### Old way > _Mark all_ the modified packages (the ones with asterisks before their > names) required by your SLICE package. > > To do this, right click on the SLICE package in the left pane and > select ''add required package'', then select the package from the next > menu. > > Repeat for all modified packages. (Yeah, boring) > > ### New way (Pharo 2.0 at least) > Put the issue tracker number in the Issue Number box and hit "Grab" to > get the title of the issue. > The (un)select in the list of "Dirty Packages to be included in the slice" > > ### Back to regular programming... > > Select your package-cache repository, this will enable the save button. > > Save the SLICE package (click on the ''Save'' button). > > An mcz package will be saved in your cache for the SLICE package and > all the modified packages. > (Name: something along the lines of > SLICE-Issue-XXXX-YYYY-ZZZZ-Comment-Initials.1) > > You will be prompted for a log message (for each one of them ?), type > a useful comment for the first package, (copy it and paste it on the > others - sure?). > > Make sure to give the number of the issue your SLICE addresses in the comment. > > Publish the package to PharoInbox repository. > > # Hwo to publish to the PharoInbox repository > > Open monticello. > > Select the PharoInbox repository on the right pane. > > Right click the repository and select "Add to package..." (this will > associate the package to the repository). > > You'll be presented with a list of possible packages. > > Pick up your slice. > > Then, go back to Monticello Browser with a list of packages on the > left and a list of repositories on the right. > > Select on your slice on the left. > Select the PharoInbox repository on the right. > > Click the Save button on the top bar. > > That's it, slice now in PharoInbox. > > > Phil >

Feb. 19, 2013

Re: [Pharo-users] Pharo 2 and old shortcuts

by Esteban Lorenzano

slices need to be merged, always and just the latest one, not all Esteban On Feb 19, 2013, at 3:11 PM, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > Question: should I do a Load or a Merge of such slices in Monticello? > > TIA > Phil > > 2013/2/19 Esteban Lorenzano <estebanlm(a)gmail.com>: >> slice is in inbox, I will integrate in half an hour >> >> http://code.google.com/p/pharo/issues/detail?id=7542 >> >> On Feb 19, 2013, at 2:45 PM, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> thanks! >> >> N. >> Am 19.02.2013 um 14:38 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: >> >> he, I have it... providing a fix now... >> >> On Feb 19, 2013, at 2:25 PM, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> >> Am 19.02.2013 um 14:19 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: >> >> I cannot reproduce it... did you tried in a new nautilus instance? >> >> I downloaded latest 2.0 image. I opened it, opened the Settings browser, >> searched for "old style", checked option. Closed Settings browser, opened >> over world menu a system browser, click in the left-most pane (classes), >> pressed cmd-f, typed RxMatcher, selected appearing RxMatcher in list and >> pressed enter. >> >> Norbert >> >> please, do not stay in 1.4... we need the feedback of people using 2.0 to >> improve, otherwise we will not realize what is wrong :) >> >> Esteban >> >> On Feb 19, 2013, at 2:12 PM, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> That was short time fun. If I select the "old style" option and try to find >> a class using cmd-f I get the following error >> >> <Bildschirmfoto 2013-02-19 um 14.10.24.png> >> >> Maybe I stay in 1.4 a while longerâ¦ >> >> Norbert >> >> Am 19.02.2013 um 12:44 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: >> >> ha... problem is that is not "use historical keys" (I don't know what that >> setting does, btw) >> is "Use old style keys" under Nautilus group >> >> Esteban >> >> On Feb 19, 2013, at 12:39 PM, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> >> Am 19.02.2013 um 11:59 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: >> >> which most places? >> >> >> e.g. in Nautilus with historical shortcuts on I can't click on a method and >> press cmd-n to browse senders. >> >> Norbert >> >> the new shortcuts were defined in nautilus, and the historical shortcuts are >> then targeting nautilus usage. Other places didn't change (or should not >> change) any keybinding. >> >> Esteban >> >> On Feb 19, 2013, at 11:56 AM, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> For a new project I started to use pharo 2.0. But I find it really >> cumbersome to use the new keyboard shortcuts. As long as I use 1.4 in >> parallel I don't want to switch to the new ones. I've found a setting in >> Settings named "use historical shortcuts" but it is not effective in most >> places. >> Is there a way change that? >> >> >> >> >> >> >> >> >> >> >> >> >

Feb. 19, 2013

Re: [Pharo-users] Pharo By Example 2 Book - Assembled Files in PDF form.

by Damien Cassou

On Tue, Feb 19, 2013 at 9:45 AM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > This should be made into a Jenkins job I think so that we can have the > PBE2 and other books in PDF form for easier dissemination. you are right. Here is one: https://ci.inria.fr/pharo-contribution/job/DeepIntoPharo/ the only missing piece is the automated upload to GForge (http://pharobooks.gforge.inria.fr/PharoByExampleTwo-Eng/) I'm working on it. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Feb. 19, 2013

Re: [Pharo-users] Pharo 2 and old shortcuts

by phil＠highoctane.be

Question: should I do a Load or a Merge of such slices in Monticello? TIA Phil 2013/2/19 Esteban Lorenzano <estebanlm(a)gmail.com>: > slice is in inbox, I will integrate in half an hour > > http://code.google.com/p/pharo/issues/detail?id=7542 > > On Feb 19, 2013, at 2:45 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > > thanks! > > N. > Am 19.02.2013 um 14:38 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > > he, I have it... providing a fix now... > > On Feb 19, 2013, at 2:25 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > > > Am 19.02.2013 um 14:19 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > > I cannot reproduce it... did you tried in a new nautilus instance? > > I downloaded latest 2.0 image. I opened it, opened the Settings browser, > searched for "old style", checked option. Closed Settings browser, opened > over world menu a system browser, click in the left-most pane (classes), > pressed cmd-f, typed RxMatcher, selected appearing RxMatcher in list and > pressed enter. > > Norbert > > please, do not stay in 1.4... we need the feedback of people using 2.0 to > improve, otherwise we will not realize what is wrong :) > > Esteban > > On Feb 19, 2013, at 2:12 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > > That was short time fun. If I select the "old style" option and try to find > a class using cmd-f I get the following error > > <Bildschirmfoto 2013-02-19 um 14.10.24.png> > > Maybe I stay in 1.4 a while longerâ¦ > > Norbert > > Am 19.02.2013 um 12:44 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > > ha... problem is that is not "use historical keys" (I don't know what that > setting does, btw) > is "Use old style keys" under Nautilus group > > Esteban > > On Feb 19, 2013, at 12:39 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > > > Am 19.02.2013 um 11:59 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > > which most places? > > > e.g. in Nautilus with historical shortcuts on I can't click on a method and > press cmd-n to browse senders. > > Norbert > > the new shortcuts were defined in nautilus, and the historical shortcuts are > then targeting nautilus usage. Other places didn't change (or should not > change) any keybinding. > > Esteban > > On Feb 19, 2013, at 11:56 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > > For a new project I started to use pharo 2.0. But I find it really > cumbersome to use the new keyboard shortcuts. As long as I use 1.4 in > parallel I don't want to switch to the new ones. I've found a setting in > Settings named "use historical shortcuts" but it is not effective in most > places. > Is there a way change that? > > > > > > > > > > > >

Feb. 19, 2013

Re: [Pharo-users] Pharo 2 and old shortcuts

by Norbert Hartl

It might be a good idea to open a new thread if you have a new topic to discuss. thanks, Norbert Am 19.02.2013 um 14:55 schrieb phil(a)highoctane.be: > There is a potential problem for me with 2.0: > > It includes NativeBoost/Athens.... > > As I am targeting iOS running on a StackVM, am I stuck to 1.4? > Is there anything to do to ensure that Pharo 2.0 is not a dead end for > such developments? > > Maybe this is just me scaring myself... There is value in an all > software Pharo stack. Which is why I went that way in the first place. > > Phil > > 2013/2/19 Esteban Lorenzano <estebanlm(a)gmail.com>: >> I cannot reproduce it... did you tried in a new nautilus instance? >> >> please, do not stay in 1.4... we need the feedback of people using 2.0 to >> improve, otherwise we will not realize what is wrong :) >> >> Esteban >> >> On Feb 19, 2013, at 2:12 PM, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> That was short time fun. If I select the "old style" option and try to find >> a class using cmd-f I get the following error >> >> <Bildschirmfoto 2013-02-19 um 14.10.24.png> >> >> Maybe I stay in 1.4 a while longerâ¦ >> >> Norbert >> >> Am 19.02.2013 um 12:44 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: >> >> ha... problem is that is not "use historical keys" (I don't know what that >> setting does, btw) >> is "Use old style keys" under Nautilus group >> >> Esteban >> >> On Feb 19, 2013, at 12:39 PM, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> >> Am 19.02.2013 um 11:59 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: >> >> which most places? >> >> >> e.g. in Nautilus with historical shortcuts on I can't click on a method and >> press cmd-n to browse senders. >> >> Norbert >> >> the new shortcuts were defined in nautilus, and the historical shortcuts are >> then targeting nautilus usage. Other places didn't change (or should not >> change) any keybinding. >> >> Esteban >> >> On Feb 19, 2013, at 11:56 AM, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> For a new project I started to use pharo 2.0. But I find it really >> cumbersome to use the new keyboard shortcuts. As long as I use 1.4 in >> parallel I don't want to switch to the new ones. I've found a setting in >> Settings named "use historical shortcuts" but it is not effective in most >> places. >> Is there a way change that? >> >> >> >> >> >> >> >> >

Feb. 19, 2013

Re: [Pharo-users] Pharo 2 and old shortcuts

by Esteban Lorenzano

you are just scared :) 1) NB does not need to be used in 2.0... is just there, as any other package... it just will not work in iOS, but the image will be ok 2) Athens will replace old graphics infrastructure, but not in 2.0 and certainly, that should not be a problem for use it in iOS in the future (since athens is a framework that uses cairo, but can use other backends, like the old balllon3d) Esteban On Feb 19, 2013, at 2:55 PM, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > There is a potential problem for me with 2.0: > > It includes NativeBoost/Athens.... > > As I am targeting iOS running on a StackVM, am I stuck to 1.4? > Is there anything to do to ensure that Pharo 2.0 is not a dead end for > such developments? > > Maybe this is just me scaring myself... There is value in an all > software Pharo stack. Which is why I went that way in the first place. > > Phil > > 2013/2/19 Esteban Lorenzano <estebanlm(a)gmail.com>: >> I cannot reproduce it... did you tried in a new nautilus instance? >> >> please, do not stay in 1.4... we need the feedback of people using 2.0 to >> improve, otherwise we will not realize what is wrong :) >> >> Esteban >> >> On Feb 19, 2013, at 2:12 PM, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> That was short time fun. If I select the "old style" option and try to find >> a class using cmd-f I get the following error >> >> <Bildschirmfoto 2013-02-19 um 14.10.24.png> >> >> Maybe I stay in 1.4 a while longerâ¦ >> >> Norbert >> >> Am 19.02.2013 um 12:44 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: >> >> ha... problem is that is not "use historical keys" (I don't know what that >> setting does, btw) >> is "Use old style keys" under Nautilus group >> >> Esteban >> >> On Feb 19, 2013, at 12:39 PM, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> >> Am 19.02.2013 um 11:59 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: >> >> which most places? >> >> >> e.g. in Nautilus with historical shortcuts on I can't click on a method and >> press cmd-n to browse senders. >> >> Norbert >> >> the new shortcuts were defined in nautilus, and the historical shortcuts are >> then targeting nautilus usage. Other places didn't change (or should not >> change) any keybinding. >> >> Esteban >> >> On Feb 19, 2013, at 11:56 AM, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> For a new project I started to use pharo 2.0. But I find it really >> cumbersome to use the new keyboard shortcuts. As long as I use 1.4 in >> parallel I don't want to switch to the new ones. I've found a setting in >> Settings named "use historical shortcuts" but it is not effective in most >> places. >> Is there a way change that? >> >> >> >> >> >> >> >> >

Feb. 19, 2013

Re: [Pharo-users] Pharo 2 and old shortcuts

by phil＠highoctane.be

There is a potential problem for me with 2.0: It includes NativeBoost/Athens.... As I am targeting iOS running on a StackVM, am I stuck to 1.4? Is there anything to do to ensure that Pharo 2.0 is not a dead end for such developments? Maybe this is just me scaring myself... There is value in an all software Pharo stack. Which is why I went that way in the first place. Phil 2013/2/19 Esteban Lorenzano <estebanlm(a)gmail.com>: > I cannot reproduce it... did you tried in a new nautilus instance? > > please, do not stay in 1.4... we need the feedback of people using 2.0 to > improve, otherwise we will not realize what is wrong :) > > Esteban > > On Feb 19, 2013, at 2:12 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > > That was short time fun. If I select the "old style" option and try to find > a class using cmd-f I get the following error > > <Bildschirmfoto 2013-02-19 um 14.10.24.png> > > Maybe I stay in 1.4 a while longerâ¦ > > Norbert > > Am 19.02.2013 um 12:44 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > > ha... problem is that is not "use historical keys" (I don't know what that > setting does, btw) > is "Use old style keys" under Nautilus group > > Esteban > > On Feb 19, 2013, at 12:39 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > > > Am 19.02.2013 um 11:59 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > > which most places? > > > e.g. in Nautilus with historical shortcuts on I can't click on a method and > press cmd-n to browse senders. > > Norbert > > the new shortcuts were defined in nautilus, and the historical shortcuts are > then targeting nautilus usage. Other places didn't change (or should not > change) any keybinding. > > Esteban > > On Feb 19, 2013, at 11:56 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > > For a new project I started to use pharo 2.0. But I find it really > cumbersome to use the new keyboard shortcuts. As long as I use 1.4 in > parallel I don't want to switch to the new ones. I've found a setting in > Settings named "use historical shortcuts" but it is not effective in most > places. > Is there a way change that? > > > > > > > >

Feb. 19, 2013

Re: [Pharo-users] Pharo 2 and old shortcuts

by Esteban Lorenzano

slice is in inbox, I will integrate in half an hour http://code.google.com/p/pharo/issues/detail?id=7542 On Feb 19, 2013, at 2:45 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > thanks! > > N. > Am 19.02.2013 um 14:38 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > >> he, I have it... providing a fix now... >> >> On Feb 19, 2013, at 2:25 PM, Norbert Hartl <norbert(a)hartl.name> wrote: >> >>> >>> Am 19.02.2013 um 14:19 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: >>> >>>> I cannot reproduce it... did you tried in a new nautilus instance? >>>> >>> I downloaded latest 2.0 image. I opened it, opened the Settings browser, searched for "old style", checked option. Closed Settings browser, opened over world menu a system browser, click in the left-most pane (classes), pressed cmd-f, typed RxMatcher, selected appearing RxMatcher in list and pressed enter. >>> >>> Norbert >>> >>>> please, do not stay in 1.4... we need the feedback of people using 2.0 to improve, otherwise we will not realize what is wrong :) >>>> >>>> Esteban >>>> >>>> On Feb 19, 2013, at 2:12 PM, Norbert Hartl <norbert(a)hartl.name> wrote: >>>> >>>>> That was short time fun. If I select the "old style" option and try to find a class using cmd-f I get the following error >>>>> >>>>> <Bildschirmfoto 2013-02-19 um 14.10.24.png> >>>>> >>>>> Maybe I stay in 1.4 a while longerâ¦ >>>>> >>>>> Norbert >>>>> >>>>> Am 19.02.2013 um 12:44 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: >>>>> >>>>>> ha... problem is that is not "use historical keys" (I don't know what that setting does, btw) >>>>>> is "Use old style keys" under Nautilus group >>>>>> >>>>>> Esteban >>>>>> >>>>>> On Feb 19, 2013, at 12:39 PM, Norbert Hartl <norbert(a)hartl.name> wrote: >>>>>> >>>>>>> >>>>>>> Am 19.02.2013 um 11:59 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: >>>>>>> >>>>>>>> which most places? >>>>>>> >>>>>>> e.g. in Nautilus with historical shortcuts on I can't click on a method and press cmd-n to browse senders. >>>>>>> >>>>>>> Norbert >>>>>>> >>>>>>>> the new shortcuts were defined in nautilus, and the historical shortcuts are then targeting nautilus usage. Other places didn't change (or should not change) any keybinding. >>>>>>>> >>>>>>>> Esteban >>>>>>>> >>>>>>>> On Feb 19, 2013, at 11:56 AM, Norbert Hartl <norbert(a)hartl.name> wrote: >>>>>>>> >>>>>>>>> For a new project I started to use pharo 2.0. But I find it really cumbersome to use the new keyboard shortcuts. As long as I use 1.4 in parallel I don't want to switch to the new ones. I've found a setting in Settings named "use historical shortcuts" but it is not effective in most places. >>>>>>>>> Is there a way change that? >>>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>> >>> >> >

Feb. 19, 2013