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

Re: [Pharo-project] BTree gones ?

by StÃ©phane Ducasse

Yes marcus is right. > Aha? > I guess it was installed from Magma, then for an unknown reason is was > maked as obselete by MC... > > > > 2009/1/13 Marcus Denker <denker(a)iam.unibe.ch>: >> Hi, >> >> As much as I know there was never a BTree class in Squeak. >> (And it was not removed in Pharo). >> >> Marcus >> >> On 12.01.2009, at 20:11, Hilaire Fernandes wrote: >> >>> Can you confirm. >>> I need it for Magma. >>> >>> Is this one suitable http://www.squeaksource.com/BTree.html ? >>> >>> Hilaire >>> >>> -- >>> http://blog.ofset.org/hilaire >>> >>> _______________________________________________ >>> 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 >> > > > > -- > http://blog.ofset.org/hilaire > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 13, 2009

Re: [Pharo-project] SmallDictionary ?? vs RB SmallDictionary

by StÃ©phane Ducasse

Yes this is strange, we will check that. Stef >> Hi all >> >> We have no idea where SmallDictionary come from? > > I added it. It's a renamed RBSmallDictionary... maybe > this was not a good idea, but then, it's used in many > place (RB, Seaside...). > >> It was not in 3.9 >> Especially since >> >> Set |array tally| >> Dictionary >> SmallDictionary |keys values size| >> >> and it does not seems defined as needed. >> RBSmallDictionary seems much better. >> > > How? It should be the same. > >> We are currently applying traits tests to these classes and this is >> really interesting to see the bugs popping out. >> >> Nicolas sent a fix for capacity that I'm planning to integrate but I >> was wondering. >> >> Stef >> >> >> _______________________________________________ >> 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 >

Jan. 13, 2009

Re: [Pharo-project] BTree gones ?

by Hilaire Fernandes

Aha? I guess it was installed from Magma, then for an unknown reason is was maked as obselete by MC... 2009/1/13 Marcus Denker <denker(a)iam.unibe.ch>: > Hi, > > As much as I know there was never a BTree class in Squeak. > (And it was not removed in Pharo). > > Marcus > > On 12.01.2009, at 20:11, Hilaire Fernandes wrote: > >> Can you confirm. >> I need it for Magma. >> >> Is this one suitable http://www.squeaksource.com/BTree.html ? >> >> Hilaire >> >> -- >> http://blog.ofset.org/hilaire >> >> _______________________________________________ >> 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 > -- http://blog.ofset.org/hilaire

Jan. 13, 2009

Re: [Pharo-project] Breakpoints (was [OT] Great job guys)

by Marcus Denker

On 09.01.2009, at 16:19, StÃ©phane Ducasse wrote: > one of the point about breakpoint is that they should not get the > method dirty. > I know that some breakpoint code has been harvested but I do not > remember how > to use it. > There is a very simple breakpoint mechanism in Pharo (in Squeak, too, but it was a bit broken there). To try: There is a "toggle break on entry" item in the menu of methods in the old browser. Technically, this just recompiles the method with a call to #break at the beginning. Could be improved a lot. Marcus > Stef > > On Jan 9, 2009, at 10:27 AM, Janko MivÅ¡ek wrote: > >> Dale Henrichs wrote: >>> ----- "Janko MivÅ¡ek" <janko.mivsek(a)eranova.si> wrote: >>> >>> | And when you are already doing that, introduce also breakpoints >>> back in >>> | Pharo as they are on GLASS GemTools. Very intuitive and the same >>> as on >>> | most other Smalltalks. If they can be supported in GemTools, why >>> | aren't yet in Pharo? Any technical reason? >>> >>> Breakpoints in GLASS/GemTools are taking advantage of the >>> breakpoint feature in the GemStone/S VM. Remember, Squeak/Pharo are >>> used as an OmniBrowser client for GLASS -- the debugger is running >>> in a GemStone vm and the UI is running in the Squeak/Pharo vm. >> >> What I like about breakpoints in GemTools is the simplicity from >> usability standpoint. And similarity of use to other Smalltaltalks. >> >> And because their UI part is implemented in OmniBrowser on GemTools, >> they should be easily ported back to Pharo OmniBrowser, even that >> breakpoints in GS/S are implemented differently than in Squeak. >> >> In other words, let we port the UI for breakpoints first, on top of >> whatever Squeak supports for breakpoints currently. Later breakpoints >> can be enhanced on VM level as well. >> >> Janko >> >> -- >> Janko MivÅ¡ek >> AIDA/Web >> Smalltalk Web Application Server >> http://www.aidaweb.si >> >> _______________________________________________ >> 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

Jan. 13, 2009

Re: [Pharo-project] SmallDictionary ?? vs RB SmallDictionary

by Marcus Denker

On 13.01.2009, at 09:17, StÃ©phane Ducasse wrote: > Hi all > > We have no idea where SmallDictionary come from? I added it. It's a renamed RBSmallDictionary... maybe this was not a good idea, but then, it's used in many place (RB, Seaside...). > It was not in 3.9 > Especially since > > Set |array tally| > Dictionary > SmallDictionary |keys values size| > > and it does not seems defined as needed. > RBSmallDictionary seems much better. > How? It should be the same. > We are currently applying traits tests to these classes and this is > really interesting to see the bugs popping out. > > Nicolas sent a fix for capacity that I'm planning to integrate but I > was wondering. > > Stef > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 13, 2009

Re: [Pharo-project] BTree gones ?

by Marcus Denker

Hi, As much as I know there was never a BTree class in Squeak. (And it was not removed in Pharo). Marcus On 12.01.2009, at 20:11, Hilaire Fernandes wrote: > Can you confirm. > I need it for Magma. > > Is this one suitable http://www.squeaksource.com/BTree.html ? > > Hilaire > > -- > http://blog.ofset.org/hilaire > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 13, 2009

Re: [Pharo-project] Extracting methods to traits

by Alexandre Bergel

Thanks Damien, I will fix that Alexandre On 8 Jan 2009, at 06:41, Damien Cassou wrote: > On Tue, Jan 6, 2009 at 7:36 PM, Alexandre Bergel > <Alexandre.Bergel(a)inria.fr> wrote: >> A method may be moved to a trait by pressing Cmd-e (or selecting the >> menu entry 'move method into a new trait'). >> >> This version contains an improvement of TOBCmdMoveToTrait. Before >> doing the refactoring, the method is checked first whether some >> instance variables are accessed. In that case, a popup window offers >> few options. >> A list of possible trait names are also offered to select the trait >> the method should be moved in. >> >> I think that if you execute any load*OB method, you will get this. > > I've just seen your commit to OB-Enhancements. Please do not use > UIEnhancements but only OB classes. > > UIManager default chooseFrom: #('proceed' 'open a debugger') title: > aString. > > should be converted to use OBChoiceRequest. > > Bye > > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 13, 2009

Re: [Pharo-project] Help clarify

by Igor Stasenko

2009/1/13 Hilaire Fernandes <hilaire(a)ofset.org>: > I need to write a DoubleLinkedList, checking for LinkedList I saw > > add: link after: otherLink > > "Add otherLink after link in the list. Answer aLink." > > | savedLink | > lastLink == otherLink ifTrue: [^ self addLast: link]. > savedLink := otherLink nextLink. > otherLink nextLink: link. > link nextLink: savedLink. > ^link. > > Why is savedLink needed ? > > Why not: > lastLink == otherLink ifTrue: [^ self addLast: link]. > link nextLink: otherLink nextLink. > otherLink nextLink: link. > ^link. > > Are there any hidden reason I don't see? > isn't a DoubleLinkedList means that there should be not only next, but prev as well? then, if nextLink: implemented as following (i don't have sources): nextLink: aLink next := aLink. aLink prev: self then you should use savedLink to avoid losing a correct prev link. > -- > http://blog.ofset.org/hilaire > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

Jan. 13, 2009

Re: [Pharo-project] new look / monticello UI

by Adrian Lienhard

On Jan 13, 2009, at 09:24 , Damien Cassou wrote: > On Mon, Jan 12, 2009 at 3:27 PM, Gary Chambers > <gazzaguru2(a)btinternet.com> wrote: >> There is a newer version of Polymorph-Tools-Diff on SqueakSource >> that tidies >> some things up (including not merging when window closed if no >> conflicts. >> This was original MC behaviour that was replicated). > > Thank you very much Gary. +1 > I would vote for non-modality or window-modality to be able to use the > code browser while merging. +1 Adrian

Jan. 13, 2009

Re: [Pharo-project] SmallDictionary ?? vs RB SmallDictionary

by StÃ©phane Ducasse

Sounds really interesting. Thanks for the pointer. I will have a look. Ideally I would like to have a good collection library and the variation you mentioned are proving that this is the way to go. Stef On Jan 13, 2009, at 10:56 AM, Lukas Renggli wrote: >> We have no idea where SmallDictionary come from? It was not in 3.9 >> Especially since > > The original SmallDictionary comes from RB. I once read some > justification why this is useful for RB, but I do not remember where I > found that. > >> and it does not seems defined as needed. >> RBSmallDictionary seems much better. > > They both have the problem that they subclass from Dictionary and you > inherit a lot of stuff that is not really necessary. As far as I know > the original RBSmallDictionary was not a subclass of Collection. > >> We are currently applying traits tests to these classes and this is >> really interesting to see the bugs popping out. > > Seaside has WASmallDictionary, another reincarnation of the > RBSmallDictionary. > > We need it because we have lots of small dictionaries that we want to > access fast. Furthermore the WASmallDictionary is ordered, so it > remembers the order in which keys are added. This makes everything > that seaside produces deterministic and therefore much easier to test > (before sometimes attributes appeared in a different order in the > generated html). Also WASmallDictionary makes it easy to have > subclasses where the same key is defined multiple times (as for > example necessary for request and response header fields). > > Of course we also wrote a lot of tests. Maybe you want to have a > look at those? > > Cheers, > Lukas > > -- > 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 >

Jan. 13, 2009