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

Re: [Pharo-project] Incompatibility between Pharo and Seasidehosting

by Adrian Lienhard

I tried what Lukas suggested. What happens is that Squeak starts up but then hogs the CPU and does not draw the GUI. However, an old version of Pharo, #10130, still works. Version #10172 does not work either, which suggests that its not Poymorph. My best guess is that its FreeType. I commented out the two startUp: methods of FreeTypeFontProvider and FreeTypeSettings, but without success. How could FreeType be disabled? Adrian On Feb 19, 2009, at 14:42 , Lukas Renggli wrote: >>> sqUnixMemory.c:172: uxGrowMemoryBy: Assertion `newDelta >= 0` >>> failed. >>> Aborted >> >> I don't think so because seasidehosting would print an error message >> in the system logs and it is not the case. > > I can only guess, but maybe the font-enumeration at startup causes the > VM to hang. Seaside Hosting uses quite an old and modified version of > the Unix VM. Maybe Adrian can verify that this is/is not the problem, > by opening a Pharo image on seasidehosting.st within an X session? > > Cheers, > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Feb. 19, 2009

Re: [Pharo-project] Question about Universes

by Lukas Renggli

The only problem i see is that it is not cleanly possible to support dependencies. If you want to install A and B that both depend on C, C will presumabely loaded twice. This does not happen with Sake and Universes. On 2/19/09, Alexandre Bergel <Alexandre.Bergel(a)inria.fr> wrote: > Thanks Lukas for sharing your experience with us. > I have a naive question. Personally, I like the way packages get > installed using class side methods on ScriptLoader. I have similar > scripts for Mondrian and other projects. > Is there something not convenient in that? > > Cheers, > Alexandre > > > On 19 Feb 2009, at 14:38, Lukas Renggli wrote: > >>> You are wrong about Sake I think. >> >> I know Sake. I've written a generator for builder.seaside.st. The >> result (or a modified version of it) is included with the Sake >> distribution as Seaside29Builder. >> >>> Sake can declare a universe of >>> known-to-work-together packages. Just take a class, declare the sake >>> tasks you know work together in the image you target and things will >>> be as in universe. >> >> Sure, you can use Sake to build something very similar to a Universe. >> However tasks are not declarative, but instead use a script to perform >> some actions. In most cases they call Installer to find and load an >> appropriate version (what is already scary in itself). >> >> I understand that Package Universe is too restrictive for some cases, >> however I wouldn't dare to replace it with Sake. Sake depends on a >> stack of hacks, it even uses its own compiler to allow uppercase >> method names. In the small codebase Code Critics finds 14 serious bugs >> like non existing inst-variable references and message sents that are >> not implemented anywhere. Of course there is not a single test. The >> way Sake calculates dependencies is totally strange, I am not sure if >> it is even correct. >> >> Lukas >> >> -- >> Lukas Renggli >> http://www.lukas-renggli.ch >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli http://www.lukas-renggli.ch

Feb. 19, 2009

Re: [Pharo-project] Question about Universes

by StÃ©phane Ducasse

thanks lukas Stef On Feb 19, 2009, at 2:38 PM, Lukas Renggli wrote: >> You are wrong about Sake I think. > > I know Sake. I've written a generator for builder.seaside.st. The > result (or a modified version of it) is included with the Sake > distribution as Seaside29Builder. > >> Sake can declare a universe of >> known-to-work-together packages. Just take a class, declare the sake >> tasks you know work together in the image you target and things will >> be as in universe. > > Sure, you can use Sake to build something very similar to a Universe. > However tasks are not declarative, but instead use a script to perform > some actions. In most cases they call Installer to find and load an > appropriate version (what is already scary in itself). > > I understand that Package Universe is too restrictive for some cases, > however I wouldn't dare to replace it with Sake. Sake depends on a > stack of hacks, it even uses its own compiler to allow uppercase > method names. In the small codebase Code Critics finds 14 serious bugs > like non existing inst-variable references and message sents that are > not implemented anywhere. Of course there is not a single test. The > way Sake calculates dependencies is totally strange, I am not sure if > it is even correct. > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 19, 2009

Re: [Pharo-project] Question about Universes

by Alexandre Bergel

Thanks Lukas for sharing your experience with us. I have a naive question. Personally, I like the way packages get installed using class side methods on ScriptLoader. I have similar scripts for Mondrian and other projects. Is there something not convenient in that? Cheers, Alexandre On 19 Feb 2009, at 14:38, Lukas Renggli wrote: >> You are wrong about Sake I think. > > I know Sake. I've written a generator for builder.seaside.st. The > result (or a modified version of it) is included with the Sake > distribution as Seaside29Builder. > >> Sake can declare a universe of >> known-to-work-together packages. Just take a class, declare the sake >> tasks you know work together in the image you target and things will >> be as in universe. > > Sure, you can use Sake to build something very similar to a Universe. > However tasks are not declarative, but instead use a script to perform > some actions. In most cases they call Installer to find and load an > appropriate version (what is already scary in itself). > > I understand that Package Universe is too restrictive for some cases, > however I wouldn't dare to replace it with Sake. Sake depends on a > stack of hacks, it even uses its own compiler to allow uppercase > method names. In the small codebase Code Critics finds 14 serious bugs > like non existing inst-variable references and message sents that are > not implemented anywhere. Of course there is not a single test. The > way Sake calculates dependencies is totally strange, I am not sure if > it is even correct. > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 19, 2009

Re: [Pharo-project] Incompatibility between Pharo and Seasidehosting

by Lukas Renggli

>> sqUnixMemory.c:172: uxGrowMemoryBy: Assertion `newDelta >= 0` failed. >> Aborted > > I don't think so because seasidehosting would print an error message > in the system logs and it is not the case. I can only guess, but maybe the font-enumeration at startup causes the VM to hang. Seaside Hosting uses quite an old and modified version of the Unix VM. Maybe Adrian can verify that this is/is not the problem, by opening a Pharo image on seasidehosting.st within an X session? Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Feb. 19, 2009

Re: [Pharo-project] Question about Universes

by Lukas Renggli

> You are wrong about Sake I think. I know Sake. I've written a generator for builder.seaside.st. The result (or a modified version of it) is included with the Sake distribution as Seaside29Builder. > Sake can declare a universe of > known-to-work-together packages. Just take a class, declare the sake > tasks you know work together in the image you target and things will > be as in universe. Sure, you can use Sake to build something very similar to a Universe. However tasks are not declarative, but instead use a script to perform some actions. In most cases they call Installer to find and load an appropriate version (what is already scary in itself). I understand that Package Universe is too restrictive for some cases, however I wouldn't dare to replace it with Sake. Sake depends on a stack of hacks, it even uses its own compiler to allow uppercase method names. In the small codebase Code Critics finds 14 serious bugs like non existing inst-variable references and message sents that are not implemented anywhere. Of course there is not a single test. The way Sake calculates dependencies is totally strange, I am not sure if it is even correct. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Feb. 19, 2009

Re: [Pharo-project] Incompatibility between Pharo and Seasidehosting

by Damien Cassou

Hi, On Thu, Feb 19, 2009 at 1:15 PM, Bruce O'Neel <squeak(a)pckswarms.ch> wrote: > Is it possible this error? > > sqUnixMemory.c:172: uxGrowMemoryBy: Assertion `newDelta >= 0` failed. > Aborted I don't think so because seasidehosting would print an error message in the system logs and it is not the case. -- Damien Cassou http://damiencassou.seasidehosting.st

Feb. 19, 2009

Re: [Pharo-project] Incompatibility between Pharo and Seasidehosting

by Bruce O'Neel

Hi, Is it possible this error? sqUnixMemory.c:172: uxGrowMemoryBy: Assertion `newDelta >= 0` failed. Aborted I get this following the procedure below on a Debian Lenny PPC system with Squeak 3.10-4. Gcc is 4.3.2. I do not get this on a Ubuntu hardy ppc system with the same version of squeak. Gcc is slightly older at 4.2.3. I've worked around this, for the moment, by adding -memory 200m to the squeak command line. I spent some weekend debugging this, but, I didn't find where the problem it is comes from. cheers bruce On Wed, Feb 18, 2009 at 04:45:00PM +0100, Damien Cassou wrote: > Hi, > > there is a problem with Pharo on Seasidehosting. Using a stock Pharo > image 10225, installing Seaside from Universe, it works perfectly fine > locally. As soon as I upload and run the image on Seasidehosting, it > doesn't work anymore.(503: Service Temporarily Unavailable). > There is nothing in the log files accessible through the > seasidehosting admin interface. > > You can see the problem on http://diagen.seasidehosting.st. > > To reproduce: > > - download Pharo version 10225 (newer versions have the annoying MIME problem) > - ScriptLoader new installingUniverse > - In the Universe browser, install Seaside. > - Upload the image and the changes file to a seasidehosting account > - Start the image > > Since all Pier images are now based on Pharo, this is a problem for > all new pier users. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Feb. 19, 2009

Re: [Pharo-project] Question about Universes

by Damien Cassou

On Thu, Feb 19, 2009 at 11:59 AM, Lukas Renggli <renggli(a)gmail.com> wrote: > - Sake is an imperative system, it uses Installer to load versions. > Installer either loads specific versions, or some version based on a > query string. I agree that this is much more powerful, however there > is no guarantee that all the packages that Installer thinks are the > right versions also work together. In the end random versions of > random packages from random repositories will be loaded in random > order into your image. Does this solve the problem? I don't think so. You are wrong about Sake I think. Sake can declare a universe of known-to-work-together packages. Just take a class, declare the sake tasks you know work together in the image you target and things will be as in universe. -- Damien Cassou http://damiencassou.seasidehosting.st

Feb. 19, 2009

Re: [Pharo-project] ABout MC browser size

by Gary Chambers

I assume you mean the WorkingCopyBrowser, it seems to have the correct default extent (580@200) as specified though the buttons in Watery 2 require extra width when rounded. Try 648@200. All is also font dependent though... Regards, Gary ----- Original Message ----- From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> To: "Pharo Development" <Pharo-project(a)lists.gforge.inria.fr> Sent: Wednesday, February 18, 2009 7:31 PM Subject: [Pharo-project] ABout MC browser size > Hi gary > > I do not really understand since I fixed the default size of the MC > browser in the past. > When I loaded your code I imagine that I merge and that they were no > conflict > so I do not understand why now I have again a wrong size. > Do you have an idea? > Did you merge back my little changes? > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Feb. 19, 2009