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

[Pharo-project] Help clarify

by Hilaire Fernandes

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? -- http://blog.ofset.org/hilaire

Jan. 13, 2009

Re: [Pharo-project] GUI editor, etc.

by Bill Schwab

Gary, Thanks!!!! Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029 >>> gazzaguru2(a)btinternet.com 01/12/09 2:29 PM >>> Polymorph-Magritte is on SqueakSource now, usual place (under the Polymorph project). Let me know how you get on. Additionally we have a small package (just a couple of methods) for using Polymorph-Magritte with the Units package if anyone is interested. Regards, Gary. ----- Original Message ----- From: GARY CHAMBERS To: Pharo-project(a)lists.gforge.inria.fr Sent: Friday, January 09, 2009 11:34 AM Subject: Re: [Pharo-project] GUI editor, etc. We have a package that provides Polymorph support for Magritte, as used in our ReportBuilder. I'm sure it would be no problem to get it released into SqueakSource :-) Regards, Gary ------------------------------------------------------------------------------ From: Bill Schwab <BSchwab(a)anest.ufl.edu> To: pharo-project(a)lists.gforge.inria.fr Sent: Friday, 9 January, 2009 4:16:55 AM Subject: [Pharo-project] GUI editor, etc. Hello all, There was some recent mention of GUI frameworks and/or an editor. For fear of losing the idea, I will just throw this out now while I am thinking of it. I submit that one needs both a drag/drop graphical tool, and a programmatic capability. The graphical approach works well for many/most uses. Programmatic construction is very helpful for creating views to match RDB schemas, etc. Magritte might be of help in both scenarios, especially the programmatic side. We might get a lot out of simply "telling Magritte about Polymorph." So far at least, we seem to be using code, not data structures, to assemble views. That would make the graphical tool something that should work like I _think_ WindowBuilder does/did. My recollection is that it executed code to construct objects and then had the modified objects write code to recreate themselves. I fear we need to be careful about looking at the code to see how it works. Perhaps a little controversial, Tweak strikes me (please feel free to disagree/correct as appropriate) as using compiler/language changes to do things that can be (and so far, I would argue should be) accomplished by composition of objects with the language as-is. What Tweak shows as events in code browsers, I would prefer to see listed in a graphical tool editor. I'm pretty sure I recall WindowBuilder doing a nice job of that too. The toothpicks holding my eyes open are about to snap. Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029 _______________________________________________ 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 Lukas Renggli

> 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

Jan. 13, 2009

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

by Hilaire Fernandes

I don't know. But I remember problem with Magma and Pharo when persisting MorphExtension using SmallDictionary (or SmallDictionnaryIdentity). Chris fund the optimisation of using SmallDictionnaryIdentity not really relevant. I have no opinion on that Hilaire 2009/1/13 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > Hi all > > We have no idea where SmallDictionary come from? 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. > > 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 > -- http://blog.ofset.org/hilaire

Jan. 13, 2009

Re: [Pharo-project] [MC] [ANN] Sourcetalk

by StÃ©phane Ducasse

but why saving the complete package is a problem. I hate to have a piece of code and not be able to use because another part is on nother server and down or gone. Stef On Jan 13, 2009, at 12:22 AM, Mariano Martinez Peck wrote: > > > On Mon, Jan 12, 2009 at 9:07 PM, Keith Hodges <keith_hodges(a)yahoo.co.uk > > wrote: > Mariano Martinez Peck wrote: > > Excelents both documents. I really like them! > > > > I am one of the SqueakDBX team and one reason I really hate > monticello > > is that when every time I want to save (commit) it commits full > > package. This is very annoying, > So switch it to diff mode. > > I think there is something I don't know about MC. Suppose I have a > whole package. I modified some clases. But I don't want to commit > some of those changes. If I see diff mode, I can see the diffs, but, > If I commit, I commit all. Not only the changes I want. To do that, > I have to override the rest of the changes so that not to commit > them. And, If I do this, I loose those changes. So, I have to backup > those changes in a file, then commit, and recover the changes again. > > I mean, I would like something like CVS or SVN where you can commit > what you want, no the whole package. > > I don't know If I could express myself. Sorry for my English. > > > > Keith > > _______________________________________________ > 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] new look / monticello UI

by Damien Cassou

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. I would vote for non-modality or window-modality to be able to use the code browser while merging. Bye -- Damien Cassou http://damiencassou.seasidehosting.st

Jan. 13, 2009

[Pharo-project] SmallDictionary ?? vs RB SmallDictionary

by StÃ©phane Ducasse

Hi all We have no idea where SmallDictionary come from? 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. 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

Jan. 13, 2009

Re: [Pharo-project] [MC] [ANN] Sourcetalk

by Keith Hodges

Mariano Martinez Peck wrote: > > > On Mon, Jan 12, 2009 at 9:07 PM, Keith Hodges > <keith_hodges(a)yahoo.co.uk <mailto:keith_hodges@yahoo.co.uk>> wrote: > > Mariano Martinez Peck wrote: > > Excelents both documents. I really like them! > > > > I am one of the SqueakDBX team and one reason I really hate > monticello > > is that when every time I want to save (commit) it commits full > > package. This is very annoying, > So switch it to diff mode. > > > I think there is something I don't know about MC. Suppose I have a > whole package. I modified some clases. But I don't want to commit > some of those changes. If I see diff mode, I can see the diffs, but, > If I commit, I commit all. Not only the changes I want. To do that, I > have to override the rest of the changes so that not to commit them. > And, If I do this, I loose those changes. So, I have to backup those > changes in a file, then commit, and recover the changes again. > > I mean, I would like something like CVS or SVN where you can commit > what you want, no the whole package. > > I don't know If I could express myself. Sorry for my English. There is a mode in which MC only saves the changes since the previous version. Not many people use it, but it is there. There is a menu item in the right hand panel I think it is. Keith

Jan. 13, 2009

Re: [Pharo-project] [MC] [ANN] Sourcetalk

by Mariano Martinez Peck

On Mon, Jan 12, 2009 at 9:07 PM, Keith Hodges <keith_hodges(a)yahoo.co.uk>wrote: > Mariano Martinez Peck wrote: > > Excelents both documents. I really like them! > > > > I am one of the SqueakDBX team and one reason I really hate monticello > > is that when every time I want to save (commit) it commits full > > package. This is very annoying, > So switch it to diff mode. > I think there is something I don't know about MC. Suppose I have a whole package. I modified some clases. But I don't want to commit some of those changes. If I see diff mode, I can see the diffs, but, If I commit, I commit all. Not only the changes I want. To do that, I have to override the rest of the changes so that not to commit them. And, If I do this, I loose those changes. So, I have to backup those changes in a file, then commit, and recover the changes again. I mean, I would like something like CVS or SVN where you can commit what you want, no the whole package. I don't know If I could express myself. Sorry for my English. > > Keith > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 12, 2009

Re: [Pharo-project] [MC] [ANN] Sourcetalk

by Keith Hodges

Mariano Martinez Peck wrote: > Excelents both documents. I really like them! > > I am one of the SqueakDBX team and one reason I really hate monticello > is that when every time I want to save (commit) it commits full > package. This is very annoying, So switch it to diff mode. Keith

Jan. 12, 2009