September 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 2744: Renaming the path to the image is not caught in Pharo on OS X

by csrabak＠bol.com.br

This issue points to a problem in the VM. The reference to the file has to be a file descriptor not a filename. If the image and changes file are kept open by the VM, that is not supposed to happen. Em 21/09/2010 15:01, Mariano Martinez Peck < marianopeck(a)gmail.com > escreveu: 2010/9/21 Guillermo Polito <guillermopolito(a)gmail.com> 2010/9/21 Mariano Martinez Peck <marianopeck(a)gmail.com> Yes, I have this probelm several times....what I did is to change the logChange: so that it does nothing, save it, and then quit the image. Anyway, what could be a solution for this problem? Relative paths? :/ No, it won't wotk. Suppose my .image and .changes are now in /home/mariano/PharoÂ and while the image is running you rename the directory toÂ /home/mariano/pharoRenamed Your smalltalk image is still pointing to your .changes in /home/mariano/PharoÂ Â and it was not updated. So...the only way I see is that the OS somehow should notify SqueakVM about that..... thanks mariano On Tue, Aug 3, 2010 at 3:28 PM, Mircea Lungu <lungu(a)iam.unibe.ch> wrote: Hi guys, If I rename any of the directories in the path of a running image I will break the image: I can't save it, I can't close it. I get a debugger at any step. It seems the image is not informed of the path change and it still tries to log the changes in the the changes file which has already moved. I verified this on OS X,. I opened an issue for this: http://code.google.com/p/pharo/issues/detail?id=2744 Mircea. _______________________________________________ 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 _______________________________________________ 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] A pattern for GUI programming (Morphic, Cuis, etc)

by csrabak＠bol.com.br

I think we should create something akin the RFC concept in Pharo page: then after a time given to collect the comments we can see if the idea was OK or not. Em 21/09/2010 09:16, Juan Vuletich < juan(a)jvuletich.org > escreveu: Mariano Martinez Peck wrote: > could we add that to the pharo online book ? Yes, sure. But I believe it would make sense only if it is documenting actual practice. Otherwise a big warning like "Warning: This is just the documentation of a proposed style. This is not currently used in Pharo.". Then, I'm not sure if it is really useful... Cheers, Juan Vuletich _______________________________________________ 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] DoubleArray

by Schwab,Wilhelm K

Sig, Fair enough :) The most recent thing I recall on NativeBoost is Stef asking for what I assume must be a Mac plugin; I thought Linux would be left out too, but it appears not, though it is not in my current vm. Beyond some list traffic, I found this: http://code.google.com/p/nativeboost/wiki/NativeBoost Is there other documentation somewhere? Build instructions? You have a block copy, which is good. What about indexing, such as getting floats or doubles out of external memory? I am very comfortable adding functions to a library for integer and float/double calculations on "large" arrays and calling them via FFI; plugins are another story. Are there examples to follow? Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Igor Stasenko [siguctua(a)gmail.com] Sent: Wednesday, September 22, 2010 6:20 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] DoubleArray 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. _______________________________________________ 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] 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. 22, 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. 22, 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. 22, 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. 22, 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. 22, 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. 22, 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