September 2009 - Pharo-dev - lists.pharo.org

[Pharo-project] [update] #10442

by StÃ©phane Ducasse

10442 ----- - Issue 1195: Improved remove required package dialogue in Monticello - Issue 1194: Monticello is confused about what to call Log Messages - Issue 1192: Cleanup of Deprecation (important for pharo by example book) Now going to bed :)

Sept. 8, 2009

Re: [Pharo-project] Spring in November, Argentina

by Mariano Martinez Peck

On Tue, Sep 8, 2009 at 3:10 PM, Alexandre Bergel <alexandre(a)bergel.eu>wrote: > Dear List, > > I added a section in the Sprint wiki page: > > http://code.google.com/p/pharo/wiki/PharoSprints?ts=1252433348&updated=Phar… > > People should add their name. I will send a remainder a few days > before the event. > > Remember most people doesn't have access to Pharo google wiki. > Cheers, > Alexandre > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 8, 2009

Re: [Pharo-project] request for the new merge tool :)

by Gary Chambers

No problem. Will stick in the new release, when done! You may have noticed we are a bit busy (Polymorph improvements included). Can't say more than that at the moment. Regards, Gary ----- Original Message ----- From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Tuesday, September 08, 2009 7:43 PM Subject: Re: [Pharo-project] request for the new merge tool :) On Sep 8, 2009, at 8:34 PM, Gary Chambers wrote: > Yes, I see for "pick-and-mix". > That kind of bypasses the merge, as such. > > I'd suggest that the MC model could be revised to allow such > operations. > Or, I can just add another menu choice like the old tools... for now a menu would be great! Stef > > Regards, Gary > > ----- Original Message ----- > From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Tuesday, September 08, 2009 7:18 PM > Subject: Re: [Pharo-project] request for the new merge tool :) > > > > On Sep 8, 2009, at 6:53 PM, Gary Chambers wrote: > >> Install code? > > No install menu :) > Gary in the old merge tool you can select a change and install it > bringing the menu on the item > This is important since we can chose what we want to install or not. > So the behavior is there since it is working with the old one. > > Stef > >> >> Just pointing out that we should all-together decide how we want MC >> to >> interact with the user then decide you to get MC to support that... >> maybe >> MC1.0/1.5/2.0 who knows. >> >> There are clearly different needs fo all of us. Just trying to get >> things >> pinned down (somewhat) before moving things along. >> >> Regards, Gary >> >> ----- Original Message ----- >> From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> >> To: <Pharo-project(a)lists.gforge.inria.fr> >> Sent: Tuesday, September 08, 2009 5:47 PM >> Subject: Re: [Pharo-project] request for the new merge tool :) >> >> >> Gary having the install code is really important. >> >> >>> Would be great to decide on the UI we want then make MC play ball... >>> >>> Regards, Gary >>> >>> ----- Original Message ----- >>> From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> >>> To: <Pharo-project(a)lists.gforge.inria.fr> >>> Sent: Tuesday, September 08, 2009 3:28 PM >>> Subject: Re: [Pharo-project] request for the new merge tool :) >>> >>> >>>> would be great. >>>> Send code :) >>>> >>>> On Sep 8, 2009, at 4:24 PM, rkrock(a)locksleycreeksoftware.com wrote: >>>> >>>>>>>> Yes, this is what the History button is supposed to do, display >>>>>>>> the >>>>>>>> diff between two arbitrary versions. >>>>>>> >>>>>>> What about backport? >>>>>>> http://lists.squeakfoundation.org/pipermail/squeak-dev/2004-September/08209… >>>>>> >>>>>> That works in the wrong direction for me. I prefer to load >>>>>> changes >>>>>> into my working copy instead of having to load the other code and >>>>>> "backporting" my changes into their code. >>>>>> >>>>>> Lukas >>>>>> >>>>> >>>>> What about an option for go forward or backward. It really on >>>>> which >>>>> fork >>>>> of the code is considered the 'root' and that is often in the eyes >>>>> of the >>>>> beholder. >>>>> >>>>>> -- >>>>>> Lukas Renggli >>>>>> http://www.lukas-renggli.ch >>>>>> >>>>>> _______________________________________________ >>>>>> Pharo-project mailing list >>>>>> Pharo-project(a)lists.gforge.inria.fr >>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- >>>>>> project >>>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project(a)lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- >>>>> project >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 8, 2009

Re: [Pharo-project] Slice-MCDependenciesDialogPlagueFixed-ab.1.mcz

by StÃ©phane Ducasse

Ok I got you right now. :) >>>> >> >> really because we tried and it worked. >> do you have a scenario showing that it breaks > Yes, the slice "fixes" this, since you never get the dialog to write a > comment for one of the dependent packages, thus are never able to > cancel > it :) > My point was, ideally, I'd like to be able to set individual comments > for each package if I want to(checkbox), and not have it break if I > cancel one of the later ones. > And that, if I had to choose between being able to set comment per > package but risking an incomplete save if I cancel one of them, and > having the same comment for all of them, I'd rather have the latter. > > Cheers, > Henry > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 8, 2009

Re: [Pharo-project] CLFramework-UIBuilder

by Henrik Johansen

StÃ©phane Ducasse skrev: >> i published the CLFramework package >> >> http://www.squeaksource.com/CLFramework.html >> >> IÂ´m continue working in it, but I have arrived at crossroads, where >> i think >> is best create my own set of widgets, from zero, or perhaps be more >> ambitious and try use 3d... i dont know; my knowledges is limited. >> > > I think that having a layout manager (copying may be the one of sophie) > is more important than new widgets because how do the components move > when you > resize a window or the relative placement of widgets is also important. > Dabbling with it last night, this was one of the things I felt was missing the most too. It might be nice with a tab of its own for an editor of a morphs LayoutFrame, which could replace the current properties Anchors, Position and Extent - Initial placement was a snap (The list of selectable widgets is a valid droptarget though, I had to ctrl-click and delete morph a couple of times due to dropping wrong :P) - The attributes are quite easy to edit (except not remembering old values for a few of them if I navigated away, then back again) - The menu editor was very nice (a bit unintuituve that you had to ctrl-s after entering data before navigating away though, yet autosaving on icon selection. Also, only icon changes were accepted when you chose a new icon, the rest (label etc.) were lost) As for widgets, the only one I was really missing was a splitter. Cheers, Henry

Sept. 8, 2009

Re: [Pharo-project] request for the new merge tool :)

by StÃ©phane Ducasse

On Sep 8, 2009, at 8:34 PM, Gary Chambers wrote: > Yes, I see for "pick-and-mix". > That kind of bypasses the merge, as such. > > I'd suggest that the MC model could be revised to allow such > operations. > Or, I can just add another menu choice like the old tools... for now a menu would be great! Stef > > Regards, Gary > > ----- Original Message ----- > From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Tuesday, September 08, 2009 7:18 PM > Subject: Re: [Pharo-project] request for the new merge tool :) > > > > On Sep 8, 2009, at 6:53 PM, Gary Chambers wrote: > >> Install code? > > No install menu :) > Gary in the old merge tool you can select a change and install it > bringing the menu on the item > This is important since we can chose what we want to install or not. > So the behavior is there since it is working with the old one. > > Stef > >> >> Just pointing out that we should all-together decide how we want MC >> to >> interact with the user then decide you to get MC to support that... >> maybe >> MC1.0/1.5/2.0 who knows. >> >> There are clearly different needs fo all of us. Just trying to get >> things >> pinned down (somewhat) before moving things along. >> >> Regards, Gary >> >> ----- Original Message ----- >> From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> >> To: <Pharo-project(a)lists.gforge.inria.fr> >> Sent: Tuesday, September 08, 2009 5:47 PM >> Subject: Re: [Pharo-project] request for the new merge tool :) >> >> >> Gary having the install code is really important. >> >> >>> Would be great to decide on the UI we want then make MC play ball... >>> >>> Regards, Gary >>> >>> ----- Original Message ----- >>> From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> >>> To: <Pharo-project(a)lists.gforge.inria.fr> >>> Sent: Tuesday, September 08, 2009 3:28 PM >>> Subject: Re: [Pharo-project] request for the new merge tool :) >>> >>> >>>> would be great. >>>> Send code :) >>>> >>>> On Sep 8, 2009, at 4:24 PM, rkrock(a)locksleycreeksoftware.com wrote: >>>> >>>>>>>> Yes, this is what the History button is supposed to do, display >>>>>>>> the >>>>>>>> diff between two arbitrary versions. >>>>>>> >>>>>>> What about backport? >>>>>>> http://lists.squeakfoundation.org/pipermail/squeak-dev/2004-September/08209… >>>>>> >>>>>> That works in the wrong direction for me. I prefer to load >>>>>> changes >>>>>> into my working copy instead of having to load the other code and >>>>>> "backporting" my changes into their code. >>>>>> >>>>>> Lukas >>>>>> >>>>> >>>>> What about an option for go forward or backward. It really on >>>>> which >>>>> fork >>>>> of the code is considered the 'root' and that is often in the eyes >>>>> of the >>>>> beholder. >>>>> >>>>>> -- >>>>>> Lukas Renggli >>>>>> http://www.lukas-renggli.ch >>>>>> >>>>>> _______________________________________________ >>>>>> Pharo-project mailing list >>>>>> Pharo-project(a)lists.gforge.inria.fr >>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- >>>>>> project >>>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project(a)lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- >>>>> project >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 8, 2009

Re: [Pharo-project] Slice-MCDependenciesDialogPlagueFixed-ab.1.mcz

by Henrik Johansen

StÃ©phane Ducasse skrev: >>> Slice-MCDependenciesDialogPlagueFixed-ab.1.mcz >>> <http://www.squeaksource.com/PharoInbox.html> >>> >>> via PharoInbox <http://www.squeaksource.com/> on 9/8/09 >>> >>> >>> Is it necessary to offer a checkbox in the parent's save dialogue to >>> ask if this is the desired behaviour? >>> >> With the current behaviour, I'd say no. >> > > > >> If you try to cancel the extra >> dialogs, >> > yes this is what we tried to achieve > > >> it leads to an error and unloadable slices... >> > > really because we tried and it worked. > do you have a scenario showing that it breaks Yes, the slice "fixes" this, since you never get the dialog to write a comment for one of the dependent packages, thus are never able to cancel it :) My point was, ideally, I'd like to be able to set individual comments for each package if I want to(checkbox), and not have it break if I cancel one of the later ones. And that, if I had to choose between being able to set comment per package but risking an incomplete save if I cancel one of them, and having the same comment for all of them, I'd rather have the latter. Cheers, Henry

Sept. 8, 2009

Re: [Pharo-project] request for the new merge tool :)

by Gary Chambers

Yes, I see for "pick-and-mix". That kind of bypasses the merge, as such. I'd suggest that the MC model could be revised to allow such operations. Or, I can just add another menu choice like the old tools... Regards, Gary ----- Original Message ----- From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Tuesday, September 08, 2009 7:18 PM Subject: Re: [Pharo-project] request for the new merge tool :) On Sep 8, 2009, at 6:53 PM, Gary Chambers wrote: > Install code? No install menu :) Gary in the old merge tool you can select a change and install it bringing the menu on the item This is important since we can chose what we want to install or not. So the behavior is there since it is working with the old one. Stef > > Just pointing out that we should all-together decide how we want MC to > interact with the user then decide you to get MC to support that... > maybe > MC1.0/1.5/2.0 who knows. > > There are clearly different needs fo all of us. Just trying to get > things > pinned down (somewhat) before moving things along. > > Regards, Gary > > ----- Original Message ----- > From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Tuesday, September 08, 2009 5:47 PM > Subject: Re: [Pharo-project] request for the new merge tool :) > > > Gary having the install code is really important. > > >> Would be great to decide on the UI we want then make MC play ball... >> >> Regards, Gary >> >> ----- Original Message ----- >> From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> >> To: <Pharo-project(a)lists.gforge.inria.fr> >> Sent: Tuesday, September 08, 2009 3:28 PM >> Subject: Re: [Pharo-project] request for the new merge tool :) >> >> >>> would be great. >>> Send code :) >>> >>> On Sep 8, 2009, at 4:24 PM, rkrock(a)locksleycreeksoftware.com wrote: >>> >>>>>>> Yes, this is what the History button is supposed to do, display >>>>>>> the >>>>>>> diff between two arbitrary versions. >>>>>> >>>>>> What about backport? >>>>>> http://lists.squeakfoundation.org/pipermail/squeak-dev/2004-September/08209… >>>>> >>>>> That works in the wrong direction for me. I prefer to load changes >>>>> into my working copy instead of having to load the other code and >>>>> "backporting" my changes into their code. >>>>> >>>>> Lukas >>>>> >>>> >>>> What about an option for go forward or backward. It really on which >>>> fork >>>> of the code is considered the 'root' and that is often in the eyes >>>> of the >>>> beholder. >>>> >>>>> -- >>>>> Lukas Renggli >>>>> http://www.lukas-renggli.ch >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project(a)lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- >>>>> project >>>>> >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 8, 2009

Re: [Pharo-project] Slice-MCDependenciesDialogPlagueFixed-ab.1.mcz

by StÃ©phane Ducasse

>> >> Slice-MCDependenciesDialogPlagueFixed-ab.1.mcz >> <http://www.squeaksource.com/PharoInbox.html> >> >> via PharoInbox <http://www.squeaksource.com/> on 9/8/09 >> >> >> Is it necessary to offer a checkbox in the parent's save dialogue to >> ask if this is the desired behaviour? > With the current behaviour, I'd say no. > If you try to cancel the extra > dialogs, yes this is what we tried to achieve > it leads to an error and unloadable slices... really because we tried and it worked. do you have a scenario showing that it breaks? > Better then with an atomic operation that is either done or not, and > having the comment > behaviour forced. > Ideally, I think it'd be nice to have an "apply to all" checkbox, > and if > not checked, change it so comments are all set before anything is > stored. (using the comment for the "top" package as default) Yes the problem is that MC uses its own widgetspec and there is no support for checkbox > > Cheers, > Henry > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 8, 2009

[Pharo-project] Fixed: Monticello is confused ...

by Andrew P. Black

I just submitted a fix, mostly internal to the MC GUI. Log messages are now called log messages, uniformly. Also, when asking MC to remove a required package, the dialog now asks the user to select only from the presently required packages, not every package in the system. The package is MonticelloGUI-AndrewBlack.7

Sept. 8, 2009