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

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

Re: [Pharo-project] About SqueakDBX

by Mariano Martinez Peck

On Wed, May 4, 2011 at 2:30 PM, Nicolas Petton <petton.nicolas(a)gmail.com>wrote: > Hi Mariano, > Hi Nicolas. Please, let me answer in the mailing list so that other can benefit also. > > I was wondering what can SqueakDBX do. http://www.squeakdbx.org/ here you have all you will probably need. In summary, it is a database driver. Like ODBC or like any other wrapper. The good thing is that it provides the same API to all databases and since there is no SQL conversion, you can exploit the benefits of each database. SqueakDBX delegates to the C library OpenDBX, which delegates to the C database client library. So...the "worst" thing of SqueakDBX is that you need the OpenDBX library and the database client libraries. This is explained here: http://www.squeakdbx.org/Architecture%20and%20desing Features: http://www.squeakdbx.org/Targets%20and%20Features Documentation: http://www.squeakdbx.org/documentation > How stable/scalable is it? Is > SqueakDBX itself is really stable. It is being used in several production apps without problems. The only tricky (depending on the OS and database) is to install OpenDBX + client libraries. But once it is working, is really stable. > there an ORM on top of it? > > Yes, it is called GlorpDBX, which is a modified version of the Glorp port to squeak (which was all hardcoded to the postgresql native driver). That version is a little old and we only make it work for PostgreSQL, Oracle, MySQL and MSSQL. However, ESUG has sponsored again. The project is being renamed to DBXTalk and the team (the students) are working in two important things: 1) new port (with the latest code) from Glorp of VW to pharo. And try to automatize the process for the future. 2) new mapping tool on top of squeakDBX but much simpler than Glorp. Something like ActiveRecord or SandstoneDB. The main idea for now is to use Magritte for describing the mappings. These two things are just starting.....so you will have to wait ;) -- Mariano http://marianopeck.wordpress.com

May 4, 2011

Re: [Pharo-project] RFC: PluggableTextMorphWithLimits

by Benjamin

Yes, sadly you're right ... The global idea is to have metrics ran on the fly, with a visible impact. Because I'm not a metric expert at all, calculating the number of characters is a bit (too) simplistic, but if programers play the game, it could be useful I think :) Thank you for your feedback Ben On May 4, 2011, at 2:07 PM, Nicolas Cellier wrote: > I think the idea is interesting. > However, this is to be confirmed by further experiments. > > Humans are very good at adapting their strategy, and one adaptation > could be to shrink names like this: > | aa | > aa := ... > instead of > | allAnscestors | > allAncestors := ... > Definitely not the original goal... > > Nicolas > > > 2011/5/4 Benjamin <benjamin.vanryseghem.pharo(a)gmail.com>: >> In fact, I ant to know if the limit is negative or not because if it's, so it just act like a classic PluggableTextMorph ( if the same text morph is used to display source code and comments, you do not want to restrict comment size ). >> >> But I could use a boolean instead, it was just a first release to know if the concept is cool enough to be used :) >> >> >> Thanks for your feedback :) >> >> >> Ben >> >> On May 4, 2011, at 1:05 PM, Fernando Olivero wrote: >> >>> Hi Ben, its a cool idea. To use this physiological "stress factor" to >>> force developers to stop coding really long method. >>> >>> I looked at the class, i only disliked the statement >>> >>> self warningLimit negative ifTrue:[ ^ self basicColor]. >>> >>> you could do : >>> warningLimit: aNumber >>> warningLimit := aNumber max: 0. >>> >>> Fernando >>> >>> On Wed, May 4, 2011 at 11:18 AM, Benjamin >>> <benjamin.vanryseghem.pharo(a)gmail.com> wrote: >>>> Hello Smalltalkers, >>>> >>>> I'm currently working on new code editing tools, and I've implemented a new subclass of PluggableTextMorph named PluggableTextMorphWithLimits , with a code oriented feature: >>>> >>>> You have a warningLimit ( 350 by default ) and an alertLimit ( 2* warningLimit by default ), and the number of characters of the text displayed is counted ( without space, tabs, cr etc). >>>> >>>> If you are below the warning limit, the background is white ( or the default color ), if you are between warningLimit and alertLimit, the background turn more and more yellow, and if you are above the alertLimit, the background turn orange :) >>>> >>>> After using it for ten minutes, you start shivering when the background turn yellow ;) >>>> >>>> Gofer new >>>> squeaksource: 'Nautilus'; >>>> package: 'PluggableTextMorphWithLimits'; >>>> load. >>>> >>>> You can test it by evaluating: >>>> >>>> PluggableTextMorphWithLimits example. >>>> >>>> I think it will be used by Nautilus, but maybe more code editing tools should used it. >>>> >>>> >>>> Thanks in advance for your feedback :) >>>> >>>> >>>> >>>> Ben >>>> >>> >> >> >> >

May 4, 2011

Re: [Pharo-project] RFC: PluggableTextMorphWithLimits

by Nicolas Cellier

I think the idea is interesting. However, this is to be confirmed by further experiments. Humans are very good at adapting their strategy, and one adaptation could be to shrink names like this: | aa | aa := ... instead of | allAnscestors | allAncestors := ... Definitely not the original goal... Nicolas 2011/5/4 Benjamin <benjamin.vanryseghem.pharo(a)gmail.com>: > In fact, I ant to know if the limit is negative or not because if it's, so it just act like a classic PluggableTextMorph ( if the same text morph is used to display source code and comments, you do not want to restrict comment size ). > > But I could use a boolean instead, it was just a first release to know if the concept is cool enough to be used :) > > > Thanks for your feedback :) > > > Ben > > On May 4, 2011, at 1:05 PM, Fernando Olivero wrote: > >> Hi Ben, its a cool idea. To use this physiological "stress factor" to >> force developers to stop coding really long method. >> >> I looked at the class, i only disliked the statement >> >> self warningLimit negative ifTrue:[ ^ self basicColor]. >> >> you could do : >> warningLimit: aNumber >> Â warningLimit := aNumber max: 0. >> >> Fernando >> >> On Wed, May 4, 2011 at 11:18 AM, Benjamin >> <benjamin.vanryseghem.pharo(a)gmail.com> wrote: >>> Hello Smalltalkers, >>> >>> I'm currently working on new code editing tools, and I've implemented a new subclass of PluggableTextMorph named PluggableTextMorphWithLimits , with a code oriented feature: >>> >>> You have a warningLimit ( 350 by default ) and an alertLimit ( 2* warningLimit by default ), and the number of characters of the text displayed is counted ( without space, tabs, cr etc). >>> >>> If you are below the warning limit, the background is white ( or the default color ), if you are between warningLimit and alertLimit, the background turn more and more yellow, and if you are above the alertLimit, the background turn orange :) >>> >>> After using it for ten minutes, you start shivering when the background turn yellow ;) >>> >>> Â Â Â Â Gofer new >>> Â Â Â Â Â Â Â Â squeaksource: 'Nautilus'; >>> Â Â Â Â Â Â Â Â package: 'PluggableTextMorphWithLimits'; >>> Â Â Â Â Â Â Â Â load. >>> >>> You can test it by evaluating: >>> >>> PluggableTextMorphWithLimits example. >>> >>> I think it will be used by Nautilus, but maybe more code editing tools should used it. >>> >>> >>> Thanks in advance for your feedback :) >>> >>> >>> >>> Ben >>> >> > > >

May 4, 2011

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

by laurent laffont

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 <http://www.blogger.com/profile/04492856362620588522> has left a new comment on your post "SandstoneDb, simple ActiveRecord style persistence...<http://www.pharocasts.com/2010/04/sandstonedb-simple-activerecord-style.html>": 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 <http://www.pharocasts.com/> at May 4, 2011 4:37 AM

May 4, 2011

Re: [Pharo-project] Just starting out

by Igor Stasenko

On 4 May 2011 09:58, Toon Verwaest <toon.verwaest(a)gmail.com> wrote: > On 05/04/2011 09:53 AM, Sven Van Caekenberghe wrote: >> >> On 04 May 2011, at 09:41, Toon Verwaest wrote: >> >>> On 05/04/2011 07:20 AM, StÃ©phane Ducasse wrote: >>>> >>>> this is because they are forced to do so because of a new law in the us >>>> about crypto. >>>> Believe they do not like that. >>> >>> What law is that, and why? Sounds interesting :) >> >> http://en.wikipedia.org/wiki/Export_of_cryptography_in_the_United_States >> >> Basically, encryption is a weapon. >> >> Sven > > Uncrackable encryption will allow drug lords, spies, terrorists and even > violent gangs to communicate about their crimes and their conspiracies with > impunity. We will lose one of the few remaining vulnerabilities of the worst > criminals and terrorists upon which law enforcement depends to successfully > investigate and often prevent the worst crimes. > For this reason, the law enforcement community is unanimous in calling for a > balanced solution to this problem. > hahaha.. what a moronic excuse. "We don't want you to be able to encrypt your data, because you might be a terrorist" but actually: "We don't want you to be able to encrypt your data, because then we can't watch over you and your private life" :) > Seriously? ROFL > So soon you can't ssh to the states anymore? :) > > -- Best regards, Igor Stasenko AKA sig.

May 4, 2011