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

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

by Lukas Renggli

> The point is that we should be able to have good tools inside the default system so that we can get faster. > We are fedup to do refactoring of core manually. You have a build server that builds PharoCore and Pharo images immediately and all the time. So, why are you not improving the system in Pharo and immediately let your servers build experimental PharoCore and Pharo images right after you commit? If tests pass the files get propagated and generate the official builds. As long as Pharo packages are clean without any overrides there should be no problem (this is the case with my builds). If you remember, we did together some refactorings while I was visiting you in Lille last year. Lukas -- Lukas Renggli www.lukas-renggli.ch

June 20, 2011

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

by Janko MivÅ¡ek

I'm also a one-click user and I'd like to have out-of-the box most of things for a daily use. In a Pharo named simply Pharo. No Pharo-dev, which already sound scary .. :) If I need more, I'd like to go to something like MetacelloBrowser, search around then one-click load it. And unload if not happy. Current Monticello/SqueakSource combo is way too complex even for me! Best regards Janko S, Bernat Romagosa piÅ¡e: > 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 > <mailto:damien.cassou@gmail.com>> > > On Mon, Jun 20, 2011 at 6:56 AM, Lukas Renggli <renggli(a)gmail.com > <mailto:renggli@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 > > -- Janko MivÅ¡ek Svetovalec za informatiko Eranova d.o.o. Ljubljana, Slovenija www.eranova.si tel: 01 514 22 55 faks: 01 514 22 56 gsm: 031 674 565

June 20, 2011

Re: [Pharo-project] [ANN] StOMP - Yet another multi-dialect object serializer

by Janko MivÅ¡ek

Hi Masashi, Now we have a competition, Fuel vs. StOMP :) Big advantage of StOMP is that it is portable and already ported to VW. Which are other advantages? Disadvantages? Also question for Fuel developers, do you plan to port it to other Smalltalks too? Portability is namelly something which is very high on checking list for a serializer to use in portable projects, like most of web ones are. Best regards Janko S, Masashi UMEZAWA piÅ¡e: > Hello all, > > I have recently developed a new serialization library called > StOMP(Smalltalk Objects on MessagePack). > http://stomp.smalltalk-users.jp/ > > StOMP is a binary serializer for major Smalltalk dialects. For those > who know SIXX, StOMP can be seen as a binary SIXX. While SIXX > represents object data as XML, StOMP uses MessagePack. By combining > the flexibility of SIXX with the compactness of MessagePack, StOMP > aims to be a unique, next-generation portable serializer for > Smalltalk. > > Features: > - Implementation is compact and portable > - Shared/circular references support > - "Class shape changes" support > - Data is interchangable between Smalltalk dialects > - Good performance for small sized object graph > > StOMP is now available for Squeak, Pharo, and VisualWorks. > > There is ConfigurationOfStOMP, so the installation is easy. > > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfStOMP'; > load. > (Smalltalk at: #ConfigurationOfStOMP) perform: #load. > > Enjoy! -- Janko MivÅ¡ek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si

June 20, 2011

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

by laurent laffont

Why a .sh ? Pharo is here ;) Laurent On Mon, Jun 20, 2011 at 12:03 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > Yes, that would be awesome and have lot of cool features. Nevertheless, > nobody prevent you from doing a poor man jenkis: a simple bash script that > downloaded latest pharo image, uncompress, and send a build.st script. In > buid.st you put a Gofer script to load all your stuff and finally set > preference. > > So....every in a while you do ./buildMyCoolImage.sh > > and that's all. > > Cheers > > > On Mon, Jun 20, 2011 at 11:46 AM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > >> Yes we would like to offer that service. >> Everybody building their onw image via jenkins :) >> >> Stef >> >> On Jun 20, 2011, at 11:25 AM, laurent laffont wrote: >> >> > 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 >> > >> > 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 >> > >> > >> > >> >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > >

June 20, 2011

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

by Gary Chambers

Some theme methods require the context of creation (aThemedMorph as passed) for adapting to corner style, colours etc. Perhaps, in TEasilyThemed, this context can be broken out into another method that MorphicUIManager could redefine as appropriate (guessing self world)... Regards, Gary ----- Original Message ----- From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Monday, June 20, 2011 10:43 AM Subject: Re: [Pharo-project] why (UIManager defaultnewPluggableDialogWindow:'Pharo is cool') openInWorld 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] About not using full Pharo

by Mariano Martinez Peck

Yes, that would be awesome and have lot of cool features. Nevertheless, nobody prevent you from doing a poor man jenkis: a simple bash script that downloaded latest pharo image, uncompress, and send a build.st script. In buid.st you put a Gofer script to load all your stuff and finally set preference. So....every in a while you do ./buildMyCoolImage.sh and that's all. Cheers On Mon, Jun 20, 2011 at 11:46 AM, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr> wrote: > Yes we would like to offer that service. > Everybody building their onw image via jenkins :) > > Stef > > On Jun 20, 2011, at 11:25 AM, laurent laffont wrote: > > > 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 > > > > 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 > > > > > > > > > -- Mariano http://marianopeck.wordpress.com

June 20, 2011

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

by Alain Plantec

In fact, settingPragmaProcessor was contributed by Andreas Raab to facilitate squeak preferences/Pharo settings compatibility :) Alain Le 20/06/2011 11:41, StÃ©phane Ducasse a Ã©crit : > 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 StÃ©phane Ducasse

Yes we would like to offer that service. Everybody building their onw image via jenkins :) Stef On Jun 20, 2011, at 11:25 AM, laurent laffont wrote: > 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 > > 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

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

by StÃ©phane Ducasse

On Jun 20, 2011, at 6:20 AM, Yanni Chiu wrote: > On 19/06/11 4:38 PM, Damien Cassou wrote: >> Hi, >> >> 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? > > My image was always built from PharoCore. It was done this way before PharoDev existed, and I saw no reason to change. > > I thought people were supposed to build their own image (tailored to their needs). IIRC, PharoDev was initially provided as a convenience for those that wanted such an artifact. > > The concept of PharoDev evolved - I recall discussion about the "branding" of PharoDev as Pharo, and relegating PharoCore to the role of build process artifact. The discussion did not raise any flags for me, until now, when the discussion has turned to "eliminating" PharoCore. > > I've never mentioned this before because I never thought I was doing anything wrong by building my own image from PharoCore. but you are not. :) The point is that we should be able to have good tools inside the default system so that we can get faster. We are fedup to do refactoring of core manually. Stef

June 20, 2011

Re: [Pharo-project] addCloseBox

by StÃ©phane Ducasse

Thanks. On Jun 20, 2011, at 11:14 AM, Gary Chambers wrote: > 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