- Pharo-dev - lists.pharo.org

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

by GermÃ¡n Arduino

Opss, you are right! Thanks (I'm still a newbie with Metacello :) ) 2010/9/22 Miguel CobÃ¡ <miguel.coba(a)gmail.com>: > 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'. > > 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

Sept. 23, 2010

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

by Miguel CobÃ¡

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'. 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

Sept. 23, 2010

Re: [Pharo-project] DoubleArray

by Igor Stasenko

On 23 September 2010 00:37, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > Henry, > > I have been getting away with #doubleAt: and #doubleAt:put:, and otherwise doing pretty much what you said, though I just use a byte array to hold the data. Â It seems to work; for FFI, I end up passing void pointers instead of double pointers, which I don't like doing. > > Your point about using ordinary arrays makes sense to a point, though even w/o external interfacing, there is still a use for DoubleArray just as there is a use for String vs. an array of characters. > The main reason, why they are not here, that VM needs an additional set of primitives, which working with them. <sellsman hat on> I can only say that with NativeBoost, you could be able to implement it quite easily in image and ship it in image, without a need to change VM or use external plugin. <sellsman hat off> > Bill > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Henrik Sperre Johansen [henrik.s.johansen(a)veloxit.no] > Sent: Wednesday, September 22, 2010 5:23 PM > To: pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] DoubleArray > > Â On 22.09.2010 23:09, Schwab,Wilhelm K wrote: >> Squeak, deliberately, does not have a double array class. Â Is that because there is some horrible reason it can't work, or because it won't work on certain platforms? > If the goal is to pass it as a parameter to an external function, one > way would be to subclass WordArray, storing(and reading) each Float in > two elements, and have the endianness decided by Smalltalk endianness. > Probably want a startUp method for the class to swap instances > endianness if the platform has changed as well. >> Put another way, should we add such a class, if only via an external heap or whatever would be needed to make it reliable? >> >> Bill > More likely because no one has actually had a need for one. > It's definitely not _needed_ in base, where normal arrays of floats > would do the same job just as well, if not better. > IMHO, if someone makes one, it so should probably be part of a package > related to external interfacing. > > Cheers, > Henry > > > _______________________________________________ > 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 > -- Best regards, Igor Stasenko AKA sig.

Sept. 23, 2010

[Pharo-project] XMLRPC Project - Progress Report

by GermÃ¡n Arduino

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 I want to ask to any person wanting to contribute with XMLRPC project take contact with me to coordinate efforts. Cheers. -- ================================================= GermÃ¡n S. ArduinoÂ <gsa @ arsol.net>Â Â Twitter: garduino Arduino Software & Web HostingÂ Â http://www.arduinosoftware.com PasswordsProÂ http://www.passwordspro.com =================================================

Sept. 23, 2010

Re: [Pharo-project] I am missing userful functionality?

by Igor Stasenko

One more variant (not sure if its a bug-free) oldBinding := Smalltalk associationAt: #WeakRegistry. WeakRegistry removeFromSystem. WeakFinalizationRegistry rename: #WeakRegistry. oldBinding becomeForward: (Smalltalk associationAt: #WeakRegistry). On 23 September 2010 01:02, Igor Stasenko <siguctua(a)gmail.com> wrote: > Hello, guys > > i want to do a simple thing, which can be expressed by following: > > oldClass replaceWith: newClass migrateInstances: [:inst | > Â ... ] > > In my case, first, i installing a WeakFinalizationRegistry class, > and then want to replace an old WeakRegistry class with it, > silently and painlessly. > > I end up with following script: > > Â | old new oldClass newClass | > Â Â Â Â old := OrderedCollection new. > Â Â Â Â new := OrderedCollection new. > > > "migrate instances" > WeakRegistry allInstancesDo: [:registry | | newr | > Â Â Â Â Â Â Â Â old add: registry. > Â Â Â Â Â Â Â Â newr := WeakFinalizationRegistry basicNew initialize. > Â Â Â Â Â Â Â Â registry migrateTo: newr. > Â Â Â Â Â Â Â Â new add: newr ]. > Â Â Â Â old asArray elementsForwardIdentityTo: new asArray. > > "replace the class" > > Â Â Â Â oldClass := WeakRegistry. > Â Â Â Â newClass := WeakFinalizationRegistry. > > Â Â Â Â Smalltalk forgetClass: #WeakFinalizationRegistry logged: false. > Â Â Â Â newClass superclass removeSubclass: newClass. > Â Â Â Â newClass setName: #WeakRegistry. > Â Â Â Â oldClass becomeForward: newClass. > > -- > > it looks a bit hackish, and i wonder how to do that in more 'standard' way. > > Initially replacing classes was: > > Â oldClass removeFromSystem. > Â newClass rename: #WeakRegistry > > the problem with that, is that all compiled methods , which was > referring to old class through association, > still using it, and to get rid of them i have to recompile them. > > > > -- > Best regards, > Igor Stasenko AKA sig. > -- Best regards, Igor Stasenko AKA sig.

Sept. 23, 2010

[Pharo-project] I am missing userful functionality?

by Igor Stasenko

Hello, guys i want to do a simple thing, which can be expressed by following: oldClass replaceWith: newClass migrateInstances: [:inst | ... ] In my case, first, i installing a WeakFinalizationRegistry class, and then want to replace an old WeakRegistry class with it, silently and painlessly. I end up with following script: | old new oldClass newClass | old := OrderedCollection new. new := OrderedCollection new. "migrate instances" WeakRegistry allInstancesDo: [:registry | | newr | old add: registry. newr := WeakFinalizationRegistry basicNew initialize. registry migrateTo: newr. new add: newr ]. old asArray elementsForwardIdentityTo: new asArray. "replace the class" oldClass := WeakRegistry. newClass := WeakFinalizationRegistry. Smalltalk forgetClass: #WeakFinalizationRegistry logged: false. newClass superclass removeSubclass: newClass. newClass setName: #WeakRegistry. oldClass becomeForward: newClass. -- it looks a bit hackish, and i wonder how to do that in more 'standard' way. Initially replacing classes was: oldClass removeFromSystem. newClass rename: #WeakRegistry the problem with that, is that all compiled methods , which was referring to old class through association, still using it, and to get rid of them i have to recompile them. -- Best regards, Igor Stasenko AKA sig.

Sept. 23, 2010

Re: [Pharo-project] DoubleArray

by Schwab,Wilhelm K

Henry, I have been getting away with #doubleAt: and #doubleAt:put:, and otherwise doing pretty much what you said, though I just use a byte array to hold the data. It seems to work; for FFI, I end up passing void pointers instead of double pointers, which I don't like doing. Your point about using ordinary arrays makes sense to a point, though even w/o external interfacing, there is still a use for DoubleArray just as there is a use for String vs. an array of characters. Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Henrik Sperre Johansen [henrik.s.johansen(a)veloxit.no] Sent: Wednesday, September 22, 2010 5:23 PM To: pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] DoubleArray On 22.09.2010 23:09, Schwab,Wilhelm K wrote: > Squeak, deliberately, does not have a double array class. Is that because there is some horrible reason it can't work, or because it won't work on certain platforms? If the goal is to pass it as a parameter to an external function, one way would be to subclass WordArray, storing(and reading) each Float in two elements, and have the endianness decided by Smalltalk endianness. Probably want a startUp method for the class to swap instances endianness if the platform has changed as well. > Put another way, should we add such a class, if only via an external heap or whatever would be needed to make it reliable? > > Bill More likely because no one has actually had a need for one. It's definitely not _needed_ in base, where normal arrays of floats would do the same job just as well, if not better. IMHO, if someone makes one, it so should probably be part of a package related to external interfacing. Cheers, Henry _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 22, 2010

Re: [Pharo-project] DoubleArray

by Henrik Sperre Johansen

On 22.09.2010 23:09, Schwab,Wilhelm K wrote: > Squeak, deliberately, does not have a double array class. Is that because there is some horrible reason it can't work, or because it won't work on certain platforms? If the goal is to pass it as a parameter to an external function, one way would be to subclass WordArray, storing(and reading) each Float in two elements, and have the endianness decided by Smalltalk endianness. Probably want a startUp method for the class to swap instances endianness if the platform has changed as well. > Put another way, should we add such a class, if only via an external heap or whatever would be needed to make it reliable? > > Bill More likely because no one has actually had a need for one. It's definitely not _needed_ in base, where normal arrays of floats would do the same job just as well, if not better. IMHO, if someone makes one, it so should probably be part of a package related to external interfacing. Cheers, Henry

Sept. 22, 2010

Re: [Pharo-project] DejaVu extra sizes Re: DemoMode should not change Fonts only sizes?

by Mariano Martinez Peck

On Tue, Sep 21, 2010 at 2:34 PM, Sven Van Caekenberghe <sven(a)beta9.be>wrote: > > On 21 Sep 2010, at 13:11, Fernando olivero wrote: > > > thanks Alain and Juan, CUIS fonts gave a excellent look and feel to > Gaucho! > > > > I highly recommend using them as the default Pharo font family > > > > Fernando > > > > pd: what i did is add the following line to the ConfigurationOfGaucho. > > > > spec > > blessing: #baseline; > > repository: 'http://www.squeaksource.com/gaucho'; > > package: 'DejaVuBitmapFonts' with:[ spec repository: ' > http://www.squeaksource.com/DejaVu'] ; > > .... > > This package works great (Pharo 1.1, Cog, OSX). Thanks for the pointer. > > Due to the size issue, I wouldn't include them all by default. > > Maybe we could make some clever set of MC packages that you can load for > each font size that you want ? > Or load the spec data from a file/url ? > You have a point here. Maybe we don't need to put all the families and all the size in the core....just the most used ones. Then, in the Dev image we can load all the rest, and the settings to set the Demo Fonts. what do you think alain? Anyway, all these fonts should be removed in #cleanUpForProduction I think. cheers mariano > > I think most people will only need one or two sizes. The fallback should > just be miminal. > > Sven > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 22, 2010

Re: [Pharo-project] Changes in external packages for Pharo 1.2

by Schwab,Wilhelm K

Mariano, I do not like the new inspector, but as long as you do not force me to use it, I'm happy to have it in the image. Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Mariano Martinez Peck [marianopeck(a)gmail.com] Sent: Wednesday, September 22, 2010 4:36 PM To: Pharo Development; A friendly place where any question about pharo is welcome Subject: [Pharo-project] Changes in external packages for Pharo 1.2 Hi folks. I would like to write now the changes for the development image for Pharo 1.2. Right now I have the following: - Let (load) NewInspector in the image, but put the old one as the default. Several people were against NewInspector. I like it for example, but anyway, if it is present in the image then I would be able to use it. - Add Memory Monitor tool from Alexandre Bergel. - Add AutoTest from Laurent Laffont. - Add GoferProjectLoader from Esteban Lorenzano, to easily manage Metacello. For any package we include, it would be AWESOME to have: - tests - a Metacello configuration So, questions: 1) do you more ore less agree with them??? (we cannot be all agree with ALL items) 2) for package developers: do you agree we include all of them in PharoDev? will you help maitaining them? are they all MIT? (I think so) Please, confirm us this. 3) do you think there are more packages/projects we should include? What about, for example: - WorkingSet from Romain Robbes - Algernon (still doesn't work in 1.1) - TDDFacilties from Hernan Wilkinson - SimpleLogger from German Arduino I know this is not Dev, but I hope in Pharo1.2 we will have: - The new method finder from Benjamin that mixes both, and remove the old ones. - The new RecentSubmisons, and remove the old one. Thanks Mariano

Sept. 22, 2010