- Pharo-dev - lists.pharo.org

Re: [Pharo-project] A lil simplification of MorphTreeNodeMorph

by Tudor Girba

Excellent job :). And very highly appreciated. Cheers, Doru On 6 Apr 2011, at 22:06, StÃ©phane Ducasse wrote: > Good! I'm happy. Igor and Ben are doing a great job. > > Stef > >> This is great! >> >> I tested it on Glamour and it looks pretty cool. And, it is definitely snappier. >> >> I tested LazyMorphTreeMorph it on a list with 1 million items in the context of Glamour with a pagination of 50 items I got: >> - before: 6414 ms >> - after: 3526 ms >> >> The code I used is (works in a Moose image, or after you load Glamour): >> >> Time millisecondsToRun: [ >> | browser | >> browser := GLMTabulator new. >> browser column: #one. >> browser transmit to: #one; andShow: [ :a | >> a tree >> tags: [ :each | {each even printString} ]; >> showOnly: 50 ]. >> browser openOn: (1 to: 1000000) >> ] >> >> Cheers, >> Doru >> >> >> On 6 Apr 2011, at 18:01, Igor Stasenko wrote: >> >>> okay.. i found one bug >>> >>> forgot to add cellPositioning: #leftCenter; for colum wrapper morph >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >>> <Tree2.3.cs> >> >> -- >> www.tudorgirba.com >> >> "What we can governs what we wish." >> >> >> >> > > -- www.tudorgirba.com "Yesterday is a fact. Tomorrow is a possibility. Today is a challenge."

April 6, 2011

[Pharo-project] Issue 3967 in pharo: Announcement enhancement

by pharo＠googlecode.com

Status: Accepted Owner: stephane...(a)gmail.com New issue 3967 by stephane...(a)gmail.com: Announcement enhancement http://code.google.com/p/pharo/issues/detail?id=3967 Both solutions lead to remaining subscribers being notified when an error occurs. So which is decided upon, depends on which of their respective benefits are valued more. For that, it'd be nice if more than 2 people chimed in on. :) Short summary (not guaranteed to be 100% objective) Curtailing -> - Your image may crash in some cases, more specifically if you: 1) have errors in subscribers to announcements made in system-critical processes, as they will be suspended while debugging. 2) deliver announcements in a separate thread from where they're announced, and the announcing thread does so regularily. + Easy to debug. Entire call-chain available, no modification to state caused by subsequent subscribers. Restart should always lead in bug being reproduceable. The remove-from-subscriptions part of Error-handling and ifCurtailed could be combined as well, in which case #2 no longer applies. Error handling -> - Hard/impossible to debug because: 1) If your error was in ordering, debugger will step through flawlessly if restarted. 2) You start at the context of the subscriptions action, no idea where it came from. + More robust, none of the cases mentioned in Curtailing will crash your image. With the different pros/cons mentioned above in mind, here are .cs with example implementations for what both Igor / I would like. (minus remove-from-subscriptions for ifCurtailed: ) Attachments: AnnouncementErrorHandling.zip 1.7 KB

April 6, 2011

Re: [Pharo-project] SmalltalkHub going beta in a week

by Nicolas Petton

Le mercredi 06 avril 2011 Ã 20:30 +0200, Noury Bouraqadi a Ã©crit : > Cool! I guess you didn't you use JTalkST (too young), did you? No, it's too young to be used in real world apps. Maybe in the future ;) cheers, Nico -- Nicolas Petton http://www.nicolas-petton.fr

April 6, 2011

Re: [Pharo-project] Import Package from VW to Pharo

by StÃ©phane Ducasse

Hi glenn What were your problems exactly? We port regularly code from VW for Moose. Now soemtimes we need some manual tweaking. Did you check the mailing-list because this topic was raised recently? Stef > I have a package in VW7.6 that I want to move to Pharo (Windows 7). I tried Fileout30 but could not get it to work. I was thinking of reading the .PST file using the XML parser and then programmatically add classes and methods to Pharo. I've looked at various classes related to Class and am having difficulty getting started. Can anyone provide some pointers? > > Regards, > Glenn

April 6, 2011

Re: [Pharo-project] abouth nautilus and the removal of CodeHolder hierarchy

by StÃ©phane Ducasse

Thanks fernando! this is cool to see some work on this front. We should work step by step. What I wanted to say is that while I value some part of CUIS. Other parts are still old and odd like its ancestor. Pharo is moving on a lot of front and people may not notice it but soon we will have a lot of pieces of the puzzle ready to get real benefit of the infrastructure we are steadily building :). Stef > Thanks Ben and Stef, the answer was in concordance with what i was thinking. > > CUIS already has the TextModel class, and the PluggableTextModel > class. So together with the menu pragma builders of Pharo, they > provide the foundations for the implementation you just nicely > explained. > > Next week, once i finish writing something for my research, i will > finish the initial port. And hopefully provide a working example of > SMx in Pharo, applying the ideas here discussed. A somehow initial > port, which can get expanded gradually, from the list of widgets we > mentioned in previous emails: MorphTreeMorph, etc.. > (and at a final stage Polymorph). > > Fernando > pd: Alex, SMx is SimpleMorph, an older version of the cleaned up > Morphic from the CUIS image. > > > On Wed, Apr 6, 2011 at 6:19 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> YES!YES!YES! >> It is cool to see your impact on them. Excellent it will really helps >> bringing pharo IDE to the next level. >> >> Stef >> >> On Apr 6, 2011, at 2:11 PM, Igor Stasenko wrote: >> >>> On 6 April 2011 13:16, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>>> Because once people are dependent and drug addict then they will spend time fixing it :) >>>> >>>> No seriously this is mega hyper hyper important that we get >>>> - solid scalable listMorph and treeMorph >>>> So the best way is to stress it. >>>> >>>> The second answer is that nautilus is cool and needs tree :) >>>> >>> i second that. >>> trees and lists are basic widgets which could be used for different means. >>> So why we should limit ourselves and use some crappy lists to mimic >>> tree, instead of using trees, and improving this widget and making it >>> work well. >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >>> >> >> >> >

April 6, 2011

Re: [Pharo-project] Metacello chapter

by StÃ©phane Ducasse

> Cool. BTW, I have a pending pull request on the Socket chapter. what is it? what do you mean? what do you need? Stef

April 6, 2011

Re: [Pharo-project] SmalltalkHub going beta in a week

by StÃ©phane Ducasse

> Hi, > > Unless there is a scalability issue, I would not discard anything from squeaksource. I believe the evolution is too valuable to simply drop it. > > But, maybe there are practical reasons. May be we could have a second server where we copy everything there. We will see how we will manage that. The query are important because we can identify created but unused created but dormant created but not used ... and tag them > In any case, the idea of having programatic access is really cool. I would love to use that for analysis purposes. :) I did not guess on that one :) and with the new EyeSee we may expect to have some cool looking infrastructure.

April 6, 2011

Re: [Pharo-project] SmalltalkHub going beta in a week

by StÃ©phane Ducasse

But you have the tool: Gofer :) Stef On Apr 6, 2011, at 6:40 PM, Mariano Martinez Peck wrote: > > > On Wed, Apr 6, 2011 at 6:34 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > Wow, looks great! > > I think it's a good idea to *not* automatically migrate projects from SqueakSource ;). It's an opportunity to get rid of a lot of cruft that has accumulated on SqueakSource during the last years... > > > +1 But providing a tool/script so that we know how to migrate manually our own projects is a nice nice nice wish :) > > > Cheers, > Adrian > > > On Apr 6, 2011, at 13:07 , Tudor Girba wrote: > > > Phenomenal stuff :). I cannot wait to use it. Will there be a possibility to migrate the existing squeaksource there? > > > > Cheers, > > Doru > > > > > > On 6 Apr 2011, at 13:00, Nicolas Petton wrote: > > > >> Hi, > >> > >> We've been working on a new code repository & project management > >> application for Smalltalk with ESUG named SmalltalkHub. > >> > >> If everything goes fine, the app should be in public beta in a week. > >> The source code of SmalltalkHub will be available at the same moment > >> (the project itself is hosted by SmalltalkHub). > >> > >> Here's a screenshot in the meantime. > >> http://nicolas-petton.fr/2011/04/06/smalltalkhub-beta-in-a-week.html > >> > >> Cheers, > >> Nicolas > >> -- > >> Nicolas Petton > >> http://www.nicolas-petton.fr > >> > >> > > > > -- > > www.tudorgirba.com > > > > "Being happy is a matter of choice." > > > > > > > > > > > > > > -- > Mariano > http://marianopeck.wordpress.com >

April 6, 2011

Re: [Pharo-project] A lil simplification of MorphTreeNodeMorph

by StÃ©phane Ducasse

Good! I'm happy. Igor and Ben are doing a great job. Stef > This is great! > > I tested it on Glamour and it looks pretty cool. And, it is definitely snappier. > > I tested LazyMorphTreeMorph it on a list with 1 million items in the context of Glamour with a pagination of 50 items I got: > - before: 6414 ms > - after: 3526 ms > > The code I used is (works in a Moose image, or after you load Glamour): > > Time millisecondsToRun: [ > | browser | > browser := GLMTabulator new. > browser column: #one. > browser transmit to: #one; andShow: [ :a | > a tree > tags: [ :each | {each even printString} ]; > showOnly: 50 ]. > browser openOn: (1 to: 1000000) > ] > > Cheers, > Doru > > > On 6 Apr 2011, at 18:01, Igor Stasenko wrote: > >> okay.. i found one bug >> >> forgot to add cellPositioning: #leftCenter; for colum wrapper morph >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> <Tree2.3.cs> > > -- > www.tudorgirba.com > > "What we can governs what we wish." > > > >

April 6, 2011

[Pharo-project] Import Package from VW to Pharo

by Glenn Swanlund

I have a package in VW7.6 that I want to move to Pharo (Windows 7). I tried Fileout30 but could not get it to work. I was thinking of reading the .PST file using the XML parser and then programmatically add classes and methods to Pharo. I've looked at various classes related to Class and am having difficulty getting started. Can anyone provide some pointers? Regards, Glenn

April 6, 2011