January 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1

by Esteban Lorenzano

>> > > Yes true. However, maybe other people rather to put a real username and > password. I think this is more flexible. > It would be cool to hear opinions. Automated, I need it for continuous integration building

Jan. 10, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1

by Esteban Lorenzano

On 2010-01-09 20:21:19 -0300, Miguel Enrique CobÃ¡ Martinez <miguel.coba(a)gmail.com> said: > El dom, 10-01-2010 a las 00:08 +0100, Matthias Berth escribiÃ³: >> Hi Bill, >> >> this one works for me with the current pharo core 1.0 rc1, update upto 10505 >> >> "execute this:" >> Gofer new >> squeaksource: 'Loader'; >> package: 'Loader'; >> load. >> "then this" >> Loader new load: 'Pharo' version: '1.0-rc2.10505'. >> "then this" >> Loader new >> load: 'Seaside28' version: '2.8.4.2' >> >> The "Loader new load: 'Pharo' version: '1.0-rc2.10505'." loads a lot >> of additional pharo packages. I guess you won't need that just to get >> seaside working. >> > > But isn't the loader alpha yet? > > I mean, I am really expecting for Esteban to release it because is more > concise to write commands, but the issue here is the testing of the 1.0 > release of pharo with the current available/stable tools, that is, > monticello, gofer and metacello. > > Cheers Yes it is alpha... but just because the lack of testing and documentation (and some complex functionality). I sent a script to Matthias I was using to prepare an image for something private... and at the same time test a little the loader package. I think is very usable now, but as I said, It lacks a lot of testing and documentation, but you can tryit if you want, a little early feedback can be very useful ;) The package has been refactored following Stef suggestions, now you should do something like this: Gofer new squeaksource: 'Loader': package: 'GoferProjectLoader'; load. Gofer project load: 'Seaside28' version: '2.8.4.2'. Cheers, Esteban pd: and now I'm going to prepare my backpack and go out on vacations, or my girlfriend will kill me :P

Jan. 10, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1

by Mariano Martinez Peck

On Sun, Jan 10, 2010 at 2:50 PM, Tudor Girba <tudor.girba(a)gmail.com> wrote: > Hi, > > Moose loads well and the tests work as expected. > Cool. Thanks for reporting Doru. > > I will try to work with this image for a while, although it kills me > not to see the packages :). > > Yes, I know. I miss packages too. Alexandre said he was going to work a bit with David to fix the current problems in O2. If this is done, you will then be able to evaluate: (ConfigurationOfPharo project version: '1.0-rc2.10505.2') load: 'StandardDevImageWithO2' But we need that someone fix that first. Thanks Mariano Cheers, > Doru > > > On 9 Jan 2010, at 18:13, Mariano Martinez Peck wrote: > > > Hi Folks/Beta-Testers! > > > > I have prepare a new PharoDev image. This image, has same > > differences with the previous ones that you should know: > > > > 1) This is the first Dev image I ever prepare. I adapt to Mac OS > > Damien's bash scripts to build them and I also cleanup all the > > Squeak stuff from those bash scripts. So, maybe there are some > > problems. Forgive me if this is the case. I would like you to check, > > not only the Image in itself but also the zip. The package.txt, > > changelog, the fonts, etc. > > > > 2) This image puts TrueType fonts again. We won't put StrikeFonts or > > DejaVu package until there is big bug with them. We know those fonts > > are faster, but still a bit buggy. If you fix those issues, cool! > > > > 3) This image DOES NOT include O2. I know there are a lot of people > > who use it (mostly in Moose), but unfortunately, this was a decision > > taken. O2 depends and overrides OB making this more unstable > > sometimes. The same as the TrueType, we will put O2 again when this > > can be perfectly load in a PharoCore image without anything about OB. > > Sorry, but we rather affect only O2 users and not all. If you want > > packages support, then help in O2 development. > > > > 4) In previous Dev images only tests from PharoCore were included. > > Now, it also includes the tests from the external packages loaded. > > > > 5) This image was build using Metacello configurations. If you want, > > compare the installScript.st from this image to the previous one. > > > > 6) There is no Web image this time. If you want to install Seaside > > 2.8.4 evaluate: > > > > Gofer new > > squeaksource: 'MetacelloRepository'; > > package: 'ConfigurationOfSeaside28'; > > load. > > > > (Smalltalk at: #ConfigurationOfSeaside28) load > > > > And if you want Seaside 3.0 evaluate: > > > > Gofer new > > squeaksource: 'MetacelloRepository'; > > package: 'ConfigurationOfSeaside30'; > > load. > > > > (Smalltalk at: #ConfigurationOfSeaside30) loadLatestVersion > > > > However, I am not sure if this is perfectly working in Pharo. > > > > > > > > Ok .... Here is the link: > https://gforge.inria.fr/frs/download.php/25156/pharo1.0-10505-rc1dev10.01.1… > > > > I will wait a couple of days now and I will also start to use this > > image for my development. If there are issues, report them. If we > > have big issues, this image is not release. On the other hand, if it > > works well, we release it. > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > www.tudorgirba.com > > "Problem solving should be concentrated on describing > the problem in a way that is relevant for the solution." > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 10, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1

by Esteban Lorenzano

Ok, I installed it and made a some-kind "web" image (Loading Seaside28 and Pier). The seaside and pier metacello configurations needs to specify the version because there is no stable version declared. The configuration line to install seaside is: (ConfigurationOfSeaside28 project version: '2.8.4.2') load. So far, is working pretty good :) Cheers, Esteban On 2010-01-09 14:13:40 -0300, Mariano Martinez Peck <marianopeck(a)gmail.com> said: > > > Hi Folks/Beta-Testers! > > I have prepare a new PharoDev image. This image, has same differences with > the previous ones that you should know: > > 1) This is the first Dev image I ever prepare. I adapt to Mac OS Damien's > bash scripts to build them and I also cleanup all the Squeak stuff from > those bash scripts. So, maybe there are some problems. Forgive me if this is > the case. I would like you to check, not only the Image in itself but also > the zip. The package.txt, changelog, the fonts, etc. > > 2) This image puts TrueType fonts again. We won't put StrikeFonts or DejaVu > package until there is big bug with them. We know those fonts are faster, > but still a bit buggy. If you fix those issues, cool! > > 3) This image DOES NOT include O2. I know there are a lot of people who use > it (mostly in Moose), but unfortunately, this was a decision taken. O2 > depends and overrides OB making this more unstable sometimes. The same as > the TrueType, we will put O2 again when this can be perfectly load in a > PharoCore image without anything about OB. > Sorry, but we rather affect only O2 users and not all. If you want packages > support, then help in O2 development. > > 4) In previous Dev images only tests from PharoCore were included. Now, it > also includes the tests from the external packages loaded. > > 5) This image was build using Metacello configurations. If you want, compare > the installScript.st from this image to the previous one. > > 6) There is no Web image this time. If you want to install Seaside 2.8.4 > evaluate: > > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfSeaside28'; > load. > > (Smalltalk at: #ConfigurationOfSeaside28) load > > And if you want Seaside 3.0 evaluate: > > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfSeaside30'; > load. > > (Smalltalk at: #ConfigurationOfSeaside30) loadLatestVersion > > However, I am not sure if this is perfectly working in Pharo. > > > > Ok .... Here is the link: > https://gforge.inria.fr/frs/download.php/25156/pharo1.0-10505-rc1dev10.01.1… > > I will wait a couple of days now and I will also start to use this image for > my development. If there are issues, report them. If we have big issues, > this image is not release. On the other hand, if it works well, we release > it. > > > Hi Folks/Beta-Testers! I have prepare a new PharoDev image. This ima= > ge, has same differences with the previous ones that you should know: <b= > r>1) This is the first Dev image I ever prepare. I adapt to Mac OS Damien&#= > 39;s bash scripts to build them and I also cleanup all the Squeak stuff fro= > m those bash scripts. So, maybe there are some problems. Forgive me if this= > is the case. I would like you to check, not only the Image in itself but a= > lso the zip. The package.txt, changelog, the fonts, etc. > > > > > > 2) This image puts TrueType fonts again. We won't put StrikeFonts o= > r DejaVu package until there is big bug with them. We know those fonts are = > faster, but still a bit buggy. If you fix those issues, cool! 3) Thi= > s image DOES NOT include O2. I know there are a lot of people who use it (m= > ostly in Moose), but unfortunately, this was a decision taken. O2 depends a= > nd overrides OB making this more unstable sometimes. The same as the TrueTy= > pe, we will put O2 again when this can be perfectly load in a PharoCore ima= > ge without anything about OB. > > > > > > Sorry, but we rather affect only O2 users and not all. If you want packages= > support, then help in O2 development. 4) In previous Dev images onl= > y tests from PharoCore were included. Now, it also includes the tests from = > the external packages loaded. > > > > > 5) This image was build using Metacello configurations. If you want, co= > mpare the installScript.st from this image to the previous one. 6) = > There is no Web image this time. If you want to install Seaside 2.8.4 evalu= > ate: > > > > Gofer new =A0=A0=A0 squeaksource: 'MetacelloRepository'; = > =A0=A0=A0 package: 'ConfigurationOfSeaside28'; =A0=A0=A0 load.<b= > r>=A0=A0=A0 (Smalltalk at: #ConfigurationOfSeaside28) load And i= > f you want Seaside 3.0 evaluate: > > Gofer new =A0=A0=A0 squeaksource: 'MetacelloRepository'; = > =A0=A0=A0 package: 'ConfigurationOfSeaside30'; =A0=A0=A0 load.<b= > r>=A0=A0=A0 (Smalltalk at: #ConfigurationOfSeaside30) loadLatestVersion= > However, I am not sure if this is perfectly working in Pharo. > > Ok .... Here is the link:=A0 <a href=3D"https://gforge.inria.fr/frs/downloa= > d.php/25156/pharo1.0-10505-rc1dev10.01.1.zip" target=3D"_blank">https://gfo= > rge.inria.fr/frs/download.php/25156/pharo1.0-10505-rc1dev10.01.1.zip</a><br= >> > I will wait a couple of days now and I will also start to use this imag= > e for my development. If there are issues, report them. If we have big issu= > es, this image is not release. On the other hand, if it works well, we rele= > ase it. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 10, 2010

[Pharo-project] how to import an icon

by Tudor Girba

Hi, I would like to import icons from external files in the image. These should be used for menus and buttons. How should I do that? What format should be used? What size? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow."

Jan. 10, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1

by Tudor Girba

Hi, Moose loads well and the tests work as expected. I will try to work with this image for a while, although it kills me not to see the packages :). Cheers, Doru On 9 Jan 2010, at 18:13, Mariano Martinez Peck wrote: > Hi Folks/Beta-Testers! > > I have prepare a new PharoDev image. This image, has same > differences with the previous ones that you should know: > > 1) This is the first Dev image I ever prepare. I adapt to Mac OS > Damien's bash scripts to build them and I also cleanup all the > Squeak stuff from those bash scripts. So, maybe there are some > problems. Forgive me if this is the case. I would like you to check, > not only the Image in itself but also the zip. The package.txt, > changelog, the fonts, etc. > > 2) This image puts TrueType fonts again. We won't put StrikeFonts or > DejaVu package until there is big bug with them. We know those fonts > are faster, but still a bit buggy. If you fix those issues, cool! > > 3) This image DOES NOT include O2. I know there are a lot of people > who use it (mostly in Moose), but unfortunately, this was a decision > taken. O2 depends and overrides OB making this more unstable > sometimes. The same as the TrueType, we will put O2 again when this > can be perfectly load in a PharoCore image without anything about OB. > Sorry, but we rather affect only O2 users and not all. If you want > packages support, then help in O2 development. > > 4) In previous Dev images only tests from PharoCore were included. > Now, it also includes the tests from the external packages loaded. > > 5) This image was build using Metacello configurations. If you want, > compare the installScript.st from this image to the previous one. > > 6) There is no Web image this time. If you want to install Seaside > 2.8.4 evaluate: > > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfSeaside28'; > load. > > (Smalltalk at: #ConfigurationOfSeaside28) load > > And if you want Seaside 3.0 evaluate: > > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfSeaside30'; > load. > > (Smalltalk at: #ConfigurationOfSeaside30) loadLatestVersion > > However, I am not sure if this is perfectly working in Pharo. > > > > Ok .... Here is the link: https://gforge.inria.fr/frs/download.php/25156/pharo1.0-10505-rc1dev10.01.1… > > I will wait a couple of days now and I will also start to use this > image for my development. If there are issues, report them. If we > have big issues, this image is not release. On the other hand, if it > works well, we release it. > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com "Problem solving should be concentrated on describing the problem in a way that is relevant for the solution."

Jan. 10, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1

by Lukas Renggli

>> Lukas is the official maintainer of the OB package for Pharo. >> Therefore I assume OB should be loaded from his repository... Lukas? > > Wait...this is not a little decision. This is really big. Because a lot of > people commits stuff to wiresong repository. How this will be merged ? where > people that wants to contribute to OB should commit ? You ask a maintainer to pull your changes from your or a separate public repository. Like about any other open-source project does. Linux. Pharo. Seaside. It does not work when everybody publishes random changes to a repository that everybody else is pulling from. Even if this looks like really open open open-source, it is the inferno. This is how you can turn in no time an excellent piece of software with hundreds of tests into battlefield of bugs, broken tests, and messed up design. Lukas - Lukas Renggli http://www.lukas-renggli.ch

Jan. 10, 2010

Re: [Pharo-project] Categorizing method extension with pragma

by CÃ©drick BÃ©ler

2010/1/10 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > yes now we should pay attention about metadata in the methods. > yes this is an extra thing to do but it might be necessary. Also it can be sort of "transparent". Imagine I download an image and start my new project. So I use a "project browser" (a packages context oriented browser), ie a classical browser that create new packages and each time I add extension methods, the metadata are associated automaticaly. > Now what we can have also is that the ***package*** knows the extension > this is what my dead slowing making progress impelemntation is doing. > uhm ok :) Maybe better.. so I'll wait and see ;) Would that autorize to have a classic method category name ? or will it still be *apackage ? What's difficult here to me is that maybe we need to stay backward compatible or see if squeakers want to adopt the same strategy wich is not that easy I guess. > > On Jan 10, 2010, at 2:08 PM, CÃ©drick BÃ©ler wrote: > > > Hi, > > > > Just a 2 cents thought on method extension. > > > > Why not associating a pragma instead of using the package name prefixed > by a star ? > > > > Say there is a package named MyPackage and I override a method in String > or add a new one. What I'd like is keeping the original method category name > (or find an appropriate one) instead of using *mypackage. For instance: > > > > String>>aMethod > > <package: MyPackage> > > ... > > ... > > ^result > > > > > > Then, we would have to adapt monticello for that purpose. We could also > use dynamic protocols to get the list of extension method by package. > > > > What does other think ? I find it could be a good starting point to deal > with packages. > > > > > > > > -- > > CÃ©drick > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- CÃ©drick

Jan. 10, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1

by Mariano Martinez Peck

On Sun, Jan 10, 2010 at 2:15 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > Lukas is the official maintainer of the OB package for Pharo. > Therefore I assume OB should be loaded from his repository... Lukas? > > Wait...this is not a little decision. This is really big. Because a lot of people commits stuff to wiresong repository. How this will be merged ? where people that wants to contribute to OB should commit ? > Cheers, > Adrian > > PS: I don't know why testFinalizationOfEquals sometimes fails (also in > PharoCore) > I created the issue: http://code.google.com/p/pharo/issues/detail?id=1771 > PPS: Fixing testSymbolTableM6812 is on my todo list (it needs a change > in PharoCore) > > Cool. I created the issue: http://code.google.com/p/pharo/issues/detail?id=1772 > > On Jan 10, 2010, at 14:05 , Mariano Martinez Peck wrote: > > > > > > > On Sun, Jan 10, 2010 at 11:34 AM, Adrian Lienhard <adi(a)netstyle.ch> > > wrote: > > > > On Jan 9, 2010, at 22:32 , Mariano Martinez Peck wrote: > > > > > Thanks Benoit for the report and taking the time to run all the > > > tests. I > > > already knew that there are a lot failing tests. Unfortunately, > > > there is not > > > too much I can do: > > > > > > 1) Maintainers of packages with failures can tell me if they are > > > failing for > > > "my fault". I mean, because I don't load a dependency or something > > > like > > > that. And if this is the case, I can fix that. > > > > > > 2) I can remove all the packages that have failing tests -> I think > > > we will > > > load very few packages. > > > > > > 3) We should ask maintainers to fix them. Of course, there are > > > packages that > > > even don't have maintainers. > > > > > > thoughts about this ? > > > > Some time ago I individually talked with each maintainer and > > eventually we managed to get all tests pass. That was with the > > previous build of the Pharo image that Damien did. Now, I don't know > > which additional tests you have loaded (?) but either these need to be > > fixed or we should not load them. We want all tests to be green for > > the release. > > > > > > Adrian: Most of the failing tests are from OB. Someone said Lukas > > made all those tests green, but they are commited in his repo. > > Someone should merge that with the wiresong repo. If no one merge > > that, I don't know what to do: or remove them or keep them. > > > > The only 3 tests no related with OB that are failing are: > > > > ObjectFinalizerTests >> testFinalizationOfEquals > > > > This one is failure, but running it again, it is green. Any idea? > > > > ReleaseTest >> testUndeclared > > > > failes. > > > > WeakSetInspectorTest >> testSymbolTableM6812 > > > > Related to NewInspector. I cc Frederic. > > > > Cheers > > > > Mariano > > > > Cheers, > > Adrian > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 10, 2010

[Pharo-project] Object Buffer (implementation tryout)

by CÃ©drick BÃ©ler

Hi, I've always found the need to copy/paste object (not string) between say, an inspector/explorer and a workspace. So I did a small class called ObjectBuffer and some extension that provide this fonctionnality (see the attached picture). I added menu command so that 'buffer it' is accessible from text selection, inspector and explorer. I doubt the implementation is optimal but this is working so I decided to share and see if people would like it too To get the object stored: self buffer or ObjectBuffer buffer hth, -- CÃ©drick

Jan. 10, 2010