- Pharo-dev - lists.pharo.org

Re: [Pharo-project] XMLRPC Project - Progress Report

by StÃ©phane Ducasse

Tell us when pharo core can be a user. Because we want to clean the mess. Stef On Oct 3, 2010, at 6:52 PM, Sven Van Caekenberghe wrote: > GermÃ¡n, > > On 03 Oct 2010, at 17:41, GermÃ¡n Arduino wrote: > >> As usual, any comment, suggestion or criticism is more than welcome. > > Well, you could consider using the Zinc HTTP Components framework. > > XMLRPCProxy>>#sendXmlRpc: is using the ugly HTTPSocket interface. > > Using any of the clients in Zn will give you a semantically much richer interface to headers and content (entities), both for requests and for responses. And you get many features on top. > > I haven't looked at the server side, but there too you can get HTTP functionality for free. > > It will add a dependency though, but I would guess you have one for the server side already, no ? > > Anyway, we're looking for users... > > Sven > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 3, 2010

Re: [Pharo-project] Metacello Configuration Browser?

by Mariano Martinez Peck

2010/9/28 Simon Denier <Simon.Denier(a)inria.fr> > > On 28 sept. 2010, at 21:30, Mariano Martinez Peck wrote: > > What I would love is a UI for GoferProjectLoader from Esteban. I mean, we > have the apt-get but we need now synaptic :) > > And....if we plan to do what I say in the email about Pharo and Metacello, > having something like that is very, VERY useful. From my point of view, even > more than a Metacello browser. > > > > That's too different usages, which are complementary: GoferProjectLoader is > for end-users, > yes! > while I'm thinking more of a browser for developers, when they have to > create a new release and check there configuration is consistent. Right now > it's quite a pain, ask Jannik who did the 4.1 Moose :) > > ahhhhh got it ;) so...the question is...why not improving Metacello-OB instead? > > > Cheers > > Mariano > > 2010/9/28 Simon Denier <Simon.Denier(a)inria.fr> > >> >> On 28 sept. 2010, at 15:14, Guillermo Polito wrote: >> >> Okok, I saw there already exists a Configuration browser :P. But it can >> be reaally improved. >> >> >> >> Which one are you talking about? The one in 1.2? Or on Squeaksource? >> >> There have been multiple efforts (GTMetaceller, MooseDevBrowser...) >> already to try and see what we would like to do in a browser. But there are >> also some performance issues with Metacello right now, which makes it >> impractical to browser config. which Dale and Alex have started to tackle >> them. >> >> Anyway, the latest effort (started during ESUG) is there: it is basically >> a rewrite of what have been done in the tools above (with still some missing >> parts). >> >> MCHttpRepository >> location: 'http://www.squeaksource.com/MetacelloBrowser' >> user: '' >> password: '' >> >> >> Note, it requires Glamour and is more of a testbed than a fully-supported >> tool for now. >> >> >> >> >> On Tue, Sep 28, 2010 at 10:00 AM, Guillermo Polito < >> guillermopolito(a)gmail.com> wrote: >> >>> I'm always reading people saying that metacello configurations are some >>> kind of... overdesign. So, maybe we need a tool (or to modify monticello >>> browser) wich allow us to: >>> >>> - know wich packages are core and dev. Sometimes using a dev image, I >>> write things depending on Dev packages and I don't realize it. >>> - create automatically or propose configurations depending on the actual >>> state of the packages. >>> - browse configurations nicely :). It's a new concept, we need a nice >>> tool to support it. >>> >>> Maybe if the configs are easily created, we can have more of them, and we >>> will be no longer so lazy. >>> >>> Cheers, >>> Guille >>> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> -- >> Simon >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > -- > Simon > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 3, 2010

Re: [Pharo-project] OB Dev in Metacello

by Mariano Martinez Peck

2010/9/29 Diogenes Moreira <diogenes.moreira(a)gmail.com> > hi folks: > > anybody could tell how load the OB Dev Tools with Metacello. > Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfOmniBrowser'; load. ((Smalltalk at: #ConfigurationOfOmniBrowser ) project version: '1.2') load: 'Dev' or... ((Smalltalk at: #ConfigurationOfOmniBrowser ) project version: '1.2') load for the core... Cheers Mariano > > > Thank in Advance.. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 3, 2010

Re: [Pharo-project] XMLRPC Project - Progress Report

by Sven Van Caekenberghe

GermÃ¡n, On 03 Oct 2010, at 17:41, GermÃ¡n Arduino wrote: > As usual, any comment, suggestion or criticism is more than welcome. Well, you could consider using the Zinc HTTP Components framework. XMLRPCProxy>>#sendXmlRpc: is using the ugly HTTPSocket interface. Using any of the clients in Zn will give you a semantically much richer interface to headers and content (entities), both for requests and for responses. And you get many features on top. I haven't looked at the server side, but there too you can get HTTP functionality for free. It will add a dependency though, but I would guess you have one for the server side already, no ? Anyway, we're looking for users... Sven

Oct. 3, 2010

Re: [Pharo-project] XMLRPC Project - Progress Report

by GermÃ¡n Arduino

Started working on the tests, the current Encoder/Decoder (at client level) works ok. For example, I opened an account on http://snipplr.com (to save useful and interesting Smalltalk snippets) and can connect without problems. Next, some examples: | url proxy r | url := Url absoluteFromText: 'http://snipplr.com/xml-rpc.php'. proxy := XMLRPCProxy new url: url. r := proxy invokeMethod: 'languages.list' withArgs: #('Your snipplr key'). r := proxy invokeMethod: 'user.checkkey' withArgs: #('Your snipplr key'). r := proxy invokeMethod: 'snippet.list' withArgs: #('Your snipplr key' 'pharo'). "To get a snippet you don't need key, but the Snippet ID" r := proxy invokeMethod: 'snippet.get' withArgs: #('41365'). The complete Snipplr xmlrpc API is on: http://snipplr.com/blog/2006/07/06/snipplr-api/ Next step is check the complete API specification (http://www.xmlrpc.com/spec.) to implement all the features at client level. As usual, any comment, suggestion or criticism is more than welcome. Cheers. 2010/9/23 GermÃ¡n Arduino <garduino(a)gmail.com>: > ok, ConfigurationOfXMLRPC is on MetacelloRepository, documentation on > #workspace method. > > Suggestions or corrections from the Metacello experts are more than welcome. > > Next Step: The real work start now :) > > Cheers. > GermÃ¡n. > > > 2010/9/23 Mariano Martinez Peck <marianopeck(a)gmail.com>: >> >> >> On Thu, Sep 23, 2010 at 12:49 AM, Miguel CobÃ¡ <miguel.coba(a)gmail.com> wrote: >>> >>> El miÃ©, 22-09-2010 a las 19:16 -0300, GermÃ¡n Arduino escribiÃ³: >>> > Hi Everybody: >>> > >>> > I reorganized the XMLRPC packages, integrating the changes of Skrish >>> > (currently on PharoGoodies) renaming the packages in four categories: >>> > >>> > XMLRPC-Client-Core >>> > XMLRPC-Client-Tests >>> > XMLRPC-Server-Core >>> > XMLRPC-Server-Tests >>> > >>> > Next step: Build the following metacello configurations: >>> > >>> > ConfigurationOfXMLRPCClient >>> > ConfigurationOfXMLRPCServer >>> > ConfigurationOfXMLRPCAll >>> >>> You don't need three configurations, just create one and create 3 groups >>> 'All','Server', 'Client'. >>> >> >> You were faster than :) I was going to answer exactly the same...one >> ConfigurationOfXMLRPC and different groups: >> - 'All' >> - 'Server' >> - 'Server with Tests' >> - 'Client' >> - 'Client with Tests' >> -etc.... >> >> Check ConfigurationOfMagma since it does almost the same I think. >> >> cheers >> >> mariano >> >>> Cheers >>> > >>> > >>> > I want to ask to any person wanting to contribute with XMLRPC project >>> > take contact with me to coordinate efforts. >>> > >>> > >>> > Cheers. >>> > >>> > >>> >>> -- >>> Miguel CobÃ¡ >>> http://miguel.leugim.com.mx >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >

Oct. 3, 2010

Re: [Pharo-project] Less plugins, more Smalltalk code! (was: Re: Pharo 1.1.1 OneClickCogVm)

by Schwab,Wilhelm K

For Ocean to succeed, you either have to work really hard to make non-blocking calls (I'm thinking of SSL sockets), or you need the ability to call functions on OS threads. The calls need to block their calling Process and let the other Processes run as though nothing is happening. ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Noury Bouraqadi [bouraqadi(a)gmail.com] Sent: Sunday, October 03, 2010 4:57 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: [Pharo-project] Less plugins, more Smalltalk code! (was: Re: Pharo 1.1.1 OneClickCogVm) On 30 sept. 2010, at 20:22, GermÃ¡n Arduino wrote: > 2010/9/30 Sven Van Caekenberghe <sven(a)beta9.be>: >> >> Less plugins, more Smalltalk code! >> I want to look at everything and never see C. >> Plugins/primitives should only be there when they are absolutely necessary (to access a platform feature or for crucial performance). >> >> Sven >> > > +1 > Yes. This is the approach we advocate in the Ocean project. We would like to see it generalized beyond the network library. Noury _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 3, 2010

[Pharo-project] [update 1.2] #12168

by stephane ducasse

12168 ----- - Issue 3043: Refactor SystemOrganizer to decouple it from Smalltalk. Thanks Nicolas Paez and Damien Pollet. - Issue 3027: Base64MimeConverterTest>>#testOnByteArray raise an error. Thanks Cyrille Delaunay Stef

Oct. 3, 2010

Re: [Pharo-project] Another fixes to finalization (was Re: [update 1.2] #12161 - #12172)

by Henrik Sperre Johansen

On 03.10.2010 11:59, Igor Stasenko wrote: > On 3 October 2010 12:36, Henrik Sperre Johansen > <henrik.s.johansen(a)veloxit.no> wrote: >> On 03.10.2010 05:47, Igor Stasenko wrote: >>> On 3 October 2010 03:13, Henrik Sperre Johansen >>> <henrik.s.johansen(a)veloxit.no> wrote: >>>> On 02.10.2010 19:01, Igor Stasenko wrote: >>>>> On 2 October 2010 19:47, StÃ©phane Ducasse<stephane.ducasse(a)inria.fr> >>>>> wrote: >>>>>> Hi igor >>>>>> >>>>>> do you understand why the previous definition was >>>>>> >>>>>> cachedDefinitions >>>>>> Definitions ifNil: [Definitions := WeakIdentityKeyDictionary >>>>>> new. >>>>>> WeakArray addWeakDependent: Definitions]. >>>>>> ^ Definitions >>>>>> >>>>> i don't. :) >>>>> >>>>> It just a way to free memory as fast as possible. >>>>> But its really not worth spending so much CPU in order to save few >>>>> bytes of memory. >>>> Without registering the dict for finalization, the values won't ever be >>>> removed with the current implementation. >>> They are removed. After each package load/unload operation. >>> I don't see a reason to do this more often. >> If they are removed explicitly, then yes. But then again, if that's the >> case, why use a weak dictionary in the first place? > i don't know much about MC to tell for sure. > >>>> Which can be somewhat hampering to performance once you have lots of >>>> nil-keyed elements all stashed from index 1 and onwards after a rehash. >>>> >>> In Pharo, weak dict knows how to reuse expired associations: >>> >> And when do they expire? Only when they are either finalized, or removed >> explicitly. >> So if you do neither, they will stay indefinately without being >> removed/reused. > no. they expiring when key become nil. > You'd think so, yes. However, see implementor of WeakKeyAssociation>>#expired, and senders of #expire. Cheers, Henry

Oct. 3, 2010

Re: [Pharo-project] Another fixes to finalization (was Re: [update 1.2] #12161 - #12172)

by Igor Stasenko

On 3 October 2010 12:36, Henrik Sperre Johansen <henrik.s.johansen(a)veloxit.no> wrote: > Â On 03.10.2010 05:47, Igor Stasenko wrote: >> >> On 3 October 2010 03:13, Henrik Sperre Johansen >> <henrik.s.johansen(a)veloxit.no> Â wrote: >>> >>> Â On 02.10.2010 19:01, Igor Stasenko wrote: >>>> >>>> On 2 October 2010 19:47, StÃ©phane Ducasse<stephane.ducasse(a)inria.fr> >>>> Â wrote: >>>>> >>>>> Hi igor >>>>> >>>>> do you understand why the previous definition was >>>>> >>>>> cachedDefinitions >>>>> Â Â Â Â Definitions ifNil: [Definitions := WeakIdentityKeyDictionary >>>>> new. >>>>> Â WeakArray addWeakDependent: Definitions]. >>>>> Â Â Â Â ^ Definitions >>>>> >>>> i don't. :) >>>> >>>> It just a way to free memory as fast as possible. >>>> But its really not worth spending so much CPU in order to save few >>>> bytes of memory. >>> >>> Without registering the dict for finalization, the values won't ever be >>> removed with the current implementation. >> >> They are removed. After each package load/unload operation. >> I don't see a reason to do this more often. > > If they are removed explicitly, then yes. But then again, if that's the > case, why use a weak dictionary in the first place? i don't know much about MC to tell for sure. >>> >>> Which can be somewhat hampering to performance once you have lots of >>> nil-keyed elements all stashed from index 1 and onwards after a rehash. >>> >> In Pharo, weak dict knows how to reuse expired associations: >> > And when do they expire? Only when they are either finalized, or removed > explicitly. > So if you do neither, they will stay indefinately without being > removed/reused. no. they expiring when key become nil. > > Cheers, > Henry > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Best regards, Igor Stasenko AKA sig.

Oct. 3, 2010

Re: [Pharo-project] Another fixes to finalization (was Re: [update 1.2] #12161 - #12172)

by Henrik Sperre Johansen

On 03.10.2010 05:47, Igor Stasenko wrote: > On 3 October 2010 03:13, Henrik Sperre Johansen > <henrik.s.johansen(a)veloxit.no> wrote: >> On 02.10.2010 19:01, Igor Stasenko wrote: >>> On 2 October 2010 19:47, StÃ©phane Ducasse<stephane.ducasse(a)inria.fr> >>> wrote: >>>> Hi igor >>>> >>>> do you understand why the previous definition was >>>> >>>> cachedDefinitions >>>> Definitions ifNil: [Definitions := WeakIdentityKeyDictionary new. >>>> WeakArray addWeakDependent: Definitions]. >>>> ^ Definitions >>>> >>> i don't. :) >>> >>> It just a way to free memory as fast as possible. >>> But its really not worth spending so much CPU in order to save few >>> bytes of memory. >> Without registering the dict for finalization, the values won't ever be >> removed with the current implementation. > They are removed. After each package load/unload operation. > I don't see a reason to do this more often. If they are removed explicitly, then yes. But then again, if that's the case, why use a weak dictionary in the first place? >> Which can be somewhat hampering to performance once you have lots of >> nil-keyed elements all stashed from index 1 and onwards after a rehash. >> > In Pharo, weak dict knows how to reuse expired associations: > And when do they expire? Only when they are either finalized, or removed explicitly. So if you do neither, they will stay indefinately without being removed/reused. Cheers, Henry

Oct. 3, 2010