March 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] pharo --headless in Windows makes a Window show anyway

by Eliot Miranda

On Sat, Mar 1, 2014 at 7:43 AM, phil(a)highoctane.be <phil(a)highoctane.be>wrote: > When running (from a Zeroconf install): > > pharo --headless Pharo.image > > it looks like that the window is not opening ( or it is opening and > closing so fast that I do not see it). > > Then I have an image with Seaside, Magritte, and other things. > > When doing the same, I do see the window of one second and then it closes. > > Is it normal to have that window opening? That's annoying for scripts as > it doesn't look good. > > On OSX I do not have this behavior. > > What causes that on Windows? > It's bits in the exe that decide whether it's a console app or a windows app. So, at least with the Cog VM, not sure about the Pharo VM, if you want to run headless you use the SqueakConsole.exe VM instead of the Squeak.exe VM. They're identical except in those bits. Yes the distinction is stupid; unix doesn't need it, but that's Windows. > Phil > -- best, Eliot

March 1, 2014

Status of the VM?

by Alexandre Bergel

Hi! Stef told me the coming VM will expose some data about the execution to the image. This will be great for our profiling tools. What is the status? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 1, 2014

Versioneer docs?

by phil＠highoctane.be

I am now porting my code to 3.0 I am using Versioneer to look at my configuration as when I do load it in 3.0, it seems that there are some duplicate packages coming in my package-cache and I want to remove these dupes. (Mostly Seaside related). Versioneer is very helpful in representing the configuration. Now, is there any doc about its usage? TIA Phil

March 1, 2014

pharo --headless in Windows makes a Window show anyway

by phil＠highoctane.be

When running (from a Zeroconf install): pharo --headless Pharo.image it looks like that the window is not opening ( or it is opening and closing so fast that I do not see it). Then I have an image with Seaside, Magritte, and other things. When doing the same, I do see the window of one second and then it closes. Is it normal to have that window opening? That's annoying for scripts as it doesn't look good. On OSX I do not have this behavior. What causes that on Windows? Phil

March 1, 2014

Re: [Pharo-dev] ws vs st extensions

by Esteban A. Maringolo

Workspace serves a particular purpose. I use them, as soon as I depend on them I move it a to a method. However, the main use I have for them is startup scripts or other things I run from the command line. They can't be methods, because they change. Regards! ps: I have to read about the process of submitting a change Esteban A. Maringolo 2014-03-01 4:15 GMT-03:00 Pharo4Stef <pharo4Stef(a)free.fr>: > > On 01 Mar 2014, at 00:17, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > >> 2014-02-28 18:26 GMT-03:00 Chris Cunningham <cunningham.cb(a)gmail.com>: >>> On Fri, Feb 28, 2014 at 6:07 AM, Esteban A. Maringolo <emaringolo(a)gmail.com> >>> wrote: >>>> >>>> I have a naive question... >>>> >>>> Why if the BasicCodeLoader handler looks for .st files does the >>>> Workpace offer .ws as the default extension? >>> >>> Well, the workspace doesn't just use chuck format - in fact, you rarely put >>> in chunk format into a workspace (or do you? I certainly don't). Also, >>> workspaces allow for dynamic local variables - which normal chunk loaders >>> don't. The two things behave differently. .st is explicitly for runnable >>> code - workspaces are for more than just code - more of a scratch pad. >> >> I know, but the cmd line handler isn't a chunk reader. It compiles the >> content of the file and evaluate it all at once. And explicitly >> expects for files with .st extension (I don't understand such >> restriction). >> >> I don't put chunk in a workspace either (actually I don't know how to >> properly read a chunk file in Pharo). >> >> tl;dr Frankly I don't like the .ws extension at all. It's a matter of habit. :) >> >> Regards! > > send a fix. > For me saving workspace in file looks prehistorical age. > just having method to manage code snippets is much more efficient > > > >> >> >> >> Esteban A. Maringolo >> > >

March 1, 2014

Re: [Pharo-dev] [squeak-dev] [ANN] Fuel 1.9.3

by Sebastian Sastre

great job you guys sebastian o/ > On 01/03/2014, at 02:23, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > Thanks for the update. > Cheers, > > HernÃ¡n > > > 2014-02-26 18:13 GMT-03:00 Max Leske <maxleske(a)gmail.com>: >> Dear fellow Smalltalkers >> >> Mariano, Martin and myself are happy to announce Fuel version 1.9.3 which includes the follwing changes to 1.9 (1.9.1 and 1.9.2 were never officially announced): >> >> - (feature) the #fuelReplacement selector offers the ability to statically replace an object (e.g. with nil) during analysis. This can lead to significantly smaller graphs and improved speed when serializing large graphs >> - (feature) serialize the same graph that was analyzed instead of retrazing the graph during serialization. This prevents changes in the graph from happening between analysis and serialization >> - (change) store source when serializing CompiledMethod objects. Needed because Opal does not allow decompilation >> - (fix) migrate variables across hierarchy >> - (feature) Object>>serializeToFileNamed: shortcut for serializing arbitrary objects >> - (fix) better compression for LargeNegativeIntegers (https://pharo.fogbugz.com/f/cases/12052/Fuel-could-store-LargeNegativeInteg…) >> >> Pharo30 already includes most of these changes (integration request: https://pharo.fogbugz.com/f/cases/13000/Integrate-Fuel-1-9-3) >> >> This release runs with: >> - Pharo: 1.1.1, 1.1.2, 1.2, 1.2.2, 1.3, 1.4, 2.0, 3.0 >> - Squeak: 4.1, 4.2, 4.3, 4.4, 4.5 >> >> The documentation is not up to date yet but we will remedy that situatoin within the next couple of days (http://rmod.lille.inria.fr/web/pier/software/Fuel) >> If you encounter any bugs or have suggestions, please contact us on the Fuel mailing list (http://lists.gforge.inria.fr/cgi-bin/mailman/roster/pharo-fuel) or create a new issue in our bug tracker (https://code.google.com/p/fuel/) >> >> We want to thank everyone who contributed to this release (by keyboard or opinion) and also all of those people who actively use Fuel. >> >> Cheers, >> Max >

March 1, 2014

Re: [Pharo-dev] [squeak-dev] [ANN] Fuel 1.9.3

by Martin Dias

On Wed, Feb 26, 2014 at 10:13 PM, Max Leske <maxleske(a)gmail.com> wrote: > Dear fellow Smalltalkers > > Mariano, Martin and myself are happy to announce Fuel version 1.9.3 which > includes the follwing changes to 1.9 (1.9.1 and 1.9.2 were never officially > announced): > > - (feature) the #fuelReplacement selector offers the ability to statically > replace an object (e.g. with nil) during analysis. This can lead to > significantly smaller graphs and improved speed when serializing large > graphs > - (feature) serialize the same graph that was analyzed instead of > retrazing the graph during serialization. This prevents changes in the > graph from happening between analysis and serialization > - (change) store source when serializing CompiledMethod objects. Needed > because Opal does not allow decompilation > - (fix) migrate variables across hierarchy > - (feature) Object>>serializeToFileNamed: shortcut for serializing > arbitrary objects > - (fix) better compression for LargeNegativeIntegers ( > https://pharo.fogbugz.com/f/cases/12052/Fuel-could-store-LargeNegativeInteg… > ) > > Pharo30 already includes most of these changes (integration request: > https://pharo.fogbugz.com/f/cases/13000/Integrate-Fuel-1-9-3) > > This release runs with: > - Pharo: 1.1.1, 1.1.2, 1.2, 1.2.2, 1.3, 1.4, 2.0, 3.0 > - Squeak: 4.1, 4.2, 4.3, 4.4, 4.5 > > The documentation is not up to date yet but we will remedy that situatoin > within the next couple of days ( > http://rmod.lille.inria.fr/web/pier/software/Fuel) > If you encounter any bugs or have suggestions, please contact us on the > Fuel mailing list ( > http://lists.gforge.inria.fr/cgi-bin/mailman/roster/pharo-fuel) or create > a new issue in our bug tracker (https://code.google.com/p/fuel/) > > We want to thank everyone who contributed to this release (by keyboard or > opinion) and also all of those people who actively use Fuel. > > Cheers, > Max > Thank you Max for all your efforts in all aspects: in code, in continuous integration, in support for users, etc. MartÃn

March 1, 2014

Re: [Pharo-dev] Phratch one-click

by btc＠openinworld.com

jannik laval wrote: > Dears, > > Phratch has now a portable version: > https://ci.inria.fr/pharo-contribution/view/Phratch/job/Phratch-OneClick/ > > Thanks to JB Arnaud, the Jenkins is configured to take the latest > one-click Pharo for each platform and install all the necessary > (Plugins, pngâ¦). > > Now, no need to install anything: just download the zip file for your > platform, unzip it and run Phratch. > > Enjoy ! > > -- > > ~~Jannik Laval~~ > Ãcole des Mines de Douai > Enseignant-chercheur > http://www.jannik-laval.eu > http://car.mines-douai.fr/ > Thats great to hear. I look forward to checking it out (just after clearing a few things from my pipeline). cheers -ben

March 1, 2014

Phratch one-click

by jannik laval

Dears, Phratch has now a portable version: https://ci.inria.fr/pharo-contribution/view/Phratch/job/Phratch-OneClick/ Thanks to JB Arnaud, the Jenkins is configured to take the latest one-click Pharo for each platform and install all the necessary (Plugins, png...). Now, no need to install anything: just download the zip file for your platform, unzip it and run Phratch. Enjoy ! -- ~~Jannik Laval~~ Ãcole des Mines de Douai Enseignant-chercheur http://www.jannik-laval.eu http://car.mines-douai.fr/

March 1, 2014

Re: [Pharo-dev] Gettext broken in Pharo 3.0

by Usman Bhatti

Hi Johan, On Sat, Mar 1, 2014 at 10:47 AM, Johan Brichau <johan(a)inceptive.be> wrote: > > On 01 Mar 2014, at 09:57, Johan Brichau <johan(a)inceptive.be> wrote: > > > More is needed because I notice the exporter is not detecting the > domain<->categories mapping anymore. > > On second view, it seems the Seaside package for gettext is not compatible > anymore with changes in recent history. > So, gettext on its own should be good to go now. > > Let me know, since I am now mostly focusing on the seaside extension that > uses it > For me, it is working now and the problem seems to be fixed. I have a desktop app so I am not using it with Seaside and everything seems to be working normally. tx a lot, Usman > > cheers > Johan >

March 1, 2014