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

Re: [Pharo-project] Maintaining KPF (was Keeping released version image up to date (was did you...)

by StÃ©phane Ducasse

Right now we have milestone1.0 and milestone1.1 for the fixes that are integrated in both But indeed we could have a specific tags. Stef >> >> > Is it possible to add a new status in Google Code, of Closed-KPF-1.0? > Then Closed means it was fixed and retrofitted to 1.0. Closed-KPF-1.0 means > fixed only in 1.1alpha. > Making the KPF list becomes trivial. > And it also captures the knowledge of whether the issue applied to 1.0 at > the time of closing, rather than someone have to puzzle over it when making > a release. > ...Stan > > > > -- > View this message in context: http://n2.nabble.com/Re-did-you-check-in-1-1-how-the-old-browser-now-suppor… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 23, 2009

Re: [Pharo-project] can we include this in NewInspector ?? (WAS) Fwd: [ANN] MagmaBrowser

by Mariano Martinez Peck

I was thinking if this little improvement will be of help to NullPointer and the UIBuilder. On Wed, Dec 23, 2009 at 12:15 PM, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr> wrote: > This is christmax. > > > Icons for Morph instances : Done :) Moreover I put the image of the morph > in the description pane (see the screenshot) ! :) > > > > Other things Stef ? :) > > This is cool definitively cool. > Are the morphs living? :) > can I interact with them? > I guess not because it would mean that you have either to copy them (bad > idea). > So I was dreaming :) > > Stef > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Dec. 23, 2009

Re: [Pharo-project] Fwd: about allCallOn -> AllReferTo : issue 261

by StÃ©phane Ducasse

Ok the three systemNavigation were broken before? We still need to fix them :) Stef > Stef, > > Between a 11106 (which does not contain my fix) and 11111 (which contains my fix), there is only one more test fail, which is not related to allCallOn: (but in ReleaseTest). > >>> I integrated your changes but apparently some tests are broken. >>> Can you have a look? > > I am not sure which test you're referring to. Among failed tests, I do not imediately see the one related to my fix. > > I first thought that testIsUnsentMessagesIn* test would be related. But actually not. They were yellow before my fix was incorporated, and these tests indirectly use SystemNavigation>>allSendersOf: selector > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > <Picture 1.png><Picture 2.png> > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 23, 2009

Re: [Pharo-project] can we include this in NewInspector ?? (WAS) Fwd: [ANN] MagmaBrowser

by StÃ©phane Ducasse

This is christmax. > Icons for Morph instances : Done :) Moreover I put the image of the morph in the description pane (see the screenshot) ! :) > > Other things Stef ? :) This is cool definitively cool. Are the morphs living? :) can I interact with them? I guess not because it would mean that you have either to copy them (bad idea). So I was dreaming :) Stef

Dec. 23, 2009

Re: [Pharo-project] Fwd: A design question

by StÃ©phane Ducasse

> Why not to redefine package on your fixture ? > Let's say you define a class named #Fixture for your test. You can > simply redefined Fixture class>>package. Ok but in that case I do not tests the behavior on class But this is an idea (Now I generate all the classes on the fly so I would have to compile all the methods). Stef

Dec. 23, 2009

Re: [Pharo-project] Fwd: sort: and sortBlock:

by StÃ©phane Ducasse

Nicolas could we build a path to make sure that we can move on? I would love to write new collection using traits (but I have no time :( I should finish sometimes what I start -- geesh). I started to implement OrderedSet (OrderedCollection no duplicate) but I think that I want probably UniqueOrdered. I will publish what I have done and ask for feedback and that other can improve. I like the idea of using the TraitsTest to have coherent sets of behavior. >> asSortedArray > asSortedCollection > asSortedCollection: > sortBy: > > A bit too many selectors? > > The different semantics currently are: > - sort in place - #sort and #sort: > - make a sorted copy - #asSortedArray does except if already > isMemberOf: Array and isSorted, #sortBy: does too but is only > understood by SequenceableCollection (stupid) > - make a sorted collection that can further sort added elements - > #asSortedCollection #asSortedCollection: > #sortBlock: has 2 semantics: instance creation and modifying the sort > block of an instance... > > And I would like another message to avoid all these keys asArray sort > I spreaded in trunk: > - sort in place if possible (if Sequenceable), or create a sorted > sequence otherwise > But you can understand I did not dare adding a new selector :) > > Nicolas

Dec. 23, 2009

[Pharo-project] Maintaining KPF (was Keeping released version image up to date (was did you...)

by Stan Shepherd

StÃ©phane Ducasse wrote: > > Yes in an ideal world. > Now either we can script the bugreport to generate that list automatically > or we will not have the resources to do it. > > Then I do not imagine somebody patient enough to read a log full of bug > descriptions. :) > But may be I'm just too lazy. > > Stef > On Dec 22, 2009, at 10:24 AM, Stan Shepherd wrote: > >> >> >> StÃ©phane Ducasse wrote: >>> >>> >>> >>> The process we have in mind is that if the bug is **really** important >>> then it will be fixed in 1.1 and 1.0. >>> We did that in the past for Squeak 3.9. >>> Now normal improvements changes.... will not be retro-ported because we >>> simply cannot. >>> And you are right to report a bug it is important in the future that >>> people check if the bug is already fixed >>> in the current unstable else we will not be able to make process and we >>> will spend our time testing. >>> >>> >> It sounds like the periodic 1.0 releases need to include a known problems >> file, which would include all bugs fixed in 1.1 alpha but not planned to >> be >> retrofitted. >> And it's probably important to make clear that, if in doubt, we should >> log a >> bug and risk it being a duplicate. Because the people with a genius for >> finding bugs are new users, and they may not be able to tell whether or >> not >> it's the same bug. >> >> -- >> View this message in context: >> http://n2.nabble.com/Re-did-you-check-in-1-1-how-the-old-browser-now-suppor… >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> >> _______________________________________________ > > Is it possible to add a new status in Google Code, of Closed-KPF-1.0? Then Closed means it was fixed and retrofitted to 1.0. Closed-KPF-1.0 means fixed only in 1.1alpha. Making the KPF list becomes trivial. And it also captures the knowledge of whether the issue applied to 1.0 at the time of closing, rather than someone have to puzzle over it when making a release. ...Stan -- View this message in context: http://n2.nabble.com/Re-did-you-check-in-1-1-how-the-old-browser-now-suppor… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Dec. 23, 2009

Re: [Pharo-project] Fwd: about allCallOn -> AllReferTo : issue 261

by Alexandre Bergel

Stef, Between a 11106 (which does not contain my fix) and 11111 (which contains my fix), there is only one more test fail, which is not related to allCallOn: (but in ReleaseTest). >> I integrated your changes but apparently some tests are broken. >> Can you have a look? I am not sure which test you're referring to. Among failed tests, I do not imediately see the one related to my fix. I first thought that testIsUnsentMessagesIn* test would be related. But actually not. They were yellow before my fix was incorporated, and these tests indirectly use SystemNavigation>>allSendersOf: selector Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Dec. 23, 2009

Re: [Pharo-project] can we include this in NewInspector ?? (WAS) Fwd: [ANN] MagmaBrowser

by Mariano Martinez Peck

that's is TOO cool :) 2009/12/23 Frederic Pluquet <fpluquet(a)ulb.ac.be> > Icons for Morph instances : Done :) Moreover I put the image of the morph > in the description pane (see the screenshot) ! :) > > Other things Stef ? :) > > Fred > ---- > FrÃ©dÃ©ric Pluquet > UniversitÃ© Libre de Bruxelles (ULB) > Assistant > http://www.ulb.ac.be/di/fpluquet > > > On Wed, Dec 23, 2009 at 8:58 AM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > >> I like when we can get the butter and the money for the butter :) >> Indeed like that this is really cool. >> Did you try to see if you could display any morph like that? ( I mean as >> icon). >> Stef >> >> On Dec 22, 2009, at 9:35 PM, Frederic Pluquet wrote: >> >> > Good idea. Too easy finally :) Done in the last version (see the >> screenshot)! >> > >> > For Form and Color instances. Parametrizable by blocks or method >> overridding (#niIcon or #niIconName) :) >> > >> > FrÃ©d >> > ---- >> > FrÃ©dÃ©ric Pluquet >> > UniversitÃ© Libre de Bruxelles (ULB) >> > Assistant >> > http://www.ulb.ac.be/di/fpluquet >> > >> > >> > 2009/12/22 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> > Fred >> > >> > this is cool !! >> > >> > Now I was thinking if you could not reuse this block and use it to add >> the visual before the [1] : Form... >> > as int he explorer >> > >> > Stef >> > >> > >> > >> > >> > >> > >> > > Form allInstances >> > >> > >> > _______________________________________________ >> > Pharo-project mailing list >> > Pharo-project(a)lists.gforge.inria.fr >> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > >> > <Forms with Icons !.png>_______________________________________________ >> > 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 >

Dec. 23, 2009

Re: [Pharo-project] can we include this in NewInspector ?? (WAS) Fwd: [ANN] MagmaBrowser

by Frederic Pluquet

Icons for Morph instances : Done :) Moreover I put the image of the morph in the description pane (see the screenshot) ! :) Other things Stef ? :) Fred ---- FrÃ©dÃ©ric Pluquet UniversitÃ© Libre de Bruxelles (ULB) Assistant http://www.ulb.ac.be/di/fpluquet On Wed, Dec 23, 2009 at 8:58 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > I like when we can get the butter and the money for the butter :) > Indeed like that this is really cool. > Did you try to see if you could display any morph like that? ( I mean as > icon). > Stef > > On Dec 22, 2009, at 9:35 PM, Frederic Pluquet wrote: > > > Good idea. Too easy finally :) Done in the last version (see the > screenshot)! > > > > For Form and Color instances. Parametrizable by blocks or method > overridding (#niIcon or #niIconName) :) > > > > FrÃ©d > > ---- > > FrÃ©dÃ©ric Pluquet > > UniversitÃ© Libre de Bruxelles (ULB) > > Assistant > > http://www.ulb.ac.be/di/fpluquet > > > > > > 2009/12/22 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > Fred > > > > this is cool !! > > > > Now I was thinking if you could not reuse this block and use it to add > the visual before the [1] : Form... > > as int he explorer > > > > Stef > > > > > > > > > > > > > > > Form allInstances > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > <Forms with Icons !.png>_______________________________________________ > > 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 >

Dec. 23, 2009