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

Re: [Pharo-project] InterfaceDiscoverer

by Alexandre Bergel

> Did you try the GraphViz from the same repository? Yes. > It seems to depend on FFI, but that functionality is not needed > anyway. You can safely ignore that warning. The dependency package of > mine will simply create an object model of the dependencies and > optionally a GraphViz file that you have to convert to a png/svg/pdf > from the command line yourself. The only way I see to load GraphViz, is to download the .mcz file, uncompress it, remove the improperly written method from the .st file, and then to load it from Squeak. Is there something better to load it? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 11, 2008

Re: [Pharo-project] InterfaceDiscoverer

by Lukas Renggli

> Sorry to answer so late. I tried to load GraphViz, but a syntax error pops > up. Did you try the GraphViz from the same repository? > MacOSGraphVizGenerator>>runWithSystemFramework: string > <> expected ->apicall: short 'system' (char*) module: > 'System.framework'> > > ^ self externalCallFailed > > I used the last Pharo image with loadOB installed. It seems to depend on FFI, but that functionality is not needed anyway. You can safely ignore that warning. The dependency package of mine will simply create an object model of the dependencies and optionally a GraphViz file that you have to convert to a png/svg/pdf from the command line yourself. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Sept. 11, 2008

Re: [Pharo-project] InterfaceDiscoverer

by Alexandre Bergel

Hi Lukas, Sorry to answer so late. I tried to load GraphViz, but a syntax error pops up. MacOSGraphVizGenerator>>runWithSystemFramework: string <> expected ->apicall: short 'system' (char*) module: 'System.framework'> ^ self externalCallFailed I used the last Pharo image with loadOB installed. Cheers, Alexandre On 6 Sep 2008, at 09:45, Lukas Renggli wrote: >> I built a small extension to OB that display dependencies between >> class >> categories. Just load InterfaceDiscoverer from squeaksource, and >> click on a >> class category in an OB browser. > > What kind of dependencies? > > For Seaside we use Package-Dependencies from > http://source.lukas-renggli.ch/unsorted/ to calculate static > dependencies between packages and visualize them using GraphViz. The > code takes some ideas from MudPie and Moose, but otherwise is a new > completely implementation. > > 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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 11, 2008

Re: [Pharo-project] Your take on that: CollectionsTests-Ordered vs Collections-Ordered-Tests

by Luc Fabresse

I understand the problem and I did not explain well but the solution of the Graphics package seems great : Graphics-Text Graphics-Files and GraphicsTests-Text GraphicsTests-Files Other packages like Graphics : CollectionTests-*, KernelTests-*, ... Packages with other naming conventions that do not seem great : File-Tests, Tests-*, Monticello-Tests Sure, a system that does not rely on string maching would be better. #Luc 2008/9/11 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > On Sep 11, 2008, at 9:35 AM, Luc Fabresse wrote: > > the convention <category>Tests[<-subcategory>] seems great IMO. >> e.g. Graphics-Text -> GraphicsTests-Text >> >> With this naming pattern it is possible to have 2 monticello packages : >> <category> and <category>Tests >> And it is possible to not load Tests packages in a deployed image. >> > > Yes it does not work if Graphics is composed of several subpackages > > With this I cannot have > > Collections-OrderedCollection > and > Collections-OrderedCollection-Tests > > separated from > > Collections-Set > and > Collections-Set-Tests > > For me I want to have packages that I can load independently and the tests > should be attached to the package (to be eventually not load with it). > >> >> > I really hate the fact that we feel everywhere category and string > matching. > > Stef > > > >> Luc >> >> 2008/9/11 Alexandre Bergel <alexandre(a)bergel.eu> >> Having a package name without any - will prevent Monticello from being >> confuse on some point. >> Stef and I already experienced that... >> >> I was never happy in inserting a - in a package name. >> >> Alexandre >> >> >> >> On 11 Sep 2008, at 07:23, Damien Cassou wrote: >> >> On Wed, Sep 10, 2008 at 9:32 PM, StÃ©phane Ducasse >> <stephane.ducasse(a)inria.fr> wrote: >> Hi >> >> I noticed that we have CollectionsTests-Ordered >> kind of package name and I would prefer to get Collections-Ordered-Tests >> What do you think. I bit of regularity would help. >> >> Collections-Test-* categories belong to the Collections-Test package >> on monticello. If you rename it to Collections-Ordered-Tests, you will >> put everything in the Collections package (because there is no >> Collections-Ordered monticello package). >> >> >> -- >> Damien Cassou >> Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good >> luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) >> _______________________________________________ >> 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 >> >> _______________________________________________ >> 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 >

Sept. 11, 2008

Re: [Pharo-project] Hello everyone!

by StÃ©phane Ducasse

I'm confused you do not use VMMaker for Hydra? > >> yes keep it there >> we have too much mailing-lists >> >> So can you do a unix/windows VM with the freeType pluging? >> > Sure i can, just give me details which/where i should take VMMaker & > platform sources & plugin. I thought that all this information was in the VM repository. Stef

Sept. 11, 2008

Re: [Pharo-project] Your take on that: CollectionsTests-Ordered vs Collections-Ordered-Tests

by StÃ©phane Ducasse

On Sep 11, 2008, at 9:35 AM, Luc Fabresse wrote: > the convention <category>Tests[<-subcategory>] seems great IMO. > e.g. Graphics-Text -> GraphicsTests-Text > > With this naming pattern it is possible to have 2 monticello > packages : <category> and <category>Tests > And it is possible to not load Tests packages in a deployed image. Yes it does not work if Graphics is composed of several subpackages With this I cannot have Collections-OrderedCollection and Collections-OrderedCollection-Tests separated from Collections-Set and Collections-Set-Tests For me I want to have packages that I can load independently and the tests should be attached to the package (to be eventually not load with it). > I really hate the fact that we feel everywhere category and string matching. Stef > > Luc > > 2008/9/11 Alexandre Bergel <alexandre(a)bergel.eu> > Having a package name without any - will prevent Monticello from > being confuse on some point. > Stef and I already experienced that... > > I was never happy in inserting a - in a package name. > > Alexandre > > > > On 11 Sep 2008, at 07:23, Damien Cassou wrote: > > On Wed, Sep 10, 2008 at 9:32 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: > Hi > > I noticed that we have CollectionsTests-Ordered > kind of package name and I would prefer to get Collections-Ordered- > Tests > What do you think. I bit of regularity would help. > > Collections-Test-* categories belong to the Collections-Test package > on monticello. If you rename it to Collections-Ordered-Tests, you will > put everything in the Collections package (because there is no > Collections-Ordered monticello package). > > > -- > Damien Cassou > Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good > luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) > _______________________________________________ > 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 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 11, 2008

[Pharo-project] About fixes for noury and other

by StÃ©phane Ducasse

Hi noury I started to harvest your fixes and I learned something :) when most of your fixes are about extending or changing a package just publish a new version of that package. This way I can use the merge tool and be much more efficient, do not create a specific package with specific class extension for it else I have to modify everything by hand. Stef

Sept. 11, 2008

Re: [Pharo-project] Your take on that: CollectionsTests-Ordered vs Collections-Ordered-Tests

by Luc Fabresse

the convention <category>Tests[<-subcategory>] seems great IMO.e.g. Graphics-Text -> GraphicsTests-Text With this naming pattern it is possible to have 2 monticello packages : <category> and <category>Tests And it is possible to not load Tests packages in a deployed image. Luc 2008/9/11 Alexandre Bergel <alexandre(a)bergel.eu> > Having a package name without any - will prevent Monticello from being > confuse on some point. > Stef and I already experienced that... > > I was never happy in inserting a - in a package name. > > Alexandre > > > > On 11 Sep 2008, at 07:23, Damien Cassou wrote: > > On Wed, Sep 10, 2008 at 9:32 PM, StÃ©phane Ducasse >> <stephane.ducasse(a)inria.fr> wrote: >> >>> Hi >>> >>> I noticed that we have CollectionsTests-Ordered >>> kind of package name and I would prefer to get Collections-Ordered-Tests >>> What do you think. I bit of regularity would help. >>> >> >> Collections-Test-* categories belong to the Collections-Test package >> on monticello. If you rename it to Collections-Ordered-Tests, you will >> put everything in the Collections package (because there is no >> Collections-Ordered monticello package). >> >> >> -- >> Damien Cassou >> Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good >> luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) >> _______________________________________________ >> 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 >

Sept. 11, 2008

Re: [Pharo-project] Your take on that: CollectionsTests-Ordered vs Collections-Ordered-Tests

by Alexandre Bergel

Having a package name without any - will prevent Monticello from being confuse on some point. Stef and I already experienced that... I was never happy in inserting a - in a package name. Alexandre On 11 Sep 2008, at 07:23, Damien Cassou wrote: > On Wed, Sep 10, 2008 at 9:32 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> Hi >> >> I noticed that we have CollectionsTests-Ordered >> kind of package name and I would prefer to get Collections-Ordered- >> Tests >> What do you think. I bit of regularity would help. > > Collections-Test-* categories belong to the Collections-Test package > on monticello. If you rename it to Collections-Ordered-Tests, you will > put everything in the Collections package (because there is no > Collections-Ordered monticello package). > > > -- > Damien Cassou > Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good > luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) > _______________________________________________ > 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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 11, 2008

Re: [Pharo-project] Hello everyone!

by Igor Stasenko

2008/9/11 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > yes keep it there > we have too much mailing-lists > > So can you do a unix/windows VM with the freeType pluging? > Sure i can, just give me details which/where i should take VMMaker & platform sources & plugin. > Stef > > On Sep 11, 2008, at 12:03 AM, Igor Stasenko wrote: > >> 2008/9/10 Alexandre Bergel <alexandre(a)bergel.eu>: >>> >>> Igor, >>> >>> Do you have a mailing list on Hydra? >>> I think it is important to initiate the creation of a community around >>> this >>> idea. >>> You may use googlecode for that. >>> >> >> there is not much activity in this area, worth creating new mailing list. >> Currently, i using squeak-dev or vm-dev mailing list for news & >> announcements. >> I asked community, maybe it is OT, but nobody complained about it, >> instead they want it there. :) >> >>> Cheers, >>> Alexandre >>> >>> >>> On 10 Sep 2008, at 10:44, Igor Stasenko wrote: >>> >>>> 2008/9/10 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>>>>>> >>>>>> >>>>>> Well, as i said, putting FreeType into VM is simple thing. >>>>>> But maintaining a code base or regular basis is completely different >>>>>> thing. I'm not sure i have enough spare time to do this now. >>>>>> First, because i'm busy with Hydra VM. >>>>>> Second , I think you are aware, that Cog & Hydra will merge in future. >>>>>> Before this happens, i have little interest in supporting >>>>>> old-fashioned VMs :) >>>>>> >>>>>> I planning to do a major refactoring in Hydra, after which , an >>>>>> Interpreter/ObjectMemory can be simulated in image. But this will have >>>>>> a major impact on backward compatibility. >>>>>> >>>>>> But for minor changes, like in some plugins, it not hurts a lot. I >>>>>> think that, if you planning to maintain own VM, then i'll advice to >>>>>> split VMMaker package on two separate parts: >>>>>> - VM core >>>>>> - all plugins >>>>>> >>>>>> Because VM is a big code bloat , which is hard to manipulate with. >>>>>> >>>>>> Also, it would be good to have a common code repository, and separate >>>>>> tracker of bugs and fixes for VM/plugins, so it will make an >>>>>> integration easier for all interesting parties. >>>>> >>>>> could you push this idea to the VM maintainers or start to do it? >>>> >>>> yes i could, but do you think that i have a chance to be heard and my >>>> point to be accepted? :) >>>> >>>>> We are talking abut that since years. >>>>> I still do not understand I thought that the svn of the vm code was >>>>> such >>>>> common >>>>> code repository? >>>> >>>> I tried to raise this topic on board meeting, concerning status of >>>> VM-dev group and the answer was like: >>>> - we already have things set up, and each maintainer know/doing things >>>> well. >>>> I'm not sure about current status, but i keep feeling that VM >>>> maintainers efforts dissipating due to lack of >>>> communication/collaboration. >>>> Maybe it is because i'm relatively new, and missing info about how >>>> things was set up long ago, before i came in, maybe people really >>>> collaborate behind the scenes, i don't know. >>>> What i really sure about, is that , it will not hurt to call for a >>>> status (re)clarification to know who doing what and how things >>>> working. >>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project(a)lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>> >>>> >>>> >>>> -- >>>> Best regards, >>>> Igor Stasenko AKA sig. >>>> _______________________________________________ >>>> 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 >>> >> >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> _______________________________________________ >> 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 > -- Best regards, Igor Stasenko AKA sig.

Sept. 11, 2008