- Pharo-dev - lists.pharo.org

[Pharo-project] [COTDC] 66 - LogicalFont
by laurent laffont May 19, 2011

May 19, 2011

Today: LogicalFont Comment Of The Day Contest - One Day One Comment Rules: #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). #2: If you cannot comment it, deprecate it. Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest Laurent

1 1

[Pharo-project] Mouse wheel
by Alexandre Bergel May 19, 2011

May 19, 2011

Hi! -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 0

[Pharo-project] Strange SmalltalkImage>>startUp
by Igor Stasenko May 19, 2011

May 19, 2011

Can someone explain me, why it does: startUp SystemChangeNotifier uniqueInstance notify: Smalltalk ofAllSystemChangesUsing: #event: why not doing it once in #initialize (on instance side, since Smalltalk is instance of SmalltalkImage)? -- Best regards, Igor Stasenko AKA sig.

1 0

[Pharo-project] Problem with Pharo 1.3 in Windows
by Torsten Bergmann May 19, 2011

May 19, 2011

Stef wrote >Now my main questions are Hey ... dont take me wrong. I want the build server to build the VMs too, I want a repeatable process and a reliable VM. I appreciate that we change this!!! We all know that if VM development is dependent on a single maintainer person then nobody would invest into Pharo, Squeak or Cuis since the truck factor* is one. I support all this. Remember: I was the one who wrote the first ConfigurationOfVMMaker so that it is easy to get all the bits and pieces. I want to make it easier for people to dive into VM building. The windows build slave is a huge step forward ... we can not only build the VM and installer ... we can also run the tests on Windows too to see if there are platform specific issues. Cool and hardly needed! But someone (person or team) has to wear the Win32 VM "hat" to check contributions or help fixing a bug. So may question is what is the direction we will take here? It looks like the standard SqueakWin32 VM is unmaintained since the last release is from July 2010. We still have no Alien, we still have no callbacks. Yes, there is Cog whose code base is newer but I think Eliots focus is on speed rather than functionality. Will we fork from standard VM, will we participate in Eliots work or will we fork an own using git and maintain it by picking pieces from the other VMs? Also: what can we do to reach the goal of feature complete VM's with aligned version numbers. I think this means to participate on lists like "vm-dev"... But maybe I'm just too impatient... Bye T. *the truck factor = The number of people on your team who have to be hit with a truck before the project is in serious trouble" -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

3 2

Re: [Pharo-project] Problem with Pharo 1.3 in Windows
by Marcus Denker May 19, 2011

May 19, 2011

On May 18, 2011, at 10:24 PM, StÃ©phane Ducasse wrote: > Hi Santiago > > which VM are you using. I used a new VM to build 1.2.2. I did the same mistake when building 1.2.1 So I will do it again. This situation with the thousands of different VMs is *impossible*. We need to fix that. > Did you try with the VM shipped with the one-click image of 1.2.2? > The one-click on hudson I guess does not work becuase of that... We need to finish the auto build of the VM. We need to ship one VM per Release. Else we will end up in a mess. -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 2

[Pharo-project] Problem with Pharo 1.3 in Windows
by Torsten Bergmann May 19, 2011

May 19, 2011

Marcus >We have system that builds VMs from the latest soures automatically. >No need to wait for anyone. Does this "build system" magically write new code for the platform, fix bugs or implement the platform specific code for new plugins? There has to be at least one maintainer of the (win32)VM otherwise "latest soures" always points to the same version and no build system is required at all !!! The platform specific VM code needs maintenance ... either we continue to use the code base/versions from Andreas for regular VM and the code base/version from Eliot for the Cog VM or we fork ... Dont know if we have the resources to fork and maintain own VM's. On the other side Squeak Win32 VM is outdated anyway (SqueakVM-Win32-4.1.1-src.zip if from July 2010). I know many of you dont care about/hate Windows but if Pharo wants to be accepted in the larger commercial market then there is no way around a well maintained Win32 port. >I unsubscribed from all Squeak lists after 3.9. And that was final. "vm-dev" is for the VM which is currently for Squeak, Cuis, Pharo, ... You dont have to subscribe again, just check the archive: http://lists.squeakfoundation.org/pipermail/vm-dev/ Bye T. -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

2 2

[Pharo-project] Problem with Pharo 1.3 in Windows
by Torsten Bergmann May 19, 2011

May 19, 2011

>And for 1.3, we should not release it until Hudson/Jenkinds can build the >complete thing *with version numbers*. +1 Bye T. -- NEU: FreePhone - kostenlos mobil telefonieren! Jetzt informieren: http://www.gmx.net/de/go/freephone

1 0

[Pharo-project] Problem with Pharo 1.3 in Windows
by Torsten Bergmann May 19, 2011

May 19, 2011

Marcus wrote >This situation with the thousands of different VMs is *impossible*. We need >to fix that. If on Windows you should really use the installer for Pharo 1.2.2. from the download page. This will give you the two VM's: standard and Cog and you can use them to start all images from your HD. Since both have a different icon (also for the Pharo window) you always know which one you start/running on. Just give it a try, its simple. Since the Pharo.exe and PharoCog.exe also have the version number in the resource section you can right click on it in explorer and check which code version/revision they have (see attached screenshot). Bye T. -- NEU: FreePhone - kostenlos mobil telefonieren und surfen! Jetzt informieren: http://www.gmx.net/de/go/freephone

3 3

[Pharo-project] Problem with Pharo 1.3 in Windows
by Torsten Bergmann May 19, 2011

May 19, 2011

Henrik Sperre Johansen >Here's how we do it for our application: PLEASE NO. Why use Reshacker? Its just a hacker tool to manipulate the resource section in an EXISTING EXE file. I remember that this was the recommended way of a well known commercial smalltalk vendor to customize the VM icon. But this is just a workaround since the VM source code was not available there. Maybe it is OK for Henrik too since he dont want to look into VM building. But for Pharo WE HAVE the VM sources and now also a win build slave for hudson therefore should just use a custom *.rc for the build. I once suggested this to Andreas, he integrated it and his standard Win32 VM includes a versioninfo in the Squeak.rc file. I also suggested it to Eliot but he didnt included it (yet). I dont really care if he integrates into Cog since for a customized Pharo VM we use a custom "PharoCog.rc" file anyway (instead of Squeak.rc) during the build step. Read my post here, including the correct files for Cog: http://lists.gforge.inria.fr/pipermail/pharo-project/2011-May/049093.html If you copy them into the dir where Makefile lives you just have to change the name of the VM to build in the Makefile See also "Customization" at http://squeakvm.org/win32/compiling.html So if you switch to VM = MyKillerApp in the Makefile the build includes MyKillerApp.def.in MyKillerApp.rc instead of Squeak.def.in/Squeak.rc And in MyKillerApp.rc you can set the version info and point to a custom MyKillerApp.ico. And in the end you get a branded MyKillerApp.exe Simple! Bye T. -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

2 1

Re: [Pharo-project] Problem with Pharo 1.3 in Windows
by Marcus Denker May 19, 2011

May 19, 2011

On May 19, 2011, at 10:08 AM, Torsten Bergmann wrote: > > Marcus wrote: >> We *neeeeeeed* for every version of Pharo a VM that has *just* the same >version number. > > I think the problem was and (maybe still is) that there > were no aligned VM releases. It's dependent on the VM maintainer > time and what he included (fixes, new plugins). > > So on each platform there was an own custom versioning scheme > (one for mac, one for windows, ...). > > On windows: for standard vm Andreas aligned with Squeak releases: > http://squeakvm.org/win32/release/?C=M;O=D > and Eliot is oriented towards his SVN revision number > http://www.mirandabanda.org/files/Cog/VM/ > We have system that builds VMs from the latest soures automatically. No need to wait for anyone. > But there was a discussion on VM versioning on vm-dev list. > Maybe you should discuss it there. > I unsubscribed from all Squeak lists after 3.9. And that was final. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0