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

Re: [Pharo-project] KnownLands: a Class dependency explorer

by StÃ©phane Ducasse

I imagine :) Fernando told me that he wants to program in 3d its objects/class so I imagine that what you want is the "same" looking at browsing coding in a different way. Stef

July 21, 2009

Re: [Pharo-project] Who are you?

by Francois Stephany

Alexandre Bergel wrote: > How many companies are using Pharo? Without thinking too much, I know > there are Netstyle.ch and Pinesoft. Are there more? We've just started a company ( http://agilitic.com/ ) with two friends. We mainly do web development with Rails/Django but we're looking for Seaside projects as well...

July 21, 2009

Re: [Pharo-project] [ANN] 10384 extraction of MorphicExtras

by Adrian Lienhard

Thanks. Strange that these tests didn't fail when I run them, but now they do. Will fix in the evening. Adrian On Jul 21, 2009, at 12:11 , StÃ©phane Ducasse wrote: > seems that you broke tests of Host... > > > adaptToWorld: aWorld > > myWorld := aWorld. > myProject := nil. "figure it out if and when > needed. maybe make it easier to find" > myHand := aWorld primaryHand. > > seems missing because it was packaged in *morphic extras* > > On Jul 20, 2009, at 10:29 PM, Adrian Lienhard wrote: > >> This update removes the MorphicExtras package. I had to spend quite >> some effort to properly detangle it from the rest of the system... >> >> MorphicExtras contained examples and experimental (and some wicked) >> morphs (in total 110 classes). The space gained is significant: >> 1.5MB. >> If somebody is interested to recover and maintain parts of what I >> removed, the package is available on SqueakSource [1]. >> >> If you experience problems, please report them as this update touched >> a lot of different places inthe system. >> >> Cheers, >> Adrian >> >> [1] www.squeaksource.com/PharoMorphicExtras.html >> >> _______________________________________________ >> 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

July 21, 2009

Re: [Pharo-project] KnownLands: a Class dependency explorer

by David Goehrig

sorry steff once again its nothing like what I'm working on :) Dave On Tue, Jul 21, 2009 at 5:04 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > May be you should have a look at Glamour > because you can script UI. > > Stef > > On Jul 20, 2009, at 11:36 PM, David Goehrig wrote: > > > On Mon, Jul 20, 2009 at 5:12 PM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr > > > wrote: > > > > Why? > > Because you can script your visualization and try all kind of them. > > Mondrian a visualisation engine. > > Soon with lumiere developed by fernando you will be able to script 3d > > objects. > > > > Because the tools I'm working on are more geared more towards live > > editing of classes and object method dictionaries than modeling and > > visualization. > > > > For example, if a circle represents a class's method dictionary, > > you can right click on it to see the list of messages associated > > with its CompiledMethods. Then you can right click on any of the > > CompiledMethods to bring up an editor, and alter the contents of the > > method, recompile, and the relationships will change accordingly. > > Similarly, you can reorganize methods by dragging and dropping them > > into different classes, etc. > > > > The design and structure of Mondrian makes it terribly difficult to > > produce that sort of interface without doing as much work as it > > would to just write it from scratch :) > > > > Dave > > > > -- > > -=-=-=-=-=-=-=-=-=-=- http://blog.dloh.org/ > > _______________________________________________ > > 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.dloh.org/

July 21, 2009

Re: [Pharo-project] [ANN] 10384 extraction of MorphicExtras

by StÃ©phane Ducasse

seems that you broke tests of Host... adaptToWorld: aWorld myWorld := aWorld. myProject := nil. "figure it out if and when needed. maybe make it easier to find" myHand := aWorld primaryHand. seems missing because it was packaged in *morphic extras* On Jul 20, 2009, at 10:29 PM, Adrian Lienhard wrote: > This update removes the MorphicExtras package. I had to spend quite > some effort to properly detangle it from the rest of the system... > > MorphicExtras contained examples and experimental (and some wicked) > morphs (in total 110 classes). The space gained is significant: 1.5MB. > If somebody is interested to recover and maintain parts of what I > removed, the package is available on SqueakSource [1]. > > If you experience problems, please report them as this update touched > a lot of different places inthe system. > > Cheers, > Adrian > > [1] www.squeaksource.com/PharoMorphicExtras.html > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 21, 2009

Re: [Pharo-project] [ANN] 10381 and 10382

by StÃ©phane Ducasse

We just fixed that. Stef On Jul 20, 2009, at 9:46 PM, Adrian Lienhard wrote: > Please note that there are about 10 tests related to dictionaries that > fail now. > > Adrian > > On Jul 20, 2009, at 17:39 , StÃ©phane Ducasse wrote: > >> Issue 962: remove BlockArgsNode KeyWordNode >> - Issue 463: SmallDictionary should not be a subclass of Set (and >> Dictionary) >> cleaner SmallDictionary + more tests >> - removing RBSmallDictionaryTests and MethodDictionaryTestBis'. >> >> Cyrille can you check on a core image that this is ok? >> Because you were using a dev one so lot of tests refered to classes >> not loaded (RB*....) >> >> Issue 443: Adrian and I have spent some time on fixing the bug. A fix >> has been produced: >> - Kernel-adrian_lienhard.358 in PharoInbox >> - Traits-Alexandre_Bergel.285 contains a test >> >> Now with the Traits package loaded :) >> >> 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

July 21, 2009

Re: [Pharo-project] Persist a morph in a message.

by StÃ©phane Ducasse

Yes I know people that would like to great a bounty and pay to push it. On Jul 21, 2009, at 7:45 AM, Torsten Bergmann wrote: > Mariano wrote: >> Your project seems very interesting, tough. > > Yes, a UI builder would be nice to have. > > Can you give us some more details? > > Thx > Torsten > -- > GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 21, 2009

Re: [Pharo-project] Persist a morph in a message.

by StÃ©phane Ducasse

Yes something like that. Use a system that we can hack and modify (have a look at the VW windowspec) this way your builder to build morphic but also something else too. windowSpec "UIPainter new openOnClass: self andSelector: #windowSpec" <resource: #canvas> ^#(#{UI.FullSpec} #window: #(#{UI.WindowSpec} #properties: #(#{UI.PropertyListDictionary} #sizeType #specifiedSize #positionType #screenCenter #openType #advanced ) #label: #(#{Kernel.UserMessage} #key: #aboutVisualWorks #defaultString: 'About Visual Works' #catalogID: #labels) #min: #(#{Core.Point} 20 20 ) #max: #(#{Core.Point} 1024 768 ) #bounds: #(#{Graphics.Rectangle} 512 384 992 704 ) ) #component: #(#{UI.SpecCollection} #collection: #( #(#{UI.TabControlSpec} #layout: #(#{Graphics.LayoutFrame} 10 0 10 0 -10 1 -40 1 ) #name: #tabs #model: #tabListHolder #labels: #() ) #(#{UI.ActionButtonSpec} #layout: #(#{Graphics.LayoutFrame} -90 1 -35 1 -10 1 -10 1 ) #name: #ok #model: #accept #label: #(#{Kernel.UserMessage} #key: #OK #defaultString: 'OK' #catalogID: #labels) #isDefault: true #defaultable: true ) ) ) ) Stef On Jul 21, 2009, at 2:58 AM, Mariano Martinez Peck wrote: > > > On Mon, Jul 20, 2009 at 7:15 PM, nullPointer <epicfan(a)gmail.com> > wrote: > > Excuse me for my poor english. > > IÂ´m developing a GUI Builder for Pharo -> > http://www.youtube.com/watch?v=CHbc1t83fEI > > One of my problems is the way of persist a morph.Now i use the same > way for > create a Morph than message #saveOnFile but not saving in a > external file > else in array of bytes returned for a #spec message. > > I would know if morphic allow or exists another way of persistence > more > readable and fast. A complex morph serialized of that way is too > slow in > load. > > Perhaps you can use another serializer. Here a some: http://www.seaside.st/documentation/persistence > > For example, http://www.seaside.st/documentation/persistence#230290016 > or http://www.seaside.st/documentation/persistence#40827471 > > Your project seems very interesting, tough. > > Best, > > Mariano > > > > > Regards. > -- > View this message in context: http://n2.nabble.com/Persist-a-morph-in-a-message.-tp3292117p3292117.html > 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 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 21, 2009

Re: [Pharo-project] Persist a morph in a message.

by StÃ©phane Ducasse

Why don't you a kind of literalArray syntax like in VW. Declarative syntax for saving description are the way to go. I would not serialize the composite. You could use mse for example: there are loader and saver for mse in the Fame package I guess. Stef > Excuse me for my poor english. > > IÂ´m developing a GUI Builder for Pharo -> > http://www.youtube.com/watch?v=CHbc1t83fEI > > One of my problems is the way of persist a morph.Now i use the same > way for > create a Morph than message #saveOnFile but not saving in a > external file > else in array of bytes returned for a #spec message. > > I would know if morphic allow or exists another way of persistence > more > readable and fast. A complex morph serialized of that way is too > slow in > load. > > Regards. > -- > View this message in context: http://n2.nabble.com/Persist-a-morph-in-a-message.-tp3292117p3292117.html > 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

July 21, 2009

Re: [Pharo-project] KnownLands: a Class dependency explorer

by StÃ©phane Ducasse

May be you should have a look at Glamour because you can script UI. Stef On Jul 20, 2009, at 11:36 PM, David Goehrig wrote: > On Mon, Jul 20, 2009 at 5:12 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > > wrote: > > Why? > Because you can script your visualization and try all kind of them. > Mondrian a visualisation engine. > Soon with lumiere developed by fernando you will be able to script 3d > objects. > > Because the tools I'm working on are more geared more towards live > editing of classes and object method dictionaries than modeling and > visualization. > > For example, if a circle represents a class's method dictionary, > you can right click on it to see the list of messages associated > with its CompiledMethods. Then you can right click on any of the > CompiledMethods to bring up an editor, and alter the contents of the > method, recompile, and the relationships will change accordingly. > Similarly, you can reorganize methods by dragging and dropping them > into different classes, etc. > > The design and structure of Mondrian makes it terribly difficult to > produce that sort of interface without doing as much work as it > would to just write it from scratch :) > > Dave > > -- > -=-=-=-=-=-=-=-=-=-=- http://blog.dloh.org/ > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 21, 2009