May 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [Pharo-users] [Pharocasts] New comment on SandstoneDb, simple ActiveRecord style persistence....

by StÃ©phane Ducasse

something that would be good is to have SActiveRecord as a trait like in SqueakSave this way no need to change the superclass definition of your domain to save your objects. Stef On May 4, 2011, at 9:01 PM, laurent laffont wrote: > On Wed, May 4, 2011 at 7:00 PM, Ramon Leon <ramon.leon(a)gmail.com> wrote: > My general approach would be this sequence of steps, let's assume his > class is called Person in collection var name people. > > If Person has an initialize method, rename it to initializeOld. > Change superclass of Person to SDActiveRecord. > Person warmUp. to setup the store for this new class. > people do: [:e | e initialize ] to invoke active records initialize > setting up it's necessary inst vars and marking all people as new > rename Person>>initializeOld back to Person>>initialize. > people do: [:e | e save ] > > Migration complete. > > > > Thanks a lot Ramon, I add this to Pharocasts. > > Laurent > > > -- > Ramon Leon > http://onsmalltalk.com > > > On Wed, May 4, 2011 at 4:58 AM, laurent laffont > <laurent.laffont(a)gmail.com> wrote: > > > > Someone knows ? > > Laurent > > > > > > ---------- Forwarded message ---------- > > From: Bernat Romagosa <noreply-comment(a)blogger.com> > > Date: Wed, May 4, 2011 at 1:37 PM > > Subject: [Pharocasts] New comment on SandstoneDb, simple ActiveRecord style > > persistence.... > > To: laurent.laffont(a)gmail.com > > > > > > Bernat Romagosa has left a new comment on your post "SandstoneDb, simple > > ActiveRecord style persistence...": > > > > I was trying to migrate a simple image-based persistence app into Sandstone, > > so I just recompiled my biz objects to be subclasses of SDActiveRecord, but > > of course the objects I want to save are already created and "floating" in > > the image, so when I try to save them I get an error as many instvars > > haven't been initialized upon creating these objects (as they were already > > there). > > > > Is there a way to automatically do this? > > > > Thanks! > > > > Bernat. > > > > > > > > Posted by Bernat Romagosa to Pharocasts at May 4, 2011 4:37 AM > > >

May 4, 2011

Re: [Pharo-project] [Pharo-users] [ANN] PHANtom: A modern Aspect Language for Pharo

by StÃ©phane Ducasse

Thanks for sharing that with us! Stef On May 4, 2011, at 5:32 PM, Lemuus wrote: > Hello all, > > We are happy to announce the release of PHANtom: a modern aspect language for Pharo. > > PHANtom was built taking into account recent advances in aspect language features such as dynamic advice rescheduling, reentrancy management, and scoping strategies for deployment. The advanced features are not all implemented yet, but the 'normal' features work and are well-tested (about 130 unit tests) so we are relasing it to the world for you to try out. We hope PHANtom can help you to solve some cross-cutting code problems. > > An overview of the language can be found at http://pleiad.cl/PHANtom Please try it out, see if it works for you, all your comments are welcome! > > More details: > > I am doing this as my engineering thesis, under the guidance of Prof. Johan Fabry. > > PHANtom works in Pharo 1.2.1 and in 1.3, and also in PharoCore. > > Right now, PHANtom uses Method Wrappers in its' implementation, just like the AspectS language did. But the plan is once we have all features implemented, that we will start compiling using the Opal compiler of Pharo, to make everything go faster. > > I just put one example from the website here so you can see what it looks like: > > asp := PhAspect new > add: (PhAdvice new > pointcut: (PhPointcut new > receivers: 'SystemWindow+'; > selectors: 'position:'; > context: #(#receiver #arguments)); > advice: [:context | > Transcript show: context receiver. > Transcript show: ' moved to: '. > Transcript show: context arguments; cr.]; > type: #after). > asp install. > > Note: the unit tests of pointcuts take a large amount of time to execute, as some of them match on everything in the image. > > For more info and how to download PHANtom see http://pleiad.cl/PHANtom

May 4, 2011

Re: [Pharo-project] Nile tests red - Pharo 1.3

by Alain_Rastoul

Ok, done. I'll have a look at the last error soon. Regards Alain "Mariano Martinez Peck" <marianopeck(a)gmail.com> a Ã©crit dans le message de news: BANLkTim7ts8650dZvoKFj-JEUhLXCOX-tw(a)mail.gmail.com... On Wed, May 4, 2011 at 10:28 PM, Alain_Rastoul <alr.dev(a)free.fr> wrote: Hi, I have a changeset to fix most tests -all except one at this time- of Nile, most of the red tests are the same errors related to NewParagraph, NSTranscripter, so the changeset is very small but I don't the procedure to submit a fix ? Thanks Alain. For the moment, upload the changeset to the issue tracker. Then, hopefully, someone take a look, and finally it is commited to Nile repo and ConfigurationOfNile is updated. Then, next Pharo build by Hudson will use the new version- Do I add a comment to the issue at code.google with the attached changeset ? http://code.google.com/p/pharo/issues/detail?id=4051 Do someone review the code (as I am new to Pharo and don't know much of Nile , Transcripter ) ? Do someone - ... who? ... - incorporate the changeset in the sources of the package ? I don't know anything about Nile either. Maybe Damien Cassou can review your changes. Thanks -- Mariano http://marianopeck.wordpress.com

May 4, 2011

Re: [Pharo-project] Nile tests red - Pharo 1.3

by Mariano Martinez Peck

On Wed, May 4, 2011 at 10:28 PM, Alain_Rastoul <alr.dev(a)free.fr> wrote: > Hi, > > I have a changeset to fix most tests -all except one at this time- of Nile, > most of the red tests are the same errors related to NewParagraph, > NSTranscripter, so the changeset is very small but I don't the procedure to > submit a fix ? > Thanks Alain. For the moment, upload the changeset to the issue tracker. Then, hopefully, someone take a look, and finally it is commited to Nile repo and ConfigurationOfNile is updated. Then, next Pharo build by Hudson will use the new version- > Do I add a comment to the issue at code.google with the attached changeset > ? > http://code.google.com/p/pharo/issues/detail?id=4051 > > Do someone review the code (as I am new to Pharo and don't know much of > Nile > , Transcripter ) ? > Do someone - ... who? ... - incorporate the changeset in the sources of > the > package ? > I don't know anything about Nile either. Maybe Damien Cassou can review your changes. Thanks -- Mariano http://marianopeck.wordpress.com

May 4, 2011

Re: [Pharo-project] right click on PluggableTreeMorph doesn't select

by Guillermo Polito

No one? :( On Sun, May 1, 2011 at 11:20 PM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > Hi! > > Let's say I have a PluggableTreeMorph with some options(a,b and c). Each > option may show a menu when I do a right click. > Buuut, If I have selected item a, and do a right clic on c, the menu shown > is for a, not for c :(. > > I expect the right click to work on the item the click is done, not in the > selected one :(. > > Is there a way to have this tree morph working as I want? > > Thanks in advance! > Guille >

May 4, 2011

[Pharo-project] Nile tests red - Pharo 1.3

by Alain_Rastoul

Hi, I have a changeset to fix most tests -all except one at this time- of Nile, most of the red tests are the same errors related to NewParagraph, NSTranscripter, so the changeset is very small but I don't the procedure to submit a fix ? Do I add a comment to the issue at code.google with the attached changeset ? http://code.google.com/p/pharo/issues/detail?id=4051 Do someone review the code (as I am new to Pharo and don't know much of Nile , Transcripter ) ? Do someone - ... who? ... - incorporate the changeset in the sources of the package ? TIA Alain

May 4, 2011

[Pharo-project] [update 1.3] #13182

by laurent laffont

13182 ----- COTDC integration - 49 - ClassFactoryWithOrganization - A.Bergel - 50 - LongTestCase (fix waiting for review - issue #4132) - L.Laffont - 51 - TestCaseAnnouncement, TestCaseStarted, TestCaseEnded - A.Bergel - 52 - PCXReadWriter (deprecated) - G.Polito - 53 - AnimatedGIFReadWriter - L.Laffont - 54 - BMPReadWriter - L.Laffont - 55 - IdentityGlyphMap (removed) - L.Laffont - 56 - HostFont (removed) - C.Cunningham - 57 - ColorMap - F.Olivero - 58 - TextPrinter (deprecated) Laurent Laffont - @lolgzs <http://twitter.com/#!/lolgzs> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/ Developer group: http://cara74.seasidehosting.st

May 4, 2011

[Pharo-project] [COTDC] 59 - HierarchicalURI

by laurent laffont

Today: HierarchicalURI Comment Of The Day Contest - One Day One Comment Rules: #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). #2: If you cannot comment it, deprecate it. Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest Laurent

May 4, 2011

Re: [Pharo-project] new Cog VMs uploaded

by Philippe Marschall

On 03.05.2011 23:40, Eliot Miranda wrote: > > > On Tue, May 3, 2011 at 11:57 AM, Philippe Marschall <kustos(a)gmx.net > <mailto:kustos@gmx.net>> wrote: > > On 03.05.2011 19:51, Eliot Miranda wrote: > > > > > > On Sun, May 1, 2011 at 4:38 AM, Philippe Marschall > <kustos(a)gmx.net > <mailto:kustos@gmx.net> > > <mailto:kustos@gmx.net > <mailto:kustos@gmx.net>>> wrote: > > > > On 29.04.2011 19:03, Eliot Miranda wrote: > > > > > > > > > On Fri, Apr 29, 2011 at 9:04 AM, Philippe Marschall > > <kustos(a)gmx.net > <mailto:kustos@gmx.net> > > <mailto:kustos@gmx.net > <mailto:kustos@gmx.net>> > > > <mailto:kustos@gmx.net > <mailto:kustos@gmx.net> > > <mailto:kustos@gmx.net > <mailto:kustos@gmx.net>>>> wrote: > > > > > > On 27.04.2011 19 <tel:27.04.2011%2019> <tel:27.04.2011%2019> > > <tel:27.04.2011%2019>:23, Eliot Miranda wrote: > > > > Philippe, > > > > > > > > can you please profile before and after? This could > > very well > > > be to > > > > do with the additional cost of shallowCopy for > contexts, but > > it is > > > > inevitable that a correct implementation is going to > be more > > expensive > > > > than the simple block-copy. The new implementation can be > > optimized, > > > > but we need to profile first to be sure we're tilting > at the > > relevant > > > > windmill. > > > > > > > > > What kind of profiling do you have in mind, MessageTally? > > > > > > > > > Yes, that would be fine. Thanks! > > > > OK, there you go. As you'll see the runtime is about the same, > that's > > because we do more iterations in the same time. Also note the > time we're > > spending in WriteStream >> #nextPutAll: with interestingly has a > > different growing behavior than WriteStream >> #nextPut: (only > 25% vs > > 100%). I already raised the issue once but people argued that the > > current code is prefect. > > > > > > Hmmm. GC behaviour is very different. Also requestContext Also shows > > up in the 2382 profiles but not the 2370 traces. You'll need to dig a > > little deeper to account for these differences. I guess they > could well > > be to do with the new (correct) MethodContext copying behaviour > > retaining more state and hence stressing the GC more. > > What approach do you suggest should I take? > > > I have no idea. You understand that when I hear these words from a VM guru I get a bit worried about the challenges ahead of me. > You could try and break down the various activities and > benchmark them separately I suppose. You could look at the profiles > you're already generating in higher resolution to see where the time is > going. You could also try and extract the SystemProfiler from OpenQwaq, > which will run on Cog, and is better than MessageTally. Andreas wrote > it to get around some of MessageTally's limitations. It should > hopefully show primitives quite accurately. I'll see what I can do. Cheers Philippe

May 4, 2011

Re: [Pharo-project] [COTDC] 58 - TextPrinter

by laurent laffont

On Tue, May 3, 2011 at 9:21 PM, laurent laffont <laurent.laffont(a)gmail.com>wrote: > Today: TextPrinter > I've seen it has been deprecated on recent PharoCore. Laurent. > > > Comment Of The Day Contest - One Day One Comment > Rules: > #1: Each day a not commented class is elected. Each day the best comment > will be integrated with name of the author(s). > #2: If you cannot comment it, deprecate it. > Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest > > Laurent >

May 4, 2011