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

Re: [Pharo-project] Do you still need a Linux VM with FreeType?

by StÃ©phane Ducasse

> The recompiling gets really more important as soon as we go for > example for > Eliot's closure implementation... that I would want to have in as > soon as possible. So marcus focus on that and let us deal with crap removal. The list you gave is good. I think that this is important to turn the TODO into issue (may be you did that) so that people can focus on one task. Stef

Sept. 25, 2008

Re: [Pharo-project] Fwd: [Seaside-dev] preliminary Seaside 2.9 alpha universe

by StÃ©phane Ducasse

why can we have an installer script or mcm ? We should be able to have one click install too. Stef On Sep 24, 2008, at 10:55 PM, Adrian Lienhard wrote: > The new and easy way to load Seaside takes up to 10 steps (see > below). We should try to make this even less painful in Pharo. I > assume, having Universes pre-loaded will already reduce half of the > steps, but how can it be further simplified? > > Adrian > > Begin forwarded message: > >> From: "Philippe Marschall" <philippe.marschall(a)gmail.com> >> Date: September 24, 2008 10:21:16 PM GMT+02:00 >> To: "Seaside - developer list" <seaside-dev(a)lists.squeakfoundation.org >> > >> Subject: [Seaside-dev] preliminary Seaside 2.9 alpha universe >> Reply-To: Seaside - developer list <seaside-dev(a)lists.squeakfoundation.org >> > >> >> Hi >> >> Seaside 2.9 was always hard to load. We always said that we would fix >> this and this is a preview of what we expect the solution to look >> like. >> >> After some evaluation of what is available in Squeak we had only two >> options, either start from scratch or use universes [1]. We decided >> to >> give universes a shot. Universes is something like a debian >> distribution universe for squeak. >> >> So how do you load this stuff: >> 1. get Universes, if you don't already have it (3.10) >> 1.1 get an XML parser [2] >> 1.2 get universes [3] >> 1.3 optionally the the OB universe browser [4] >> 2. save the *.packages to your image directory >> 3. load the attached .mcz >> 4. evaluate UUniverse switchSystemToUniverse: UUniverse >> seasideAndServers >> 5. in the world menu open a "Universe Browser" either basic or >> enhanced >> 6. "update list from network" >> 7. choose a distribution >> 8. choose a server >> >> There are still some unsolved issues like the naming of alpha an beta >> versions. We probably want website integration as well. One possible >> change would be to move the tests to a separate tests category. >> >> [1] http://wiki.squeak.org/squeak/3785 >> [2] http://www.squeaksource.com/universes.html >> [3] http://www.squeaksource.com/XMLSupport.html >> [4] http://www.squeaksource.com/OBUniverse.html >> >> Cheers >> Philippe > <Seaside-Universe-pmm.18.mcz><seaside.packages><servers.packages> >> >> _______________________________________________ >> seaside-dev mailing list >> seaside-dev(a)lists.squeakfoundation.org >> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 25, 2008

Re: [Pharo-project] about preparing the first release

by StÃ©phane Ducasse

> >> Hi guys >> >> I will work using the pinesoft etoy removal package. >> But it can take time to do that carefully since etoy put its >> fingers everywhere. >> Now I would really like that we define a date for the first release. >> I would really like to have something for maximum end of october. >> What about you? > > Sounds good. > > We should also think about if we do a beta phase before releasing > and if we will maintain the most recent released version? I think if > we continue making radical changes, we need to maintain the most > recent stable release, that is, to apply critical bug fixes to it. Sure this is really important. > And, what numbering scheme do we use? > > I'd suggest the common major.minor[.maintenance] scheme starting > with "1.0". > The first maintenance release then would be 1.0.1 and the following > release would be 1.1 etc. An increase of the major digit would only > be justified when fundamental changes are introduced (like image > format change). > ok for me. Stef

Sept. 25, 2008

Re: [Pharo-project] Re: Re: Re: Re: [ANN] Demo with both Truetype+Polymorph

by Marcus Denker

On 24.09.2008, at 21:57, StÃ©phane Ducasse wrote: > thanks for the report. > I guess that marcus will look into that. I do not know how he made > the one click precisely. > Can you put a report on the bugtracker? I will not have time to look at this for the next days. I really need to work on the SNF proposal, securing my funding for the next months is kind of important even for pharo ;-) Marcus -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

Sept. 25, 2008

Re: [Pharo-project] Do you still need a Linux VM with FreeType?

by Marcus Denker

On 24.09.2008, at 23:16, <bryce(a)kampjes.demon.co.uk> <bryce(a)kampjes.demon.co.uk > wrote: > > I've stabilised the changes I was working on so now's a reasonable > time for me to look at this if it's still required. Is it? > > For now, I just used the vm from the seaside package and copied all th dll's in from the freetype package. This seems to work... The recompiling gets really more important as soon as we go for example for Eliot's closure implementation... that I would want to have in as soon as possible. Marcus -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

Sept. 25, 2008

Re: [Pharo-project] Do you still need a Linux VM with FreeType?

by Igor Stasenko

2008/9/25 <bryce(a)kampjes.demon.co.uk>: > > I've stabilised the changes I was working on so now's a reasonable > time for me to look at this if it's still required. Is it? > > Exupery already needs VMs for all major platforms, so I'm thinking > about merging that requirement with what Pharo needs. I can build > Linux VMs easily as it's my main development platform. Other platforms > depend on time, so far development has been more important than > maintaining ports for me. > Hi Bryce, i'm already added platform source for linux. You can see it on https://gforge.inria.fr/frs/?group_id=1299 page. I would appreciate if you help how to add dependency in linker (to link with -lfreetype) , if plugin is compiled in. Otherwise it require to change a makefile to complete a build. Btw, same for B3DAcceleratorPlugin - it needs adding -lgl > Bryce > > _______________________________________________ > 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. 24, 2008

[Pharo-project] Do you still need a Linux VM with FreeType?

by bryce＠kampjes.demon.co.uk

I've stabilised the changes I was working on so now's a reasonable time for me to look at this if it's still required. Is it? Exupery already needs VMs for all major platforms, so I'm thinking about merging that requirement with what Pharo needs. I can build Linux VMs easily as it's my main development platform. Other platforms depend on time, so far development has been more important than maintaining ports for me. Bryce

Sept. 24, 2008

[Pharo-project] Fwd: [Seaside-dev] preliminary Seaside 2.9 alpha universe

by Adrian Lienhard

The new and easy way to load Seaside takes up to 10 steps (see below). We should try to make this even less painful in Pharo. I assume, having Universes pre-loaded will already reduce half of the steps, but how can it be further simplified? Adrian Begin forwarded message: > From: "Philippe Marschall" <philippe.marschall(a)gmail.com> > Date: September 24, 2008 10:21:16 PM GMT+02:00 > To: "Seaside - developer list" <seaside- > dev(a)lists.squeakfoundation.org> > Subject: [Seaside-dev] preliminary Seaside 2.9 alpha universe > Reply-To: Seaside - developer list <seaside-dev(a)lists.squeakfoundation.org > > > > Hi > > Seaside 2.9 was always hard to load. We always said that we would fix > this and this is a preview of what we expect the solution to look > like. > > After some evaluation of what is available in Squeak we had only two > options, either start from scratch or use universes [1]. We decided to > give universes a shot. Universes is something like a debian > distribution universe for squeak. > > So how do you load this stuff: > 1. get Universes, if you don't already have it (3.10) > 1.1 get an XML parser [2] > 1.2 get universes [3] > 1.3 optionally the the OB universe browser [4] > 2. save the *.packages to your image directory > 3. load the attached .mcz > 4. evaluate UUniverse switchSystemToUniverse: UUniverse > seasideAndServers > 5. in the world menu open a "Universe Browser" either basic or > enhanced > 6. "update list from network" > 7. choose a distribution > 8. choose a server > > There are still some unsolved issues like the naming of alpha an beta > versions. We probably want website integration as well. One possible > change would be to move the tests to a separate tests category. > > [1] http://wiki.squeak.org/squeak/3785 > [2] http://www.squeaksource.com/universes.html > [3] http://www.squeaksource.com/XMLSupport.html > [4] http://www.squeaksource.com/OBUniverse.html > > Cheers > Philippe > _______________________________________________ > seaside-dev mailing list > seaside-dev(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

Sept. 24, 2008

Re: [Pharo-project] about preparing the first release

by Bill Schwab

Stef, Given a willingness to slip (either date or feature list) if the system is unstable, a deadline is great. Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029 >>> stephane.ducasse(a)inria.fr 09/24/08 4:08 PM >>> Hi guys I will work using the pinesoft etoy removal package. But it can take time to do that carefully since etoy put its fingers everywhere. Now I would really like that we define a date for the first release. I would really like to have something for maximum end of october. What about you? Stef _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 24, 2008

Re: [Pharo-project] about preparing the first release

by Adrian Lienhard

On Sep 24, 2008, at 22:08 , StÃ©phane Ducasse wrote: > Hi guys > > I will work using the pinesoft etoy removal package. > But it can take time to do that carefully since etoy put its fingers > everywhere. > Now I would really like that we define a date for the first release. > I would really like to have something for maximum end of october. > What about you? Sounds good. We should also think about if we do a beta phase before releasing and if we will maintain the most recent released version? I think if we continue making radical changes, we need to maintain the most recent stable release, that is, to apply critical bug fixes to it. And, what numbering scheme do we use? I'd suggest the common major.minor[.maintenance] scheme starting with "1.0". The first maintenance release then would be 1.0.1 and the following release would be 1.1 etc. An increase of the major digit would only be justified when fundamental changes are introduced (like image format change). Adrian

Sept. 24, 2008