- Pharo-dev - lists.pharo.org

Re: [Pharo-project] PharoCore 1.3 built stalled

by Igor Stasenko

On 4 May 2011 17:11, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > On Wed, May 4, 2011 at 5:04 PM, Gary Chambers <gazzaguru2(a)btinternet.com> > wrote: >> >> Of course, now, we get no warning of being unable to write to the changes >> file... >> (e.g. when starting a second invocation of Pharo...) >> > > Once (at brussels Sprint) I suggested Igor to change the headless UIMAnager > so that if receives iteration, instead (or maybe in addition) to throwing an > error, to log somewhere (kind of Transcipt in file) about such event. Maybe > it is worth it... > headless ui manager logs all errors, warnings and notices to PharoDebug.log > >> >> Regards, Gary >> >> ----- Original Message ----- From: "Igor Stasenko" <siguctua(a)gmail.com> >> To: <Pharo-project(a)lists.gforge.inria.fr> >> Sent: Tuesday, May 03, 2011 2:52 AM >> Subject: Re: [Pharo-project] PharoCore 1.3 built stalled >> >> >> On 3 May 2011 00:49, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> >>> it is my fault but I have no idea how to solve it. >>> A package was loading over an already existing one and you get a pop up. >>> >> >> i have a fix for it. >> See #4075 >> >> it makes sure that no matter what current UI manager you using >> (running image headless or not) >> a system startup (all classes startup) is _always_ performed using >> non-interactive UI manager. >> >> So, since CommandLine file-in scripts during startup, this will make >> sure that it will run non-interactively. >> >> >>> Stef >>> >>> On May 2, 2011, at 11:39 PM, Igor Stasenko wrote: >>> >>>> On 2 May 2011 23:26, Igor Stasenko <siguctua(a)gmail.com> wrote: >>>>> >>>>> On 2 May 2011 23:13, laurent laffont <laurent.laffont(a)gmail.com> wrote: >>>>>> >>>>>> Last built started more than 1 day ago and not finished .... >>>>>> Laurent. >>>>> >>>>> This is not good. I killed the jobs. Lets see if it will repeat again. >>>>> >>>> >>>> Okay the problem is that there is a warning and it is handled by >>>> MorphicUIManager, >>>> instead of NonInteractiveUIManager which just forcing it to always >>>> proceed, while morphic one >>>> expects user to press proceed or abandon. >>>> >>>> So, the problem is with an update of >>>> progressTitle: 'Loading 13179-Pha-PlentyOfCleans...' >>>> >>>> >>>> But i don't undestand why it not switched to NonInteractiveUIManager >>>> at image startup. >>>> Aha.. i guess i know why. >>>> Is its not because command line stuff that are triggered at image >>>> startup, which tries to evaluate some code >>>> before full startup procedure completes? >>>> >>>> A command line , i think should be changed to start loading external >>>> code only after >>>> everything else is started (including UI manager). >>>> Otherwise we will have problems like that. >>>> >>>>> -- >>>>> Best regards, >>>>> Igor Stasenko AKA sig. >>>>> >>>> >>>> >>>> >>>> -- >>>> Best regards, >>>> Igor Stasenko AKA sig. >>>> >>> >>> >>> >> >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> >> > > > > -- > Mariano > http://marianopeck.wordpress.com > > -- Best regards, Igor Stasenko AKA sig.

May 4, 2011

Re: [Pharo-project] PharoCore 1.3 built stalled

by Igor Stasenko

On 4 May 2011 17:04, Gary Chambers <gazzaguru2(a)btinternet.com> wrote: > Of course, now, we get no warning of being unable to write to the changes > file... > (e.g. when starting a second invocation of Pharo...) > which is never shown properly , because it was "shown" before morphic initialized. To fix that, it should use #addDeferredUIMessage: to inform user, when UI is ready to work after startup is complete. But apparently not in the middle of startup, when you cannot clearly tell, if its already safe to make any calls to morphic or not.. > Regards, Gary > > ----- Original Message ----- From: "Igor Stasenko" <siguctua(a)gmail.com> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Tuesday, May 03, 2011 2:52 AM > Subject: Re: [Pharo-project] PharoCore 1.3 built stalled > > > On 3 May 2011 00:49, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >> it is my fault but I have no idea how to solve it. >> A package was loading over an already existing one and you get a pop up. >> > > i have a fix for it. > See #4075 > > it makes sure that no matter what current UI manager you using > (running image headless or not) > a system startup (all classes startup) is _always_ performed using > non-interactive UI manager. > > So, since CommandLine file-in scripts during startup, this will make > sure that it will run non-interactively. > > >> Stef >> >> On May 2, 2011, at 11:39 PM, Igor Stasenko wrote: >> >>> On 2 May 2011 23:26, Igor Stasenko <siguctua(a)gmail.com> wrote: >>>> >>>> On 2 May 2011 23:13, laurent laffont <laurent.laffont(a)gmail.com> wrote: >>>>> >>>>> Last built started more than 1 day ago and not finished .... >>>>> Laurent. >>>> >>>> This is not good. I killed the jobs. Lets see if it will repeat again. >>>> >>> >>> Okay the problem is that there is a warning and it is handled by >>> MorphicUIManager, >>> instead of NonInteractiveUIManager which just forcing it to always >>> proceed, while morphic one >>> expects user to press proceed or abandon. >>> >>> So, the problem is with an update of >>> progressTitle: 'Loading 13179-Pha-PlentyOfCleans...' >>> >>> >>> But i don't undestand why it not switched to NonInteractiveUIManager >>> at image startup. >>> Aha.. i guess i know why. >>> Is its not because command line stuff that are triggered at image >>> startup, which tries to evaluate some code >>> before full startup procedure completes? >>> >>> A command line , i think should be changed to start loading external >>> code only after >>> everything else is started (including UI manager). >>> Otherwise we will have problems like that. >>> >>>> -- >>>> Best regards, >>>> Igor Stasenko AKA sig. >>>> >>> >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >>> >> >> >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > > > -- Best regards, Igor Stasenko AKA sig.

May 4, 2011

Re: [Pharo-project] new Cog VMs uploaded

by Chris Cunningham

You should be able to extract the code and use it in Pharo/Squeak without issue, even if it is GPL. What you can't do is include it in the distribution, since it isn't MIT. You also shouldn't study the code and write your own version of it - I believe that would be a derivative work, which would likely make it a GPL derivative. However, if it was extracted, and you brought it in to do profiling, and then removed it afterwards, that shouldn't be an issue at all. Just remember to remove it after you no longer need it - that way the GPL code won't accidentally creep into the Pharo/Squeak code-base. Basically, this would be a great example of a project that should be an external project and not part of core (or dev). -Chris

May 4, 2011

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

by Lemuus

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] PharoCore 1.3 built stalled

by Mariano Martinez Peck

On Wed, May 4, 2011 at 5:04 PM, Gary Chambers <gazzaguru2(a)btinternet.com>wrote: > Of course, now, we get no warning of being unable to write to the changes > file... > (e.g. when starting a second invocation of Pharo...) > > Once (at brussels Sprint) I suggested Igor to change the headless UIMAnager so that if receives iteration, instead (or maybe in addition) to throwing an error, to log somewhere (kind of Transcipt in file) about such event. Maybe it is worth it... > Regards, Gary > > ----- Original Message ----- From: "Igor Stasenko" <siguctua(a)gmail.com> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Tuesday, May 03, 2011 2:52 AM > Subject: Re: [Pharo-project] PharoCore 1.3 built stalled > > > > On 3 May 2011 00:49, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> it is my fault but I have no idea how to solve it. >> A package was loading over an already existing one and you get a pop up. >> >> > i have a fix for it. > See #4075 > > it makes sure that no matter what current UI manager you using > (running image headless or not) > a system startup (all classes startup) is _always_ performed using > non-interactive UI manager. > > So, since CommandLine file-in scripts during startup, this will make > sure that it will run non-interactively. > > > Stef >> >> On May 2, 2011, at 11:39 PM, Igor Stasenko wrote: >> >> On 2 May 2011 23:26, Igor Stasenko <siguctua(a)gmail.com> wrote: >>> >>>> On 2 May 2011 23:13, laurent laffont <laurent.laffont(a)gmail.com> wrote: >>>> >>>>> Last built started more than 1 day ago and not finished .... >>>>> Laurent. >>>>> >>>> >>>> This is not good. I killed the jobs. Lets see if it will repeat again. >>>> >>>> >>> Okay the problem is that there is a warning and it is handled by >>> MorphicUIManager, >>> instead of NonInteractiveUIManager which just forcing it to always >>> proceed, while morphic one >>> expects user to press proceed or abandon. >>> >>> So, the problem is with an update of >>> progressTitle: 'Loading 13179-Pha-PlentyOfCleans...' >>> >>> >>> But i don't undestand why it not switched to NonInteractiveUIManager >>> at image startup. >>> Aha.. i guess i know why. >>> Is its not because command line stuff that are triggered at image >>> startup, which tries to evaluate some code >>> before full startup procedure completes? >>> >>> A command line , i think should be changed to start loading external >>> code only after >>> everything else is started (including UI manager). >>> Otherwise we will have problems like that. >>> >>> -- >>>> Best regards, >>>> Igor Stasenko AKA sig. >>>> >>>> >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >>> >>> >> >> >> > > > -- > Best regards, > Igor Stasenko AKA sig. > > > -- Mariano http://marianopeck.wordpress.com

May 4, 2011

Re: [Pharo-project] PharoCore 1.3 built stalled

by Gary Chambers

Of course, now, we get no warning of being unable to write to the changes file... (e.g. when starting a second invocation of Pharo...) Regards, Gary ----- Original Message ----- From: "Igor Stasenko" <siguctua(a)gmail.com> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Tuesday, May 03, 2011 2:52 AM Subject: Re: [Pharo-project] PharoCore 1.3 built stalled On 3 May 2011 00:49, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > it is my fault but I have no idea how to solve it. > A package was loading over an already existing one and you get a pop up. > i have a fix for it. See #4075 it makes sure that no matter what current UI manager you using (running image headless or not) a system startup (all classes startup) is _always_ performed using non-interactive UI manager. So, since CommandLine file-in scripts during startup, this will make sure that it will run non-interactively. > Stef > > On May 2, 2011, at 11:39 PM, Igor Stasenko wrote: > >> On 2 May 2011 23:26, Igor Stasenko <siguctua(a)gmail.com> wrote: >>> On 2 May 2011 23:13, laurent laffont <laurent.laffont(a)gmail.com> wrote: >>>> Last built started more than 1 day ago and not finished .... >>>> Laurent. >>> >>> This is not good. I killed the jobs. Lets see if it will repeat again. >>> >> >> Okay the problem is that there is a warning and it is handled by >> MorphicUIManager, >> instead of NonInteractiveUIManager which just forcing it to always >> proceed, while morphic one >> expects user to press proceed or abandon. >> >> So, the problem is with an update of >> progressTitle: 'Loading 13179-Pha-PlentyOfCleans...' >> >> >> But i don't undestand why it not switched to NonInteractiveUIManager >> at image startup. >> Aha.. i guess i know why. >> Is its not because command line stuff that are triggered at image >> startup, which tries to evaluate some code >> before full startup procedure completes? >> >> A command line , i think should be changed to start loading external >> code only after >> everything else is started (including UI manager). >> Otherwise we will have problems like that. >> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >>> >> >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> > > > -- Best regards, Igor Stasenko AKA sig.

May 4, 2011

Re: [Pharo-project] Pharocast ContactManager using SandstoneDb

by Bernat Romagosa

Also, images can get corrupted, crash, etc. 2011/5/4 Miguel CobÃ¡ <miguel.coba(a)gmail.com> > The difference is that saving the whole image is a longer operation that > just saving a couple records when they are directed to do so. In a image > with little activity this difference can be almost null but in a heavy > accessed image with a lot of data being created, the difference in times > is notorious. > Also, the image save is blocking AFAIK and during image saving the > responsiveness is greatly diminished. > > Cheers > > El miÃ©, 04-05-2011 a las 04:36 -0700, Jeff Gray escribiÃ³: > > Kind of on topic as you're talking about sandstone....Since all records > are > > loaded at start up, is there an advantage of using sandstonedb for > > persistence over just saving the image? > > > > -- > > View this message in context: > http://forum.world.st/Re-Pharocast-ContactManager-using-SandstoneDb-tp34934… > > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > > > -- > Miguel CobÃ¡ > http://twitter.com/MiguelCobaMtz > http://miguel.leugim.com.mx > > > > >

May 4, 2011

Re: [Pharo-project] Pharocast ContactManager using SandstoneDb

by Miguel CobÃ¡

The difference is that saving the whole image is a longer operation that just saving a couple records when they are directed to do so. In a image with little activity this difference can be almost null but in a heavy accessed image with a lot of data being created, the difference in times is notorious. Also, the image save is blocking AFAIK and during image saving the responsiveness is greatly diminished. Cheers El miÃ©, 04-05-2011 a las 04:36 -0700, Jeff Gray escribiÃ³: > Kind of on topic as you're talking about sandstone....Since all records are > loaded at start up, is there an advantage of using sandstonedb for > persistence over just saving the image? > > -- > View this message in context: http://forum.world.st/Re-Pharocast-ContactManager-using-SandstoneDb-tp34934… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > -- Miguel CobÃ¡ http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

May 4, 2011

Re: [Pharo-project] [Vm-dev] Fwd: System time

by btc＠openInWorld.com

May 4, 2011

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

by CÃ©drick BÃ©ler

maybe the initialization can be done in the inspector by iterating over all instances that have some instances set to nil... (MyObject allInstances select: [:ea | ea createdOn isNil]) do: [:ea | ea initInstVarsFromSDFramework] where initInstVarsFromSDFramework would be somethin like super initialize + maybe some tweaks on createdOn... SDActiveRecord>> initialize super initialize. id := UUID new asString36. createdOn := updatedOn := DateAndTime now. version := 0. isNew := true hth, CÃ©drick

May 4, 2011