June 2011 - Pharo-dev - lists.pharo.org

[Pharo-project] I am serializing correctly with SIXX?

by Mariano Martinez Peck

>> serialize: anObject on: aStream | sws | sws := SixxWriteStream on: aStream. sws nextPut: anObject. sws close. >> materializeFrom: aStream | srs objects | srs := SixxReadStream on: aStream. objects := srs contents. srs close. ^ objects Is that correct or I am doing it wrong? All I want to do is to serialize a graph into a stream. The stream I am using is or this: (FileDirectory default forceNewFileNamed: 'Bench') or (RWBinaryOrTextStream on: '') I am not sure if I should be doing a #nextPut: or a #nextPutAll:. I mean, sometimes anObject is a collection and sometimes it is not. So, which one should I use? Thanks Mariano -- Mariano http://marianopeck.wordpress.com

June 2, 2011

Re: [Pharo-project] [update 1.3] #13237

by StÃ©phane Ducasse

thanks marcus. Stef On Jun 2, 2011, at 10:45 AM, Marcus Denker wrote: > 13237 > ----- > > Issue 4336: deprecated MorphicTextEditor > http://code.google.com/p/pharo/issues/detail?id=4336 > > Issue 4335: Remove more methods that are the same already in the superclass > http://code.google.com/p/pharo/issues/detail?id=4335 > > Issue 4334: Travial cleanup: some (to:)do: --> to:do > http://code.google.com/p/pharo/issues/detail?id=4334 > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >

June 2, 2011

[Pharo-project] [update 1.3] #13237

by Marcus Denker

13237 ----- Issue 4336: deprecated MorphicTextEditor http://code.google.com/p/pharo/issues/detail?id=4336 Issue 4335: Remove more methods that are the same already in the superclass http://code.google.com/p/pharo/issues/detail?id=4335 Issue 4334: Travial cleanup: some (to:)do: --> to:do http://code.google.com/p/pharo/issues/detail?id=4334 -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

June 2, 2011

Re: [Pharo-project] Compiling and using the FT2Plugin

by Schwab,Wilhelm K

Look for the // wks ... comment near the bottom of the attached. It's not much, but it can be a HUGE help when the paths are off, etc. I really should have used syslog(), but I don't see a good example of that. Either I never did it in the vm or lost track of it. The change goes in sqUnixExternalPrims.c, at least in the vms that I have hacked (non-Cog). Caveat emptor, etc. Good luck! Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Schwab,Wilhelm K [bschwab(a)anest.ufl.edu] Sent: Wednesday, June 01, 2011 8:59 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Compiling and using the FT2Plugin Alain, Sig's answer leaves me doubting my suspicion, but I will toss it out anyway, and since you are building a vm, you can pretty easily run through the exercise. First, the question: what (full path) library is the vm trying to load? It really is a plugin, so some of my more common concerns (extra slashes in the path, so.Name instead of libName.so, etc., go away - or do they??). Sadly, I don't see the code I want to give you on this machine. Maybe my laptop will have some friendly symlinks to the tweaked files. In short, I think that any time the (particularly linux) vm translates a number to to a name or a name to a path, and the subsequent load fails, it should say something somewhere about what it tried to open/load. I have used syslog() to good effect. It's nice because the logs rotate, giving some time for the user to look for it and yet not clog the drive with old news. Ok; I'll shut up and see if I can find some code for you :) Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Alain Plantec [alain.plantec(a)yahoo.com] Sent: Wednesday, June 01, 2011 2:00 PM To: pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Compiling and using the FT2Plugin Le 01/06/2011 19:46, Igor Stasenko a Ã©crit : > On 1 June 2011 19:20, Alain Plantec<alain.plantec(a)yahoo.com> wrote: >> Hi all, >> I try to build my own vm (ubuntu 10.04, virtualbox) >> Thanks to the **excellent** Mariano blog, I can compile, it runs ok except >> the FT2Plugin >> I always have the following error message while trying to load fonts: >> >> ioLoadModule(libFT2Plugin.so): >> libFT2Plugin.so: cannot open shared object file: No such file or directory >> >> I guess that it is because the plugin is unable to load libfreetype.so. >> does someone know what I am missing ? >> > i know. ;) > > i wanna add a correct settings for building this plugin on all > platforms. so we can ship a vm with this plugin by default. > But i haven't time to do it yet. So, if you find a solution how to do > it for unix, i will capture your knowledge in corresponding config(s) > :) ahhhhh! thanks Igor I'm not so stupid, its a problem :) ok, I will try Cheers Alain >> thanks >> Alain >> >

June 2, 2011

Re: [Pharo-project] Compiling and using the FT2Plugin

by Schwab,Wilhelm K

Alain, Sig's answer leaves me doubting my suspicion, but I will toss it out anyway, and since you are building a vm, you can pretty easily run through the exercise. First, the question: what (full path) library is the vm trying to load? It really is a plugin, so some of my more common concerns (extra slashes in the path, so.Name instead of libName.so, etc., go away - or do they??). Sadly, I don't see the code I want to give you on this machine. Maybe my laptop will have some friendly symlinks to the tweaked files. In short, I think that any time the (particularly linux) vm translates a number to to a name or a name to a path, and the subsequent load fails, it should say something somewhere about what it tried to open/load. I have used syslog() to good effect. It's nice because the logs rotate, giving some time for the user to look for it and yet not clog the drive with old news. Ok; I'll shut up and see if I can find some code for you :) Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Alain Plantec [alain.plantec(a)yahoo.com] Sent: Wednesday, June 01, 2011 2:00 PM To: pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Compiling and using the FT2Plugin Le 01/06/2011 19:46, Igor Stasenko a Ã©crit : > On 1 June 2011 19:20, Alain Plantec<alain.plantec(a)yahoo.com> wrote: >> Hi all, >> I try to build my own vm (ubuntu 10.04, virtualbox) >> Thanks to the **excellent** Mariano blog, I can compile, it runs ok except >> the FT2Plugin >> I always have the following error message while trying to load fonts: >> >> ioLoadModule(libFT2Plugin.so): >> libFT2Plugin.so: cannot open shared object file: No such file or directory >> >> I guess that it is because the plugin is unable to load libfreetype.so. >> does someone know what I am missing ? >> > i know. ;) > > i wanna add a correct settings for building this plugin on all > platforms. so we can ship a vm with this plugin by default. > But i haven't time to do it yet. So, if you find a solution how to do > it for unix, i will capture your knowledge in corresponding config(s) > :) ahhhhh! thanks Igor I'm not so stupid, its a problem :) ok, I will try Cheers Alain >> thanks >> Alain >> >

June 2, 2011

Re: [Pharo-project] [Metacello] A newly discovered Metacello bug (yet to be characterized)

by Dale Henrichs

Ocompletion-ul.102 was loaded because ConfigurationOfPharo 1.2.2 loads ConfigurationOfOmniBrowser 1.2.5 which loads ConfigurationOfOCompletion 1.3 which is not correct for Pharo 1.2.2 ... It looks like ConfigurationOfPharo 1.2.2 was introduced for Pharo 1.2.2 and previous versions of Pharo-1.2 were using ConfigurationOfPharo 1.2-beta2 which calls for ConfigurationOfOmniBrowser 1.2.4, which is presumably the version that should be used in Pharo 1.2. ConfigurationOfOmniBrowser 1.2.5 looks like a direct copy of ConfigurationOfOmniBrowser 1.3 and 1.3 _is_ targetted at Pharo1.3 ... With the way things are configured, any attempt to load a configuration that either directly or indirectly references ConfigurationOfOmniBrowser will likely fail... ....Now on to characterizing the Metacello bug:) Dale ----- Original Message ----- > The Seaside3.0.5 load failure in Pharo1.2.2-12353 is due to the fact > that Ocompletion-ul.102 is loaded in the image which is a package > that is part of ConfigurationOfOCompletion 1.4 (presumably targetted > at Pharo1.3 not Pharo1.2.2) ... In the earlier version of Pharo 1.2, > Ocompletion-ul.92 is loaded and it is part of > ConfigurationOfOCompletion 1.2.2 ... > > Not sure why Ocompletion-ul.102 was loaded as ConfigurationOfPharo > points to the correct version of ConfigurationOfOCompletion, so I'll > have to do more detective work... > > Dale > > ----- Original Message ----- > > Okay the odd behavior between Pharo1.2-12339, Pharo1.2.1-12345 and > > Pharo1.2.2-12353 can be attributed to a known Metacello issue: > > > > http://code.google.com/p/metacello/issues/detail?id=112 > > > > So we are only facing two bugs: > > > > - the issue reported by Lukas, where version OmniBrowser 1.2.3 is > > loaded on > > top of version 1.2.4 (when nothing should have been loaded). > > Which appears > > to be fixed by Metacello 1.0-beta.29 (still need a test case to > > reproduce > > the bug) > > - the Seaside3.0.5 load failure Pharo1.2.2-12353 that doesn't > > show > > up in earlier > > versions. This error has to do with > > OcompletionPharoCompatibility > > and is likely > > due to a configuration error somewhere. > > > > I'll keep on digging... > > > > Dale > > > > > > ----- Original Message ----- > > > > > > In the mail to Lukas below, I was able to identify a previously > > > unreported bug in Metacello1.0-beta.28.3.3 when loading > > > Seaside3.0.5 > > > into Pharo1.2-12339. In the process of characterizing the bug, I > > > discovered that the Seaside load was correct when using Metacello > > > 1.0-beta.29 (an unreleased version). > > > > > > However, when I tested Seaside3.0.5 and Metacello1.0-beta.29 > > > using > > > Pharo1.2.2-12353, I discovered more odd behavior and Seaside3.0.5 > > > hit errors during the load. There is something fishy going on and > > > at > > > this point in time the root cause is not obvious. > > > > > > The Metacello unit tests are passing in all three versions: > > > Pharo1.2-12339, Pharo1.2.1-12345 and Pharo1.2.2-12353. > > > > > > I am now in the process of attempting to characterize the bugs. > > > > > > I will keep you posted on my progress. > > > > > > Dale > > > > > > ----- Original Message ----- > > > > Lukas, > > > > > > > > I have looked specifically at Seaside3.0.5 and > > > > Pharo1.2-12339/PharoCore1.2-12336 > > > > and have found two things: > > > > > > > > 1. #stable version for ConfigurationOfOmniBrowser for 1.2 is > > > > 1.2.3 > > > > and it should be 1.2.4. > > > > 2. if OB 1.2.4 is already loaded then the version is > > > > downgraded > > > > to > > > > 1.2.3 > > > > > > > > Item #1 is a configuration issue and item #2 is a bug ... > > > > > > > > I had not heard that "many projects could no longer be loaded > > > > into > > > > Pharo1.2", so I was (and still am) blissfully unaware of the > > > > problems that folks are having. > > > > > > > > Seaside3.0.5 loads into Pharo1.2/PharoCore1.2 and passes all of > > > > the > > > > unit tests ... so there are no "load issues." The Seaside > > > > control > > > > panel works fine and I have not noticed any other > > > > OmniBrowser-related issues ... but then I don't live in the > > > > images > > > > day in and day out so there could be subtle issues. > > > > > > > > I am currently trying to characterized the "downgrade version" > > > > bug > > > > and will push out a fix as soon as I have one. > > > > > > > > Dale > > > > > > > > > > > > ----- Original Message ----- > > > > > > Here's the current state of 3.0.5: I saved the images from > > > > > > Jenkins > > > > > > and > > > > > > uploaded them to the web site. The change log has also been > > > > > > updated > > > > > > [1]. Everything but the Metacello configuration seems to > > > > > > work > > > > > > fine. > > > > > > If > > > > > > I load the Metacello configuration into a Pharo 1.2 it > > > > > > tries > > > > > > to > > > > > > load a > > > > > > version of OB that does not work in Pharo 1.2. > > > > > > > > > > As far as I know most configurations have been updated to > > > > > Pharo > > > > > 1.3 > > > > > already and many projects (I learned that with Glamour, > > > > > Mondrian, > > > > > Moose, Spy, ...) cannot be loaded into latest stable (Pharo > > > > > 1.2) > > > > > anymore. What surprised me more is that Metacello does not > > > > > allow > > > > > to > > > > > load old versions (at least this is true for the > > > > > configurations > > > > > I > > > > > had > > > > > problems with). So I guess we have the same problem here. > > > > > > > > > > I suggest that you load OB with this script: > > > > > https://github.com/renggli/builder/blob/master/scripts/omnibrowser.st > > > > > > > > > > Lukas > > > > > > > > > > -- > > > > > Lukas Renggli > > > > > www.lukas-renggli.ch > > > > > _______________________________________________ > > > > > seaside-dev mailing list > > > > > seaside-dev(a)lists.squeakfoundation.org > > > > > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev > > > > > > > > > _______________________________________________ > > > > seaside-dev mailing list > > > > seaside-dev(a)lists.squeakfoundation.org > > > > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev > > > > > > > > > >

June 2, 2011

Re: [Pharo-project] [Metacello] A newly discovered Metacello bug (yet to be characterized)

by Dale Henrichs

The Seaside3.0.5 load failure in Pharo1.2.2-12353 is due to the fact that Ocompletion-ul.102 is loaded in the image which is a package that is part of ConfigurationOfOCompletion 1.4 (presumably targetted at Pharo1.3 not Pharo1.2.2) ... In the earlier version of Pharo 1.2, Ocompletion-ul.92 is loaded and it is part of ConfigurationOfOCompletion 1.2.2 ... Not sure why Ocompletion-ul.102 was loaded as ConfigurationOfPharo points to the correct version of ConfigurationOfOCompletion, so I'll have to do more detective work... Dale ----- Original Message ----- > Okay the odd behavior between Pharo1.2-12339, Pharo1.2.1-12345 and > Pharo1.2.2-12353 can be attributed to a known Metacello issue: > > http://code.google.com/p/metacello/issues/detail?id=112 > > So we are only facing two bugs: > > - the issue reported by Lukas, where version OmniBrowser 1.2.3 is > loaded on > top of version 1.2.4 (when nothing should have been loaded). > Which appears > to be fixed by Metacello 1.0-beta.29 (still need a test case to > reproduce > the bug) > - the Seaside3.0.5 load failure Pharo1.2.2-12353 that doesn't show > up in earlier > versions. This error has to do with OcompletionPharoCompatibility > and is likely > due to a configuration error somewhere. > > I'll keep on digging... > > Dale > > > ----- Original Message ----- > > > > In the mail to Lukas below, I was able to identify a previously > > unreported bug in Metacello1.0-beta.28.3.3 when loading > > Seaside3.0.5 > > into Pharo1.2-12339. In the process of characterizing the bug, I > > discovered that the Seaside load was correct when using Metacello > > 1.0-beta.29 (an unreleased version). > > > > However, when I tested Seaside3.0.5 and Metacello1.0-beta.29 using > > Pharo1.2.2-12353, I discovered more odd behavior and Seaside3.0.5 > > hit errors during the load. There is something fishy going on and > > at > > this point in time the root cause is not obvious. > > > > The Metacello unit tests are passing in all three versions: > > Pharo1.2-12339, Pharo1.2.1-12345 and Pharo1.2.2-12353. > > > > I am now in the process of attempting to characterize the bugs. > > > > I will keep you posted on my progress. > > > > Dale > > > > ----- Original Message ----- > > > Lukas, > > > > > > I have looked specifically at Seaside3.0.5 and > > > Pharo1.2-12339/PharoCore1.2-12336 > > > and have found two things: > > > > > > 1. #stable version for ConfigurationOfOmniBrowser for 1.2 is > > > 1.2.3 > > > and it should be 1.2.4. > > > 2. if OB 1.2.4 is already loaded then the version is downgraded > > > to > > > 1.2.3 > > > > > > Item #1 is a configuration issue and item #2 is a bug ... > > > > > > I had not heard that "many projects could no longer be loaded > > > into > > > Pharo1.2", so I was (and still am) blissfully unaware of the > > > problems that folks are having. > > > > > > Seaside3.0.5 loads into Pharo1.2/PharoCore1.2 and passes all of > > > the > > > unit tests ... so there are no "load issues." The Seaside control > > > panel works fine and I have not noticed any other > > > OmniBrowser-related issues ... but then I don't live in the > > > images > > > day in and day out so there could be subtle issues. > > > > > > I am currently trying to characterized the "downgrade version" > > > bug > > > and will push out a fix as soon as I have one. > > > > > > Dale > > > > > > > > > ----- Original Message ----- > > > > > Here's the current state of 3.0.5: I saved the images from > > > > > Jenkins > > > > > and > > > > > uploaded them to the web site. The change log has also been > > > > > updated > > > > > [1]. Everything but the Metacello configuration seems to work > > > > > fine. > > > > > If > > > > > I load the Metacello configuration into a Pharo 1.2 it tries > > > > > to > > > > > load a > > > > > version of OB that does not work in Pharo 1.2. > > > > > > > > As far as I know most configurations have been updated to Pharo > > > > 1.3 > > > > already and many projects (I learned that with Glamour, > > > > Mondrian, > > > > Moose, Spy, ...) cannot be loaded into latest stable (Pharo > > > > 1.2) > > > > anymore. What surprised me more is that Metacello does not > > > > allow > > > > to > > > > load old versions (at least this is true for the configurations > > > > I > > > > had > > > > problems with). So I guess we have the same problem here. > > > > > > > > I suggest that you load OB with this script: > > > > https://github.com/renggli/builder/blob/master/scripts/omnibrowser.st > > > > > > > > Lukas > > > > > > > > -- > > > > Lukas Renggli > > > > www.lukas-renggli.ch > > > > _______________________________________________ > > > > seaside-dev mailing list > > > > seaside-dev(a)lists.squeakfoundation.org > > > > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev > > > > > > > _______________________________________________ > > > seaside-dev mailing list > > > seaside-dev(a)lists.squeakfoundation.org > > > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev > > > > > >

June 2, 2011

Re: [Pharo-project] [Metacello] A newly discovered Metacello bug (yet to be characterized)

by Dale Henrichs

Okay the odd behavior between Pharo1.2-12339, Pharo1.2.1-12345 and Pharo1.2.2-12353 can be attributed to a known Metacello issue: http://code.google.com/p/metacello/issues/detail?id=112 So we are only facing two bugs: - the issue reported by Lukas, where version OmniBrowser 1.2.3 is loaded on top of version 1.2.4 (when nothing should have been loaded). Which appears to be fixed by Metacello 1.0-beta.29 (still need a test case to reproduce the bug) - the Seaside3.0.5 load failure Pharo1.2.2-12353 that doesn't show up in earlier versions. This error has to do with OcompletionPharoCompatibility and is likely due to a configuration error somewhere. I'll keep on digging... Dale ----- Original Message ----- > > In the mail to Lukas below, I was able to identify a previously > unreported bug in Metacello1.0-beta.28.3.3 when loading Seaside3.0.5 > into Pharo1.2-12339. In the process of characterizing the bug, I > discovered that the Seaside load was correct when using Metacello > 1.0-beta.29 (an unreleased version). > > However, when I tested Seaside3.0.5 and Metacello1.0-beta.29 using > Pharo1.2.2-12353, I discovered more odd behavior and Seaside3.0.5 > hit errors during the load. There is something fishy going on and at > this point in time the root cause is not obvious. > > The Metacello unit tests are passing in all three versions: > Pharo1.2-12339, Pharo1.2.1-12345 and Pharo1.2.2-12353. > > I am now in the process of attempting to characterize the bugs. > > I will keep you posted on my progress. > > Dale > > ----- Original Message ----- > > Lukas, > > > > I have looked specifically at Seaside3.0.5 and > > Pharo1.2-12339/PharoCore1.2-12336 > > and have found two things: > > > > 1. #stable version for ConfigurationOfOmniBrowser for 1.2 is > > 1.2.3 > > and it should be 1.2.4. > > 2. if OB 1.2.4 is already loaded then the version is downgraded > > to > > 1.2.3 > > > > Item #1 is a configuration issue and item #2 is a bug ... > > > > I had not heard that "many projects could no longer be loaded into > > Pharo1.2", so I was (and still am) blissfully unaware of the > > problems that folks are having. > > > > Seaside3.0.5 loads into Pharo1.2/PharoCore1.2 and passes all of the > > unit tests ... so there are no "load issues." The Seaside control > > panel works fine and I have not noticed any other > > OmniBrowser-related issues ... but then I don't live in the images > > day in and day out so there could be subtle issues. > > > > I am currently trying to characterized the "downgrade version" bug > > and will push out a fix as soon as I have one. > > > > Dale > > > > > > ----- Original Message ----- > > > > Here's the current state of 3.0.5: I saved the images from > > > > Jenkins > > > > and > > > > uploaded them to the web site. The change log has also been > > > > updated > > > > [1]. Everything but the Metacello configuration seems to work > > > > fine. > > > > If > > > > I load the Metacello configuration into a Pharo 1.2 it tries to > > > > load a > > > > version of OB that does not work in Pharo 1.2. > > > > > > As far as I know most configurations have been updated to Pharo > > > 1.3 > > > already and many projects (I learned that with Glamour, Mondrian, > > > Moose, Spy, ...) cannot be loaded into latest stable (Pharo 1.2) > > > anymore. What surprised me more is that Metacello does not allow > > > to > > > load old versions (at least this is true for the configurations I > > > had > > > problems with). So I guess we have the same problem here. > > > > > > I suggest that you load OB with this script: > > > https://github.com/renggli/builder/blob/master/scripts/omnibrowser.st > > > > > > Lukas > > > > > > -- > > > Lukas Renggli > > > www.lukas-renggli.ch > > > _______________________________________________ > > > seaside-dev mailing list > > > seaside-dev(a)lists.squeakfoundation.org > > > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev > > > > > _______________________________________________ > > seaside-dev mailing list > > seaside-dev(a)lists.squeakfoundation.org > > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev > > >

June 2, 2011

[Pharo-project] A newly discovered Metacello bug (yet to be characterized)

by Dale Henrichs

In the mail to Lukas below, I was able to identify a previously unreported bug in Metacello1.0-beta.28.3.3 when loading Seaside3.0.5 into Pharo1.2-12339. In the process of characterizing the bug, I discovered that the Seaside load was correct when using Metacello 1.0-beta.29 (an unreleased version). However, when I tested Seaside3.0.5 and Metacello1.0-beta.29 using Pharo1.2.2-12353, I discovered more odd behavior and Seaside3.0.5 hit errors during the load. There is something fishy going on and at this point in time the root cause is not obvious. The Metacello unit tests are passing in all three versions: Pharo1.2-12339, Pharo1.2.1-12345 and Pharo1.2.2-12353. I am now in the process of attempting to characterize the bugs. I will keep you posted on my progress. Dale ----- Original Message ----- > Lukas, > > I have looked specifically at Seaside3.0.5 and > Pharo1.2-12339/PharoCore1.2-12336 > and have found two things: > > 1. #stable version for ConfigurationOfOmniBrowser for 1.2 is 1.2.3 > and it should be 1.2.4. > 2. if OB 1.2.4 is already loaded then the version is downgraded to > 1.2.3 > > Item #1 is a configuration issue and item #2 is a bug ... > > I had not heard that "many projects could no longer be loaded into > Pharo1.2", so I was (and still am) blissfully unaware of the > problems that folks are having. > > Seaside3.0.5 loads into Pharo1.2/PharoCore1.2 and passes all of the > unit tests ... so there are no "load issues." The Seaside control > panel works fine and I have not noticed any other > OmniBrowser-related issues ... but then I don't live in the images > day in and day out so there could be subtle issues. > > I am currently trying to characterized the "downgrade version" bug > and will push out a fix as soon as I have one. > > Dale > > > ----- Original Message ----- > > > Here's the current state of 3.0.5: I saved the images from > > > Jenkins > > > and > > > uploaded them to the web site. The change log has also been > > > updated > > > [1]. Everything but the Metacello configuration seems to work > > > fine. > > > If > > > I load the Metacello configuration into a Pharo 1.2 it tries to > > > load a > > > version of OB that does not work in Pharo 1.2. > > > > As far as I know most configurations have been updated to Pharo 1.3 > > already and many projects (I learned that with Glamour, Mondrian, > > Moose, Spy, ...) cannot be loaded into latest stable (Pharo 1.2) > > anymore. What surprised me more is that Metacello does not allow to > > load old versions (at least this is true for the configurations I > > had > > problems with). So I guess we have the same problem here. > > > > I suggest that you load OB with this script: > > https://github.com/renggli/builder/blob/master/scripts/omnibrowser.st > > > > Lukas > > > > -- > > Lukas Renggli > > www.lukas-renggli.ch > > _______________________________________________ > > seaside-dev mailing list > > seaside-dev(a)lists.squeakfoundation.org > > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev > > > _______________________________________________ > seaside-dev mailing list > seaside-dev(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev >

June 1, 2011

Re: [Pharo-project] Fwd: Background Changer

by GastÃ³n Dall' Oglio

great :) something that occurs to me that you could add is the ability to automatically change the background image among some preset time to time. Take a look at: http://www.squeaksource.com/Scheduler.html 2011/6/1 GastÃ³n Dall' Oglio <gaston.dalloglio(a)gmail.com> > Now it's working, thanks. I try it later. > > > 2011/6/1 Lemuus <lemuus(a)gmail.com> > >> I checked the repo and it's working. I also copied the project to >> squeaksource just in case: >> >> Gofer new >> squeaksource: 'BackgroundChanger'; >> package: 'BackgroundChanger'; >> load. >> Greetings, >> Daniel Galdames G. >> >> On Wed, Jun 1, 2011 at 10:56 AM, Alexandre Bergel < >> alexandre.bergel(a)me.com> wrote: >> >>> in case of >>> >>> Begin forwarded message: >>> >>> *From: *GastÃ³n Dall' Oglio <gaston.dalloglio(a)gmail.com> >>> *Date: *1 June 2011 10:47:28 GMT-04:00 >>> *To: *Pharo-project(a)lists.gforge.inria.fr >>> *Subject: **Re: [Pharo-project] Fwd: Background Changer* >>> *Reply-To: *Pharo-project(a)lists.gforge.inria.fr >>> >>> Lemuus or Alexandre, I get an error when I connect to the repository, you >>> could check it? I want to try! >>> Thanks. >>> >>> 2011/5/25 Mariano Martinez Peck <marianopeck(a)gmail.com> >>> >>>> nice tool :) >>>> I always put backgrounds. >>>> >>>> >>>> On Wed, May 25, 2011 at 5:36 PM, Alexandre Bergel < >>>> alexandre.bergel(a)me.com> wrote: >>>> >>>>> FYI >>>>> >>>>> Begin forwarded message: >>>>> >>>>> *From: *Lemuus <lemuus(a)gmail.com> >>>>> *Date: *24 May 2011 18:35:00 GMT-04:00 >>>>> *To: *pharo-chile(a)googlegroups.com >>>>> *Subject: **Background Changer* >>>>> *Reply-To: *pharo-chile(a)googlegroups.com >>>>> >>>>> Hi, >>>>> I tend change the background on Pharo a lot, so i made a little >>>>> application to change the background using an image gallery, so you can see >>>>> the image you want to put on the background. >>>>> You can load it with: >>>>> >>>>> Gofer new >>>>> url: 'http://lemuus.homelinux.org/lemuus/BackgroundChanger'; >>>>> package: 'BackgroundChanger'; >>>>> load. >>>>> >>>>> It register on the World menu->System->Change Background >>>>> It will ask for a directory with images, and then show you a gallery >>>>> with the images on that directory. >>>>> Then you can select an image, and select the layout for the background. >>>>> Greetings, >>>>> Daniel Galdames G. >>>>> >>>>> >>>>> -- >>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>>> Alexandre Bergel http://www.bergel.eu >>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Mariano >>>> http://marianopeck.wordpress.com >>>> >>>> >>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >>> >>> >> >

June 1, 2011