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

Re: [Pharo-project] why (UIManager default newPluggableDialogWindow:'Pharo is cool') openInWorld

by StÃ©phane Ducasse

On Jun 20, 2011, at 11:11 AM, Gary Chambers wrote: > Because TEasilyThemed is designed to be applied to Morph subclasses... > So when self (aMorphicUIManager) is passed to the theme it does not understand all Morph protocol. Yes I saw but I still wonder why this is needed to "copy" all these protocols. > > Regards, Gary > > ----- Original Message ----- From: "stephane ducasse" <stephane.ducasse(a)free.fr> > To: "An open mailing list to discuss any topics related to an open-sourceSmalltalk" <Pharo-project(a)lists.gforge.inria.fr> > Sent: Saturday, June 18, 2011 6:58 PM > Subject: [Pharo-project] why (UIManager default newPluggableDialogWindow:'Pharo is cool') openInWorld > > >> why >> >> (UIManager default >> newPluggableDialogWindow: 'Pharo is cool') openInWorld >> >> does not work? >> Apparently MorphicUIManager is missing something? >> Stef > >

June 20, 2011

Re: [Pharo-project] Draft chapter on Settings Framework for PBE2 now online

by StÃ©phane Ducasse

Thanks alain! Great idea! On Jun 20, 2011, at 8:36 AM, Alain Plantec wrote: > Hi Hernan, > > First you have to declare your own keyword. > To do that, extend SettingTreeBuilder for your application by > adding a #myAppSettings method. > > SettingTreeBuilder>>myAppSettings > <settingPragmaProcessor> > "Process a <myAppSettings> pragma" > currentPragma methodClass theNonMetaClass perform: currentPragma selector with: self. > > > Then you can use <myAppSettings> as you do with <systemsettings> for the settings declarations. > In order to open the SettingBrowser, just indicate the keywords you want: > (SettingBrowser browse: #('myAppSettings' 'systemsettings')) > or > (SettingBrowser browse: #('myAppSettings' )) > > I will update the settings chapter with that. > Cheers > Alain > > > > Le 20/06/2011 00:18, HernÃ¡n Morales Durand a Ã©crit : >> Hi Oscar, >> >> I would like to build my own application settings in a separated >> Settings browser, can I use<myAppSettings> like the<systemsettings> >> pragma? any example code how to do it? >> >> Cheers, >> >> 2011/2/8 Oscar Nierstrasz<oscar.nierstrasz(a)gmail.com>: >>> Hi Folks, >>> >>> There is now a draft chapter on the Settings Framework for "Pharo by Example 2" available for review: >>> >>> https://gforge.inria.fr/frs/download.php/28243/Settings.pdf >>> >>> http://pharobyexample.org/ >>> >>> Cheers, >>> - on >>> >>> >>> > >

June 20, 2011

Re: [Pharo-project] About not using full Pharo

by laurent laffont

Personally I'm tired of loading the tools / frameworks I use in Pharo. I would like to take time to setup my own Hudson. I think it's normal that a lot of people needs its own "One Click" with latest pharo/vm/tools they use, just because we can do it. Would be cool to have an open CI platform so people can register their own config. 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 On Mon, Jun 20, 2011 at 10:53 AM, Bernat Romagosa < tibabenfortlapalanca(a)gmail.com> wrote: > I'm a One-Click user! > > I use most of the tools included by default (finder, OB, autocompletion, > etc), plus I add a couple more to my images (newInspector, multipleWorlds, > etc). > > Cheers! > > 2011/6/20 Damien Cassou <damien.cassou(a)gmail.com> > >> On Mon, Jun 20, 2011 at 6:56 AM, Lukas Renggli <renggli(a)gmail.com> wrote: >> >> I've read that some of you are installing their own set of packages on >> >> top of Pharo-Core and not using Pharo. Why is that so? What don't you >> >> like in Pharo? Why didn't you tell us before? >> > >> > Uhh? Don't tell me you didn't know? All images I build on my Jenkins >> > are based on PharoCore since we setup that infrastructure. >> >> >> You are right, I knew about you :-) >> >> >> > Since the beginning of 2011, 3757 of my images were downloaded from >> > people other than me. Not sure who this is, why they do it, and if >> > this number is any significant? Maybe it helps you for your >> > statistics? >> >> I often use your images to get the latest Pier and Seaside. >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> "Lambdas are relegated to relative obscurity until Java makes them >> popular by not having them." James Iry >> >> >

June 20, 2011

[Pharo-project] [TODO] 1.3

by Marcus Denker

Open Issues in Core: ================= Issue 4328: Transcript: 5) Update problem when evaluating 1 to: 30 do: [: x | Transcript cr; show: x. (Delay forSeconds: 0.2) wait.]. Issue 4329: Transcript: 4) clear on cmd-s Issue 4417: Zinc does not honour network proxy configuration.... Issue 4424: Can't execute comment in Finder http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D1.3 Open Issues in Full: ================ Issue 4390: OCompletion does not respect #enabled setting; it has no "off switch" Issue 4394: GoferApiTest >> testRepositoryErrors fails in Full but not in Core http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D1.3-DevImage -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

June 20, 2011

Re: [Pharo-project] addCloseBox

by Gary Chambers

I do get a close box, just the default window size is a bit too small to see it well (resize). Regards, Gary ----- Original Message ----- From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> To: "An open mailing list to discuss any topics related to an open-sourceSmalltalk" <Pharo-project(a)lists.gforge.inria.fr> Sent: Saturday, June 18, 2011 8:12 PM Subject: [Pharo-project] addCloseBox > Hi > > does anybody have an idea why the close box does not get added? > > (PluggableDialogWindow new > title: 'Pharo is cool'; > addCloseBox) openInWorld > > Stef > >

June 20, 2011

Re: [Pharo-project] why (UIManager defaultnewPluggableDialogWindow: 'Pharo is cool') openInWorld

by Gary Chambers

Just the parenthesis placement... (UITheme builder newPluggableDialogWindow: 'Pharo is cool' for: (RectangleMorph new)) beUnresizeable; openInWorld Regards, Gary ----- Original Message ----- From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Saturday, June 18, 2011 8:02 PM Subject: Re: [Pharo-project] why (UIManager defaultnewPluggableDialogWindow: 'Pharo is cool') openInWorld On Jun 18, 2011, at 7:58 PM, stephane ducasse wrote: > why > > (UIManager default > newPluggableDialogWindow: 'Pharo is cool') openInWorld > > does not work? > Apparently MorphicUIManager is missing something? > Stef > (ExampleBuilderMorph new newPluggableDialogWindow: 'Pharo is cool') openInWorld is working because ExampleBuilderMorph inherits from Morph and not from Object (UITheme builder newPluggableDialogWindow: 'Pharo is cool'; minimumExtent: 200@300) openInWorld similarly. Now there is something that I do not understand. What is the use of the builder since I cannot pass it specific setting (UITheme builder newPluggableDialogWindow: 'Pharo is cool' for: (RectangleMorph new); beUnresizeable <<< does not work because the builder (a ComposableMorph does not pass such setting to the PluggableDialogWindow. ) openInWorld I would really like to have a nice kernel that support well such approach. In fact I imagine that we should not use UITheme builder that way. Stef

June 20, 2011

Re: [Pharo-project] why (UIManager default newPluggableDialogWindow:'Pharo is cool') openInWorld

by Gary Chambers

Because TEasilyThemed is designed to be applied to Morph subclasses... So when self (aMorphicUIManager) is passed to the theme it does not understand all Morph protocol. Regards, Gary ----- Original Message ----- From: "stephane ducasse" <stephane.ducasse(a)free.fr> To: "An open mailing list to discuss any topics related to an open-sourceSmalltalk" <Pharo-project(a)lists.gforge.inria.fr> Sent: Saturday, June 18, 2011 6:58 PM Subject: [Pharo-project] why (UIManager default newPluggableDialogWindow:'Pharo is cool') openInWorld > why > > (UIManager default > newPluggableDialogWindow: 'Pharo is cool') openInWorld > > does not work? > Apparently MorphicUIManager is missing something? > Stef >

June 20, 2011

Re: [Pharo-project] Fuel - a fast object deployment tool

by Henrik Sperre Johansen

On 08.12.2010 17:50, Martin Dias wrote: > Hi all > > Last months I and Tristan have been working on Fuel project, an object > binary serialization tool. The idea is that objects are much more > times loaded than stored, therefore it is worth to spend time while > storing in order to have faster loading and user experience. We > present an implementation of a pickle format that is based on > clustering similar objects. > > There is a summary of the project below, but more complete information > is available here: http://rmod.lille.inria.fr/web/pier/software/Fuel > > The implementation still needs a lot of work to be really useful, > optimizations should be done, but we'll be glad to get feedback of the > community. > > > = Pickle format = > > The pickle format and the serialization algorithm main idea, is > explained in this slides: > > http://www.slideshare.net/tinchodias/fuel-serialization-in-an-example > > > = Current features = > > - Class shape changing (when a variable has been added, or removed, or > its index changed) > - Serialize most of the basic objects. > - Serialize (almost) any CompiledMethod > - Detection of global or class variables > - Support for cyclic object graphs > - Tests > > > = Next steps = > > - Improve version checking. > - Optimize performance. > - Serialize more kinds of objects: > -- Class with its complete description. > -- Method contexts > -- Active block closures > -- Continuation > - Some improvements for the user: > -- pre and post actions to be executed. > -- easily say 'this object is singleton'. > - Partial loading of a stored graph. > - Fast statistics/brief info extraction of a stored graph. > - ConfigurationOfFuel. > - Be able to deploy materialization behavior only (independent from > the serialization behavior) > > > = Download = > > In a Pharo 1.1 or 1.1.1 evaluate: > > Gofer new > squeaksource: 'Fuel'; > version: 'Fuel-MartinDias.74'; > version: 'FuelBenchmarks-MartinDias.4'; > load. > > > = Benchmarks = > > You can run benchmarks executing this line (results in Transcript): > > FLBenchmarks newBasic run. > > > Thank you! > Martin Dias One thing I do not see mentioned, and feel could use some attention, is thread safety. (aka other threads altering the graph you are serializing) The classic answer would of course be "always run FUEL at highest priority", but if we ever want to move to true multi-core, that's not enough. What would be neat is protecting all mutation of objects in the graph with a Mutex/Monitor whose critical section covers the analysis and serialization, i.e. blocking all other processes that wants to mutate objects in the graph untill serialization is complete. Aside from the behaviour when a marked object is encountered, the process is the same as for immutability, as discussed here: http://forum.world.st/immutability-and-become-Was-Re-squeak-dev-immutabilit… You could do this image-side as part of the analyze phase, as Eliot's post suggests, but it's not entirely safe when: A child -> B B parent -> A 1 . Process1 protects A with Mutex 2. Process2 calls method on B which does: a) B parent: C b) (B's tmpRef to A) child: somethingElse *Wait for Mutex* 3. Process 1 makes B, C immutable, serializes B with C as parent. 4. Process2 changes A child. It could of course be argued that is a programming/logic error to update B parent ref before child ref in A, (you'd actually have to do extra work to get that order), still it's a hard one to debug if it does happen. (Note to the thread: Following the same logic, I would also say it should be considered an error to keep a mutable cache as part of an immutable object :) ) In fact, you *could* implement it with immutability, injecting handler contexts with behaviour as described above into existing/new processes for any resulting immutability errors. Cheers, Henry

June 20, 2011

Re: [Pharo-project] About not using full Pharo

by Bernat Romagosa

I'm a One-Click user! I use most of the tools included by default (finder, OB, autocompletion, etc), plus I add a couple more to my images (newInspector, multipleWorlds, etc). Cheers! 2011/6/20 Damien Cassou <damien.cassou(a)gmail.com> > On Mon, Jun 20, 2011 at 6:56 AM, Lukas Renggli <renggli(a)gmail.com> wrote: > >> I've read that some of you are installing their own set of packages on > >> top of Pharo-Core and not using Pharo. Why is that so? What don't you > >> like in Pharo? Why didn't you tell us before? > > > > Uhh? Don't tell me you didn't know? All images I build on my Jenkins > > are based on PharoCore since we setup that infrastructure. > > > You are right, I knew about you :-) > > > > Since the beginning of 2011, 3757 of my images were downloaded from > > people other than me. Not sure who this is, why they do it, and if > > this number is any significant? Maybe it helps you for your > > statistics? > > I often use your images to get the latest Pier and Seaside. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Lambdas are relegated to relative obscurity until Java makes them > popular by not having them." James Iry > >

June 20, 2011

Re: [Pharo-project] About not using full Pharo

by Damien Cassou

On Mon, Jun 20, 2011 at 6:56 AM, Lukas Renggli <renggli(a)gmail.com> wrote: >> I've read that some of you are installing their own set of packages on >> top of Pharo-Core and not using Pharo. Why is that so? What don't you >> like in Pharo? Why didn't you tell us before? > > Uhh? Don't tell me you didn't know? All images I build on my Jenkins > are based on PharoCore since we setup that infrastructure. You are right, I knew about you :-) > Since the beginning of 2011, 3757 of my images were downloaded from > people other than me. Not sure who this is, why they do it, and if > this number is any significant? Maybe it helps you for your > statistics? I often use your images to get the latest Pier and Seaside. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

June 20, 2011