February 2017 - Pharo-users

Re: [Pharo-users] Team programming with Smalltalk

by Dale Henrichs

On 02/20/2017 03:58 AM, Denis Kudriashov wrote: > > 2017-02-18 8:53 GMT+01:00 itlists(a)schrievkrom.de > <mailto:itlists@schrievkrom.de> <itlists(a)schrievkrom.de > <mailto:itlists@schrievkrom.de>>: > > Sadly this is gone or simply only badly implemented. E.g. in > Pharo you > can select a package - fine, but to know, what has been extended > in this > package ?. The name of the method categories also define in which > package this method is located in. Make a type error and the > method goes > into a different package and you will not recognize it. Solutions born > by the idea: how can we make it simple to have a solution this > evening - > and these solutions survive over the years. > > > It will be changed in Pharo 7 with Calypso. It already shows packages > instead of categories with start convension. You guys should really be thinking in terms of projects not packages especially for Pharo7... browse project lets you see all classes involved in a project, save project saves all dirty packages in project, diff project shows all changes for a project ... etc. etc. ... Dale

Feb. 21, 2017

Re: [Pharo-users] Latest Voyage for Pharo4

by Dale Henrichs

On 02/19/2017 11:21 PM, Stephan Eggermont wrote: > On 19/02/17 18:50, Dale Henrichs wrote: >> Hilaire, >> >> I mentioned last night that I thought that there was a better solution >> to your problem and I think that if you load the latest Metacello and >> then lock Seaside3: >> >> Metacello image >> configuration: 'Seaside3'; >> version: '3.1.5'; "most recent 3.1.x version" >> lock. >> >> Then load Voyage, you shouldn't have the problem with Seaside being >> updated to 3.2. > > Voyage needs a newer Grease, is that backwards compatible (I forgot)? > Don't know if Grease is backwards compatible or not ...

Feb. 21, 2017

Re: [Pharo-users] running code on image starts and quitting

by Cyril Ferlicot D.

On 21/02/2017 17:29, Raffaello Giulietti wrote: > > Hi Cyril, > > doesn't seem to work in my case. > > Just for fun, I try to set a class instance variable to Time current in > the class-side #startUp method and quit the image with saving. Upon > restarting the image, the class instance variable is still nil. > > Anything else I have to ensure? > As Sven said I forgot that you need to register your class. You can add this in the class side on Pharo 5-6: "protocol: class initialization" initialize super initialize. SessionManager default registerToolClassNamed: self name -- Cyril Ferlicot http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Feb. 21, 2017

Re: [Pharo-users] running code on image starts and quitting

by Raffaello Giulietti

On 2017-02-21 17:10, Cyril Ferlicot D. wrote: > On 21/02/2017 16:54, Raffaello Giulietti wrote: >> Hi guys, >> >> I need to run some Pharo code whenever the image starts. Similarly on >> (clean) quitting. >> What's the recommended practice? >> >> Regards >> RG >> > > Hello! > > Every classes should be able to override the methods #startUp, > #startUp:, #shutDown and #shutDown: in order to do some work. > > Hi Cyril, doesn't seem to work in my case. Just for fun, I try to set a class instance variable to Time current in the class-side #startUp method and quit the image with saving. Upon restarting the image, the class instance variable is still nil. Anything else I have to ensure?

Feb. 21, 2017

Re: [Pharo-users] UFFI and ByteArray

by Esteban Lorenzano

usually, something more or less like this: sourceByteArrayOrExternalAddress := â¦ some ... destEnternalAddressOrByteArray replaceFrom: 1 to: sourceByteArrayOrExternalAddress size with: sourceByteArrayOrExternalAddress startingAt: 1 and or course you can play with the starting points and sizes. cheers, Esteban > On 21 Feb 2017, at 17:13, Raffaello Giulietti <raffaello.giulietti(a)lifeware.ch> wrote: > > Hi, > > I'm having a hard time finding documentation on how to copy a portion of a ByteArray to/from another portion of a heap allocated C byte array with UFFI. > > My current reference is https://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgre… > > Thanks for directing me at relevant docs or examples and sorry in advance if I missed some important point in the docs. > > RG > >

Feb. 21, 2017

Re: [Pharo-users] running code on image starts and quitting

by Sven Van Caekenberghe

You also have to register with SessionManager (see its class comment, see its references). > On 21 Feb 2017, at 17:10, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > > On 21/02/2017 16:54, Raffaello Giulietti wrote: >> Hi guys, >> >> I need to run some Pharo code whenever the image starts. Similarly on >> (clean) quitting. >> What's the recommended practice? >> >> Regards >> RG >> > > Hello! > > Every classes should be able to override the methods #startUp, > #startUp:, #shutDown and #shutDown: in order to do some work. > > > -- > Cyril Ferlicot > > http://www.synectique.eu > > 2 rue Jacques PrÃ©vert 01, > 59650 Villeneuve d'ascq France >

Feb. 21, 2017

UFFI and ByteArray

by Raffaello Giulietti

Hi, I'm having a hard time finding documentation on how to copy a portion of a ByteArray to/from another portion of a heap allocated C byte array with UFFI. My current reference is https://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgre… Thanks for directing me at relevant docs or examples and sorry in advance if I missed some important point in the docs. RG

Feb. 21, 2017

Re: [Pharo-users] running code on image starts and quitting

by Cyril Ferlicot D.

On 21/02/2017 16:54, Raffaello Giulietti wrote: > Hi guys, > > I need to run some Pharo code whenever the image starts. Similarly on > (clean) quitting. > What's the recommended practice? > > Regards > RG > Hello! Every classes should be able to override the methods #startUp, #startUp:, #shutDown and #shutDown: in order to do some work. -- Cyril Ferlicot http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Feb. 21, 2017

running code on image starts and quitting

by Raffaello Giulietti

Hi guys, I need to run some Pharo code whenever the image starts. Similarly on (clean) quitting. What's the recommended practice? Regards RG

Feb. 21, 2017

Re: [Pharo-users] Loading Seaside via Bootstrap in Pharo 6

by Sven Van Caekenberghe

Hi Torsten, Thanks for your extensive reply, I am too busy to try myself, but I very much appreciate your help. Sven (PS: yes, that was the error that I saw too) > On 21 Feb 2017, at 14:24, Torsten Bergmann <astares(a)gmx.de> wrote: > > Hi, > > regarding the problem Sven mentioned on http://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/2017-February/… > > here are my findings: > > When I use latest Pharo 6 (Image 60404) and run > > Metacello new > smalltalkhubUser: 'Seaside' project: 'MetacelloConfigurations'; > configuration: 'Seaside3'; > version: #'release3.2'; > load > > it loads the latest release 3.2 (which internally loads 3.2.1). The package is "ConfigurationOfSeaside3-JohanBrichau.323.mcz" > > This loads fine in Pharo 6 except that after installation the "Tools" -> "Seaside control panel" is not working anymore as > "NewListModel" is not found anymore. So the control panel is broken. Dont know what the migration path is for UI's > who used the removed "NewListModel" class. > > So yes - one can (by using the above script) use Seaside but currently has to start the server with a script > until this is fixed. This is good to know - but does not solve the "loading from catalog" issue. > > ----------------------------------------------------------------------------------------------------------------------------------------- > > So (in a fresh image 60404) I loaded "Bootstrap" from catalog and I received the error Sven reported. > > But ConfigurationOfBootstrap itself is not the problem I guess. Because it is also only referencing the > "release3.2" version of Seaside and also "ConfigurationOfSeaside3-JohanBrichau.323.mcz" is loaded. > > > The Transcript shows the following error output: > > Loaded -> ConfigurationOfSeaside3-JohanBrichau.323 --- http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main/ --- > http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main/Error: Name not found: Seaside-Pharo-Development > > Also when you try to open the ConfigurationOfSeaside3 using Versionner I receiver an error "Name not found: Seaside-Pharo-Development". > > So there must be something wrong with the Seaside config I thought - or (what would be worse) with the newer Metacello > version included in Pharo 6. At least the config looks OK and in both situations "ConfigurationOfSeaside3-JohanBrichau.323" is used. > > Additionally I tried: > > - when I load the Bootstrap config in a fresh Pharo 5.0 image (50769) from Catalog all loads fine. > - when I manipulate the Pharo 6 image to have a version 5 signature > SystemVersion newVersion: 'Pharo5.0'. SystemVersion current inspect. > and load from catalog afterwards it also does not work. So I guess a Pharo 5.x specific config rule could not be the cause. > > > Now I checked how Catalog loads the configs. And in class CatalogProject you will notice that for the catalog we still use Gofer for loading > > installStableVersion > Gofer it > url: self repositoryUrl; > configurationOf: self name; > loadStable > > when I change it to Metacello API > > installStableVersion > Metacello new > repository: self repositoryUrl, '/',self name; > configuration: self name; > version: #'stable'; > load > > what a surprise: anything loads fine. I still wonder and do not know about the difference why Gofer and Metacello loading in Pharo 6 > makes a difference now. > > So we could fix it for the catalog ... still I have no glue about the Gofer/Metacello API difference ... > > https://pharo.fogbugz.com/f/cases/19736/Catalog-should-use-Metacello-API-in… > > > Thanks > T.

Feb. 21, 2017