August 2009 - Pharo-dev - lists.pharo.org

[Pharo-project] New Pharo based on core 10413

by Damien Cassou

Please download and report problems: http://pharo-project.org/pharo-download -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Aug. 9, 2009

Re: [Pharo-project] a process to maintain non core package

by John M McIntosh

I believe Joseph Pelrine work on one for the "Squeak World Tour" fork. http://desk.org:8080/CampSmalltalk/Squeak%20World%20Tour%20Results From time to time he thinks of bring it up to date, but there is a general lack of interest... However I can ask him for a spec sheet/objectives for the product and see how they match to other proposals. If people are curious about why he would know a bit about package management then consider http://www.amazon.com/Mastering-Envy-Developer-Joseph-Pelrine/dp/0521666503 On 9-Aug-09, at 9:03 AM, Michael Roberts wrote: > do we have a list of candidate package management systems? > > cheers, > > Mike > -- = = = ======================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================

Aug. 9, 2009

Re: [Pharo-project] About v4 strike fonts

by John M McIntosh

Ok, yesterday I had grabbed the Pharo1.0beta latest update: #10401 from the download link on the pharo page in order to rebuild the iPhone ebook st80docs (I'll say more once Apple approves). So this morning I fired up the image using a macintosh carbon 4.1.1beta2U vm then executed >> | f1 f2 | >> f1 := Form extent: 8@8 depth: 32. >> f1 fillColor: (Color r: 1.0 g: 1.0 b: 0.7 alpha: 0.6). >> f2 := Form extent: 8@8 depth: 32. >> f2 fillColor: (Color r: 0.5 g: 1.0 b: 0.7 alpha: 0.7). >> (BitBlt toForm: f1) sourceForm: f2; combinationRule: 20; copyBits. >> (f1 colorAt: 2@2) alpha and I get 1.0 I note http://article.gmane.org/gmane.comp.lang.smalltalk.sapphire.devel/8433 Maybe you have the 2007 BitBltPlugin.bundle loaded? On 9-Aug-09, at 9:37 AM, Juan Vuletich wrote: > StÃ©phane Ducasse wrote: >> >> >> >> >> So I do not know what to think. I have the latest vm and this is >> the one which executed the image. >> Of course we will have to change this vmVersion to write the exact >> pharo image >> number which is here 10413 >> >> Stef >> >> > Neither do I. The attach is what I get. John, can you shed some > light on this? > > BTW, leaving now. Will be back in about 8 hours, and check mail then. > > Cheers, > Juan Vuletich > <display.png> -- = = = ======================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================

Aug. 9, 2009

Re: [Pharo-project] a process to maintain non core package

by Dale Henrichs

Mike, I have been working on Metacello which is a package management system for Smalltalk. Metacello is built on top of Monticello and should also be able to manage MC2 artifacts. Metacello runs on Squeak, Pharo and GemStone. It is currently in alpha as I am still working on making it "feature complete". Information for downloading it can be found on the Monticello mailing list - there is a tutorial (see the version 0.6 announcement). I created Metacello to address specific needs that I have run into while maintaining GLASS: - Named versions associated with lists of explicit Monticello file names. One can declare that version 0.3 consists of: 'Example-Core-anon.9' 'Example-Tests-anon.3' 'Example-AddOn-anon.1' 'Example-UI-anon.1' When one comes across an announcement of version 0.3 for the Example project you will know exactly which versions of the packages need to be loaded. Furthermore, you can evaluate an expression like the following to load version 0.3: (ExampleProject version: '0.3') load - Package to package dependencies. One can declare required packages like the following: 'Example-Core-anon.9' 'Example-Tests-anon.3' requires: 'Example-Core' 'Example-AddOn-anon.1' requires: 'Example-Tests' 'Example-UI-anon.1' requires: { 'OB'. 'Example-AddOn'. } From the above statements, the package load order is derived and used when you load the project: (ExampleProject version: '0.3') load It is also used to determine _which_ packages should be loaded when an expression like the following is executed: (ExampleProject version: '0.3') load: 'Example-AddOn' This statement causes 'Example-Core-anon.9', 'Example-Tests-anon.3', 'Example-AddOn-anon.1' to be loaded in order. - Package to Project dependencies. In the above example 'OB' is a named reference to the OmniBrowser project and if 'Example-UI' is loaded, then the OmniBrowser project will be loaded. - Conditional package declarations. One can declare package versions that will be conditionally loaded for Squeak, Pharo. or GemStone. For GemStone I also declare different package versions based on which version of GemStone is being run. There is more, including a spartan OB interface... Currently I am integrating Metacello into the GemStone/GLASS build process. Soon I will be using Metacello for managing updates for GLASS users - the version of GemTools running on the 1.0beta is managed with Metacello... In parallel I am working on making Metacello feature complete for the 1.0 release (only a couple features left on my list). The biggest item remaining is a tutorial covering the all of the features (or a least the most important). Metacello is under the MIT license. I think that Metacello addresses at least a couple of requirements for Pharo, but then I'm biased:) Dale ----- "Michael Roberts" <mike(a)mjr104.co.uk> wrote: | do we have a list of candidate package management systems? | | cheers, |

Aug. 9, 2009

Re: [Pharo-project] About v4 strike fonts

by John M McIntosh

10 years back the VM source was in the image, this included vmmaker and an encoded zip file for all the C source files need to build the VM on the platform, aka macintosh. Out of that the vmVersion primitive would just return the update number of the image used to build the VM because they were synchronized. Today that number has little meaning, and is different on each platform, since it reflects the image used to build the VM, and says nothing about which version of vmmaker was used to make the VM. http://isqueak.org/getAttributeIntoLength On 9-Aug-09, at 10:08 AM, Damien Cassou wrote: > 2009/8/9 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> So I do not know what to think. I have the latest vm and this is >> the one >> which executed the image. >> Of course we will have to change this vmVersion to write the exact >> pharo >> image >> number which is here 10413 > > I think that the version printed is the one that generated the VM > sources. You can't change it without regenerating the VM or hacking > the C source code. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Lambdas are relegated to relative obscurity until Java makes them > popular by not having them." James Iry > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- = = = ======================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================

Aug. 9, 2009

Re: [Pharo-project] About v4 strike fonts

by Damien Cassou

2009/8/9 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > So I do not know what to think. I have the latest vm and this is the one > which executed the image. > Of course we will have to change this vmVersion to write the exact pharo > image > number which is here 10413 I think that the version printed is the one that generated the VM sources. You can't change it without regenerating the VM or hacking the C source code. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Aug. 9, 2009

Re: [Pharo-project] [ANN] 10413

by Damien Cassou

On Sun, Aug 9, 2009 at 3:32 PM, StÃ©phane Ducasse<stephane.ducasse(a)inria.fr> wrote: > Now it should be easier for people that want to test strike fonts (one > file to load) Why would Strike fonts be necessary? We have FreeType and a good looking font by default in Pharo non-core. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Aug. 9, 2009

Re: [Pharo-project] a process to maintain non core package

by Keith Hodges

Adrian Lienhard wrote: > Hi, > > I really think we need a package management system and a process to > maintain it. > > The goal is that loading and using non-core packages "just > works" (unlike for instance SqueakMap, where loading more often fails > than succeeds because there are a lot of obsolete packages and a > dependency mechanism is missing). > > - There should be a responsible maintainer for each package > - For each package there should be a known way to discuss and report > problems > - A gate keeper includes and removes packages from the set depending > on their status > > This limits the set of included packages (at least initially) but > would increase the quality and hence the user experience. > > Maybe there could be two sets, a stable and an unstable set. New > packages would first go to the unstable set and then move up to the > stable set after a while. > > An automated build process could load packages into new builds and > report the result of the tests. > > The package management system does not need to be very sophisticated, > but it should manage dependencies and have a simple GUI (to search for > packages and see what is already loaded). > > Cheers, > Adrian > > Half of what you describe is in Sake/Packages Keith

Aug. 9, 2009

Re: [Pharo-project] a process to maintain non core package

by Miguel Enrique CobÃ¡ Martinez

El dom, 09-08-2009 a las 14:26 +0200, Adrian Lienhard escribiÃ³: > - There should be a responsible maintainer for each package > - For each package there should be a known way to discuss and report > problems > - A gate keeper includes and removes packages from the set depending > on their status > Yes, something like the Debian process, but simplified for pharo. Also it is important to have a way to track unmantained packages to avoid the squeak map problem.

Aug. 9, 2009

Re: [Pharo-project] About v4 strike fonts

by StÃ©phane Ducasse

So I do not know what to think. I have the latest vm and this is the one which executed the image. Of course we will have to change this vmVersion to write the exact pharo image number which is here 10413 Stef

Aug. 9, 2009