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

Re: [Pharo-project] Pharo 1.1: String-> arithmetic

by StÃ©phane Ducasse

because 'abc' * 2 does not make sense. and because this was limited anyway. better use plain collect:... > Hi Stef, > > In Pharo 1.1 the class String has not the protocol arithmetic and its methods... why? > Got errors when running some tests. Could I add them with a new version of Torch? I would prefer not. > > Vero > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 19, 2010

[Pharo-project] Pharo 1.1: String-> arithmetic

by Veronica Isabel Uquillas Gomez

Hi Stef, In Pharo 1.1 the class String has not the protocol arithmetic and its methods... why? Got errors when running some tests. Could I add them with a new version of Torch? Vero

May 19, 2010

Re: [Pharo-project] UUID on ubuntu 10.04

by laurent laffont

On Wed, May 19, 2010 at 9:42 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Apparently the student reinstalled her ubuntu from scratch (no incremental > installation) and the vm did not crash > anymore. > :( so we cannot reproduce the bug on Ubuntu now ........ Laurent > > Stef > > On May 17, 2010, at 9:16 PM, StÃ©phane Ducasse wrote: > > > I asked the student to try. > > > > Stef > > > > On May 17, 2010, at 9:06 PM, laurent laffont wrote: > > > >> On ArchLinux I have the problem when UUID is built external. Official > 4.0.3.2202 Unix VM binaries on http://squeakvm.org/unix/ works well for me > (UUID is internal). > >> > >> Can you try with this one click image I made once (uses 4.0.3.2202 > binaries) http://lolgzs.free.fr/pharo/Pharo-1.0-OneClick.zip > >> > >> Laurent Laffont > >> > >> http://pharocasts.blogspot.com/ > >> http://magaloma.blogspot.com/ > >> > >> > >> On Mon, May 17, 2010 at 8:24 PM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > >> I can confirm that this is exactly the same trace than the one reported > by laurent (no debug file). > >> > >> Stef > >> On May 17, 2010, at 7:51 PM, David T. Lewis wrote: > >> > >>> On Mon, May 17, 2010 at 07:38:59PM +0200, St?phane Ducasse wrote: > >>>> Hi guys > >>>> > >>>> I took seaside the latest one click image and when I have to save a MC > package > >>>> I get a core dump with UUID new:... > >>>> I checke the so.UUIDplugin is there and I do not understand. > >>>> Can somebody with a Ubuntu give a try to save something using MC and > the latest seaside one click. > >>> > >>> Hi Stef, > >>> > >>> This issue is being tracked here: > http://bugs.squeak.org/view.php?id=7358 > >>> > >>> It is not clear to me if the issue is resolved in the Ian's latest VM > >>> build, so if you or anyone else can confirm the UUID crash happening > >>> with this VM, that would be helpful to clarify. > >>> > >>> Dave > >>> > >>> > >>> _______________________________________________ > >>> 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 > > > > > > _______________________________________________ > > 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 >

May 19, 2010

Re: [Pharo-project] TORCH: supporting source-code change integration

by StÃ©phane Ducasse

do not add more buttons It would be better to use <menu> and cretae them automatically then yous would just be added dynamically. Stef On May 19, 2010, at 9:30 AM, Veronica Isabel Uquillas Gomez wrote: > Hola Mariano, > > Yup, I considered that but as there are already many buttons, I never tried.. > Will try it anyway... > > gracias, > Veronica > > On 18 May 2010, at 12:12, Mariano Martinez Peck wrote: > >> Hola VerÃ³nica! >> >> I love it!!! nice, very nice :) >> >> I will give you more feedback as far as I start to use it. >> The only thing I would add is a button in the MC. Look the attached screenshot. It would be cool not only to have it in the context menu, but in the MC broser...for example, next to "changes" button a "torch" button or something like that. >> >> I really like it. Moose and all it tools seems to be working in Pharo 1.1 so....maybe if people agree we can include this cool tool together with Mondrian and Glamour ? They have 460 green tests :) >> >> DEV!!!!!!!! >> >> :) >> >> On Tue, May 18, 2010 at 11:39 AM, Tudor Girba <tudor.girba(a)gmail.com> wrote: >> Hi Veronica, >> >> It is pretty impressive :). >> >> Would it be Ok if I added this on the Moose page? >> >> Cheers, >> Doru >> >> >> >> On 18 May 2010, at 11:21, StÃ©phane Ducasse wrote: >> >> Thanks veronica. >> lukas said that he was impressed this is a complement :) >> >> On May 18, 2010, at 11:00 AM, Veronica Isabel Uquillas Gomez wrote: >> >> Dear all, >> >> I would like to announce Torch, a tool for supporting source-code change integration. For now, it offers visualizations of the changes and enhanced change lists. >> Torch can be accessed through Monticello (in the main MC browser, in the repository browser or in the history browser). Selecting a version or slice, you can view the changes with Torch using the contextual menu. >> Once you open the Torch dashboard, you can access the enhanced change list or a detailed visualization via the contextual menu as well. >> >> Torch is available on SqueakSource, the repository is named Torch, and you need to load the ConfigurationOfTorch package. >> It runs in a dev or core image. >> >> For a dev image. >> - ConfigurationOfTorch loadVersion10 >> >> For a core image. >> 1) Set fonts - described in the attached file. >> 2) ConfigurationOfTorch loadDefault >> >> I would appreciate comments and feedback! >> >> Best Regards, >> VerÃ³nica Uquillas GÃ³mez >> Vrije University Brussel - SOFT Lab >> University of Lille - RMOD Team >> >> <torchFontsScript.st> >> >> >> >> _______________________________________________ >> 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 >> >> -- >> www.tudorgirba.com >> >> "Problem solving efficiency grows with the abstractness level of problem understanding." >> >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> <Picture 5.png>_______________________________________________ >> 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

May 19, 2010

Re: [Pharo-project] Fwd: Re: Decoding bug with XMLParser ?

by StÃ©phane Ducasse

excellent! Let us know this is good to get more support on the XML/DTD part. Stef On May 19, 2010, at 2:17 AM, jaayer wrote: > > > ============ Forwarded message ============ > From : jaayer<jaayer(a)zoho.com> > To : <alexandre.bergel(a)inria.fr> > Date : Tue, 18 May 2010 16:30:06 -0700 > Subject : Re: Decoding bug with XMLParser ? > ============ Forwarded message ============ > > ---- On Tue, 18 May 2010 02:29:18 -0700 Alexandre Bergel <alexandre.bergel(a)inria.fr> wrote ---- > >> To give a bit of context, the problem is: >> >> -=-=-=-=-=-=-=-=-=-=-=-= >> exampleEncodedXML >> ^'<?xml version="1.0" encoding="UTF-8"?> >> <test-data>…</test-data> >> ' >> >> testDecodingCharacters >> | xmlDocument element | >> "XMLTokenizer testDecodingCharacters" >> >> xmlDocument := XMLDOMParser parseDocumentFrom: self exampleEncodedXML readStream. >> element := xmlDocument firstTagNamed: #'test-data'. >> >> self assert: element contentString first codePoint = 8230 >> -=-=-=-=-=-=-=-=-=-=-=-= >> >> #testDecodingCharacters goes yellow >> >>> Thinking of it, it's not really an encoding problem, rather a bug in >>> the entity->character conversion. I guess there should be a similar >>> test where there is an actual ellipsis character in the xml, instead >>> of the entity. >> >> Any idea how your test can goes green? >> >>> And now I realize our server will not be able to connect outside its >>> DMZ, so I won't be able to use the fix :D >> >> DMZ ? >> >> Cheers, >> Alexandre >> > > Character references like the one above are handled using #nextCharReference. It does so by reading the number after the "&#" or "&x" prefix and then sending #value: to the class Unicode with that as the argument. If you evaluate the following code in a workspace with cmd-p: "(Unicode value: 8230) codePoint", you will see that the resulting code point is not what you would expect. For me it was "1069555750". The same behavior results when creating a Unicode character with #charFromUnicode:. Unless Unicode>>value: and Unicode>>charFromUnicode: are being used incorrectly, I am not sure that this is a bug, or least a bug in XML-Support. > > (I am working on adding full DTD support with validation and refactoring and re-engineering the parser at the moment, which is why minor releases have slowed to a trickle. I will take a closer look at how character encoding is handled in the process.) > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 19, 2010

Re: [Pharo-project] UUID on ubuntu 10.04

by StÃ©phane Ducasse

Apparently the student reinstalled her ubuntu from scratch (no incremental installation) and the vm did not crash anymore. Stef On May 17, 2010, at 9:16 PM, StÃ©phane Ducasse wrote: > I asked the student to try. > > Stef > > On May 17, 2010, at 9:06 PM, laurent laffont wrote: > >> On ArchLinux I have the problem when UUID is built external. Official 4.0.3.2202 Unix VM binaries on http://squeakvm.org/unix/ works well for me (UUID is internal). >> >> Can you try with this one click image I made once (uses 4.0.3.2202 binaries) http://lolgzs.free.fr/pharo/Pharo-1.0-OneClick.zip >> >> Laurent Laffont >> >> http://pharocasts.blogspot.com/ >> http://magaloma.blogspot.com/ >> >> >> On Mon, May 17, 2010 at 8:24 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> I can confirm that this is exactly the same trace than the one reported by laurent (no debug file). >> >> Stef >> On May 17, 2010, at 7:51 PM, David T. Lewis wrote: >> >>> On Mon, May 17, 2010 at 07:38:59PM +0200, St?phane Ducasse wrote: >>>> Hi guys >>>> >>>> I took seaside the latest one click image and when I have to save a MC package >>>> I get a core dump with UUID new:... >>>> I checke the so.UUIDplugin is there and I do not understand. >>>> Can somebody with a Ubuntu give a try to save something using MC and the latest seaside one click. >>> >>> Hi Stef, >>> >>> This issue is being tracked here: http://bugs.squeak.org/view.php?id=7358 >>> >>> It is not clear to me if the issue is resolved in the Ian's latest VM >>> build, so if you or anyone else can confirm the UUID crash happening >>> with this VM, that would be helpful to clarify. >>> >>> Dave >>> >>> >>> _______________________________________________ >>> 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 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 19, 2010

Re: [Pharo-project] TORCH: supporting source-code change integration

by Veronica Isabel Uquillas Gomez

Hi Tudor, - could you be more specific, when does the MC browser crash?, i haven't noticed any problem with it. - Yup, Lukas created the AST-semantics package, and I have to include it - No, I am not overriding code, that is a setting already included in Glamour, but true, the border is a cleaner solution... will take a look thank you, Veronica On 19 May 2010, at 08:50, StÃ©phane Ducasse wrote: > > On May 19, 2010, at 12:47 AM, Tudor Girba wrote: > >> Hi Veronica, >> >> A bit of feedback: >> - After loading Torch, the package contextual menu seems to crash the Monticello Browser >> - You extend isSuper in RBProgramNode and RBVariableNode, which generates an override conflict with methods in Moose-Core. > > may be moose should have a look at the new AST-semantics package that lukas created because veronica used that ones > originally and after a discussing with lukas he created ast-semantics > >> - The Glamour tags look different, so I guess you also have some Glamour overrides. That should not happen :). Maybe you have some suggestions for improvement, or maybe you just need the border for the [i] icon? >> >> Cheers, >> Doru >> >> >> On 18 May 2010, at 15:16, Veronica Isabel Uquillas Gomez wrote: >> >>> Hi Tudor, >>> >>> thank you :D >>> >>> sure!!! >>> >>> cheers, >>> Veronica >>> >>> >>> On 18 May 2010, at 11:39, Tudor Girba wrote: >>> >>>> Hi Veronica, >>>> >>>> It is pretty impressive :). >>>> >>>> Would it be Ok if I added this on the Moose page? >>>> >>>> Cheers, >>>> Doru >>>> >>>> >>>> On 18 May 2010, at 11:21, StÃ©phane Ducasse wrote: >>>> >>>>> Thanks veronica. >>>>> lukas said that he was impressed this is a complement :) >>>>> >>>>> On May 18, 2010, at 11:00 AM, Veronica Isabel Uquillas Gomez wrote: >>>>> >>>>>> Dear all, >>>>>> >>>>>> I would like to announce Torch, a tool for supporting source-code change integration. For now, it offers visualizations of the changes and enhanced change lists. >>>>>> Torch can be accessed through Monticello (in the main MC browser, in the repository browser or in the history browser). Selecting a version or slice, you can view the changes with Torch using the contextual menu. >>>>>> Once you open the Torch dashboard, you can access the enhanced change list or a detailed visualization via the contextual menu as well. >>>>>> >>>>>> Torch is available on SqueakSource, the repository is named Torch, and you need to load the ConfigurationOfTorch package. >>>>>> It runs in a dev or core image. >>>>>> >>>>>> For a dev image. >>>>>> - ConfigurationOfTorch loadVersion10 >>>>>> >>>>>> For a core image. >>>>>> 1) Set fonts - described in the attached file. >>>>>> 2) ConfigurationOfTorch loadDefault >>>>>> >>>>>> I would appreciate comments and feedback! >>>>>> >>>>>> Best Regards, >>>>>> VerÃ³nica Uquillas GÃ³mez >>>>>> Vrije University Brussel - SOFT Lab >>>>>> University of Lille - RMOD Team >>>>>> >>>>>> <torchFontsScript.st> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>> >>>> -- >>>> www.tudorgirba.com >>>> >>>> "Problem solving efficiency grows with the abstractness level of problem understanding." >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> 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 >> >> -- >> www.tudorgirba.com >> >> "Problem solving efficiency grows with the abstractness level of problem understanding." >> >> >> >> >> _______________________________________________ >> 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

May 19, 2010

Re: [Pharo-project] TORCH: supporting source-code change integration

by Veronica Isabel Uquillas Gomez

Hola Mariano, Yup, I considered that but as there are already many buttons, I never tried.. Will try it anyway... gracias, Veronica On 18 May 2010, at 12:12, Mariano Martinez Peck wrote: > Hola VerÃ³nica! > > I love it!!! nice, very nice :) > > I will give you more feedback as far as I start to use it. > The only thing I would add is a button in the MC. Look the attached screenshot. It would be cool not only to have it in the context menu, but in the MC broser...for example, next to "changes" button a "torch" button or something like that. > > I really like it. Moose and all it tools seems to be working in Pharo 1.1 so....maybe if people agree we can include this cool tool together with Mondrian and Glamour ? They have 460 green tests :) > > DEV!!!!!!!! > > :) > > On Tue, May 18, 2010 at 11:39 AM, Tudor Girba <tudor.girba(a)gmail.com> wrote: > Hi Veronica, > > It is pretty impressive :). > > Would it be Ok if I added this on the Moose page? > > Cheers, > Doru > > > > On 18 May 2010, at 11:21, StÃ©phane Ducasse wrote: > > Thanks veronica. > lukas said that he was impressed this is a complement :) > > On May 18, 2010, at 11:00 AM, Veronica Isabel Uquillas Gomez wrote: > > Dear all, > > I would like to announce Torch, a tool for supporting source-code change integration. For now, it offers visualizations of the changes and enhanced change lists. > Torch can be accessed through Monticello (in the main MC browser, in the repository browser or in the history browser). Selecting a version or slice, you can view the changes with Torch using the contextual menu. > Once you open the Torch dashboard, you can access the enhanced change list or a detailed visualization via the contextual menu as well. > > Torch is available on SqueakSource, the repository is named Torch, and you need to load the ConfigurationOfTorch package. > It runs in a dev or core image. > > For a dev image. > - ConfigurationOfTorch loadVersion10 > > For a core image. > 1) Set fonts - described in the attached file. > 2) ConfigurationOfTorch loadDefault > > I would appreciate comments and feedback! > > Best Regards, > VerÃ³nica Uquillas GÃ³mez > Vrije University Brussel - SOFT Lab > University of Lille - RMOD Team > > <torchFontsScript.st> > > > > _______________________________________________ > 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 > > -- > www.tudorgirba.com > > "Problem solving efficiency grows with the abstractness level of problem understanding." > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > <Picture 5.png>_______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 19, 2010

Re: [Pharo-project] TORCH: supporting source-code change integration

by Veronica Isabel Uquillas Gomez

Hi Henry Indeed you are right, and that prerequisite is the only one which is overriding code... I was doing some tests, and I think I can remove it for a core image configuration, will discuss with Tudor regards, Veronica On 18 May 2010, at 14:58, Henrik Johansen wrote: > In particular, this prereq in ConfigurationOfGlamour caused it: > baseline20beta4: spec > spec for: #common do: [ > *snip* > spec package: 'Morphic-MorphTreeWidget' with: [ > spec repository: 'http://squeaksource.com/Momo10']; > *snip* > ] > > As I said, since MorphTreeWidget is already part of 1.1Core, this caused an older version of the widget to load. > > Since Settings Browser uses methods found in the newer version in Core, loading Glamour caused it to DNU when I tried opening a Settings Browser. > > Cheers, > Henry > > > On May 18, 2010, at 2:41 15PM, Henrik Johansen wrote: > >> Yes, that is where it broke.... >> >> >> On May 18, 2010, at 2:32 30PM, StÃ©phane Ducasse wrote: >> >>> henrik >>> >>> did you try on 1.1? >>> >>> Stef >>> >>> On May 18, 2010, at 1:00 PM, Henrik Johansen wrote: >>> >>>> >>>> >>>> Den 18.05.2010 12:12, skrev Mariano Martinez Peck: >>>>> Hola VerÃ³nica! >>>>> >>>>> I love it!!! nice, very nice :) >>>>> >>>>> I will give you more feedback as far as I start to use it. >>>>> The only thing I would add is a button in the MC. Look the attached >>>>> screenshot. It would be cool not only to have it in the context menu, >>>>> but in the MC broser...for example, next to "changes" button a "torch" >>>>> button or something like that. >>>>> >>>>> I really like it. Moose and all it tools seems to be working in Pharo >>>>> 1.1 so....maybe if people agree we can include this cool tool together >>>>> with Mondrian and Glamour ? They have 460 green tests :) >>>> Strange, for me it lead to errors in 1.1 because: >>>> - It depends on Momo10 (MorphTreeMorph) >>>> - This has been integrated into Morphic in 1.1 >>>> - Loading Torch overrode the code in Morphic with code from Momo rep. >>>> - The "old" tree was missing methods (rowInset:) used by the settings >>>> browser, so that broke. >>>> >>>> Soooo, Metacello tags with version info as well coming soon? >>>> I really haven't followed that discussion :) >>>> >>>> Cheers, >>>> Henry >>>> >>>> _______________________________________________ >>>> 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 >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 19, 2010

Re: [Pharo-project] Managing Pharo external packages with Metacello, please read!

by StÃ©phane Ducasse

sound cool. Estenban we need more :) On May 19, 2010, at 2:45 AM, Dale Henrichs wrote: > Yes, I don't think that it is a good idea to modify the configuration when it is published in the PharoXXMetacelloRepository. > > In the end the reason for this discussion revolves around the desire to provide a simple method for developers/users to load projects that are "known/tested to work in PharoXX". > > Creating a PharoXXMetacelloRepository means that we have a "white list" of configurations that are"known/tested to work in PharoXX". > > GoferProjectLoader provides an API for loading projects from a target repository. The API makes it very simple to load a particular project by name, without having to specify more details about the version of groups involved. It also means that one can arrange to do special things under the cover of the GoferProjectLoader, like point to a different repository based upon the version of Pharo that it is running in ... > > I think that what we need in addition to a "white list" of projects, a "white list" of _versions_ that are "known/tested to work in PharoXX." > > I think it would be straightforward to subclass/extend the GoferProjectLoader to add the notion of a version/group "white list" that records the exact configuration/version/group(s) that have been tested and known to work. This same extension to GoferProjectLoader can automatically include an overrideRepositories: to ensure that all projects/packages are loaded from the PharoXXMetacelloRepository repository... > > By default, the GoferProjectLoader loaded into PharoXX would point to PharoXXMetacelloRepository and use the "white list" of versions. > > Once a developer/user has become comfortable using PharoXX, he/she can configure GoferProjectLoader to suit his/her needs as well as directly load Configurations/versions that are not on the "white list" (using Metacello directly) without requiring any changes to the configurations or where they originated from... > > So in the end the following expression will do things differently depending upon a) which version of Pharo it is executed in and b) whether or not you are using the 'default' GoferProjectLoader: > > Gofer project load: 'SqueakDBX'. > > All while using the same Configuration... > > Dale > > StÃ©phane Ducasse wrote: >> Yes I think that this is what dale proposed. >> Dale is off line today but he will probably comment >> Stef >> >> On May 18, 2010, at 10:59 AM, Tudor Girba wrote: >> >> >> >>> Hi, >>> >>> I like this approach: >>> 1. Projects can continue to be built independently. For example, in Moose, we have already a process with multiple configurations (one for each repository) depending on each other. >>> 2. When ready, the Configurations and all related packages are "published" in the PharoXXMetacelloRepository. Having a package per Configuration makes it easy to copy it. >>> >>> The only problem is that the code of Configuration mentions explicitly the repository (especially in the case of having nested Configurations, I point to a configuration by specifying the repository, package, and class). So, I guess the simplest thing here would be to provide the default "load" method to already override dynamically all repositories with the PharoXXMetacelloRepository. >>> >>> Cheers, >>> Doru >>> >>> >>> On 18 May 2010, at 09:32, StÃ©phane Ducasse wrote: >>> >>> >>> >>>> I understand nicolas. Now my agenda is more than full. >>>> and the proposal is here. Simple >>>> >>>> ========================================================== >>>> One repo per version Pharo1.0, Pharo11 ... MetacelloRepository >>>> containing **published** configurationOfXXX >>>> -> all the dependent packages are copied locally + configuration ready to load using load. >>>> >>>> A project >>>> contain its single/or several configurationOfMyProject with the complete history >>>> people commit the config to their repository and if they want they **publish** from their repository to the version repository >>>> a version. This version is frozen -> all the dependent packages are copied locally + configuration ready to load using load. >>>> >>>> For Pharo core or pharo packages that we maintain we want to maintain it as a project. >>>> with its own repository and packages. >>>> >>>> We can use automatic build server to validate the status or migration between different repositories >>>> ========================================================== >>>> >>>> >>>> Stef >>>> >>>> On May 17, 2010, at 11:00 PM, Nicolas Cellier wrote: >>>> >>>> >>>> >>>>> The meaning of my message was don't do it for squeak, but do it for yourself. >>>>> I don't doubt the mailing list is a mine of information, but even in >>>>> the best mine you need to dig a lot before extracting the gold >>>>> nuggets. >>>>> Of course, I've got no right to control your agenda, who am I ? >>>>> You can consider the subject close, and I won't find your attitude >>>>> shocking at all. >>>>> But next time, consider writing a rationale for your own, it will >>>>> increase quality of Pharo decision process. >>>>> >>>>> Best regards >>>>> >>>>> Nicolas >>>>> >>>>> 2010/5/17 StÃ©phane Ducasse >>>>> <stephane.ducasse(a)inria.fr> >>>>> : >>>>> >>>>> >>>>>> nicolas >>>>>> >>>>>> all the information is in the metacello mailing-list and we already posted many mails on that topics in this mailing list. >>>>>> I'm sorry but I do not have the time to repeat again what we said. Now since I'm in a really good mood >>>>>> in a nutshell >>>>>> >>>>>> one repo per version Pharo1.0, Pharo11 ... MetacelloRepository >>>>>> containing configurationOfXXX frozen = all the dependent packages are copied locally + configuration ready to load using load. >>>>>> >>>>>> a project >>>>>> contain its single/or whatever configurationOfMyProject >>>>>> people publish the config to their repository and if they want they push from their repository to the version repository >>>>>> a version that they freeze (may be using tags) >>>>>> >>>>>> For Pharo core or pharo packages that we maintain we want to maintain it as a project. >>>>>> with its own repository and packages. >>>>>> >>>>>> Then we have a server that load configuration and barks if something wrong happen. And may be we kick out >>>>>> the configurationofXXX from MetacelloRepositories >>>>>> >>>>>> >>>>>> >>>>>>> Steph, >>>>>>> I understand how boring it may seem: >>>>>>> - you already discussed the subject over and over >>>>>>> - you already took decisions >>>>>>> and now we come later with new proposals, and ask you to reconsider >>>>>>> the work again... >>>>>>> >>>>>>> >>>>>> more than that. :) >>>>>> It looks like if we did not talk or think about what we are doing. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>> As for the Preferences/Settings, Pharo choices are probably very weel thought. >>>>>>> >>>>>>> However, every solution will come with trade offs, and it would be >>>>>>> good to have a rationale justifying the choices you made, and perhaps >>>>>>> more importantly justifying why you did abandon some solutions, >>>>>>> because some questions might be repeated in Pharo 1.2, 1.3, 2.0 ... >>>>>>> and find different answers in different context. Note that Squeak >>>>>>> evolutions might have influence on Pharo too, and it's part of the >>>>>>> context... >>>>>>> >>>>>>> I strongly encourage you to establish your rationale on Pharo grounds >>>>>>> - independently of Andreas proposals, put it on the Pharo wiki and let >>>>>>> us know the URL. >>>>>>> >>>>>>> You also know that Squeak goals are not exactly those of Pharo w.r.t. >>>>>>> backward compatibility, so Squeak can't just blindly replicate Pharo >>>>>>> solutions without a rationale. >>>>>>> >>>>>>> The merit of Andreas proposal is to try and establish such a >>>>>>> rationale. Without it, we're bound to repeat discussions again and >>>>>>> again, >>>>>>> >>>>>>> >>>>>> So to fix the problem consider that as our proposal. >>>>>> >>>>>> Stef >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>> >>>> >>>> >>> -- >>> >>> www.tudorgirba.com >>> >>> >>> "Every thing has its own flow." >>> >>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> >>> >> >> >> >

May 19, 2010