- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Package comments

by laurent laffont

Why not HelpSystem ? Works quite well to document any package. Laurent Laffont http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/ On Fri, Sep 3, 2010 at 11:25 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > I started to work on DrDoc (look at the package on squeaksource) > to add metadata to packages and the idea is to save there information in > terms of SmallUML spec. > > Now I cannot integrate and taking care of the system, working on my daily > job and producing what I want. > So sorry. > > Stef > > On Sep 3, 2010, at 5:01 AM, Sean P. DeNigris wrote: > > > > > I yearn for package comments, especially when hunting for a starting > point in > > a new package. > > > > What say you? > > > > Sean > > > > p.s. For reference, I started a Squeak issue with links to previous > > discussions here - http://bugs.squeak.org/view.php?id=7558. > > why there? > I cannot remember all these information > > > > -- > > View this message in context: > http://forum.world.st/Package-comments-tp2525056p2525056.html > > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > > > _______________________________________________ > > 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. 3, 2010

Re: [Pharo-project] Package comments

by StÃ©phane Ducasse

I started to work on DrDoc (look at the package on squeaksource) to add metadata to packages and the idea is to save there information in terms of SmallUML spec. Now I cannot integrate and taking care of the system, working on my daily job and producing what I want. So sorry. Stef On Sep 3, 2010, at 5:01 AM, Sean P. DeNigris wrote: > > I yearn for package comments, especially when hunting for a starting point in > a new package. > > What say you? > > Sean > > p.s. For reference, I started a Squeak issue with links to previous > discussions here - http://bugs.squeak.org/view.php?id=7558. why there? I cannot remember all these information > -- > View this message in context: http://forum.world.st/Package-comments-tp2525056p2525056.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 3, 2010

Re: [Pharo-project] PharoKernel #12121

by StÃ©phane Ducasse

for me this is simple - I would like to use a metacello configuration to reload everything in between this kernel image and the current 12121 but I do not have the time. So ... On Sep 2, 2010, at 11:08 PM, Lukas Renggli wrote: > Very impressive. Can't wait to see Pharo built from such a small image. > > Lukas > > On 2 September 2010 23:02, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: >> Hi, >> >> I uploaded the new version of PharoKernel #12121: >> >> https://gforge.inria.fr/frs/download.php/27438/PharoKernel-1.2-12121.zip >> >> The shrinking process is now based on packages. >> >> Cheers >> -- Pavel >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Lukas Renggli > 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

Sept. 3, 2010

Re: [Pharo-project] Native (OS-level) windows

by StÃ©phane Ducasse

Hi evgeniy We would love to see any progress in the direction of having feenestri working for Pharo now we do not have simply the task forces. So if you do any changes in the system to help you in this task send the patches and changes so that life is easier for you and we can get this done in the future. Stef On Sep 3, 2010, at 8:15 AM, Evgeniy Philippov wrote: > Hello folks and Todd Blanchard, > > I have three questions. First question is---what is the current status of Ffenestri, and where can I download some version of Pharo with the most up-to-date Ffenestri support? The second question is---what are the other Pharo OS-level windowing interfaces, and what is their status? And the last question is---what is more complete: Squeak's Ffenestri support, or Pharo's Ffenestri support? > > My intents. I plan to use some version of Squeak or Pharo system for my project (which is a hobby project), and I am mainly interested in OS-level windowing for Linux (Ubuntu) and to a lesser extent for Win32 too. I studied wxSqueak a bit, and concluded that Ffenestri is overall simpler to develop than wxSqueak, and guessed that Ffenestri moves/will move faster when considering the completeness of it, than wxSqueak. > > -- > Evgeniy > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 3, 2010

Re: [Pharo-project] PluggableShoutMorph >> okToStyle still make a reference to Preferences

by Cyrille Delaunay

When I look at http://www.squeaksource.com/shout, It seems that I have the last version of the package 'Shout'. Am I looking at the right place ? 2010/9/3 Lukas Renggli <renggli(a)gmail.com> > Not if you use the latest version. I fixed that a long time ago. > > Lukas > > 2010/9/3 Cyrille Delaunay <cy.delaunay(a)gmail.com>: > > PluggableShoutMorph >> okToStyle still make a reference to Preferences, > > which is no longer present in pharo 1.2. It generate problem when opening > a > > debugger for example (which is a problem :)). > > I opened an issue: > > http://code.google.com/p/pharo/issues/detail?id=2905 > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > -- > Lukas Renggli > 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 >

Sept. 3, 2010

Re: [Pharo-project] [Pharo-users] TestSprinter

by StÃ©phane Ducasse

ask marcus when he is running OPAL tests. And I need that when I integrate because there are ALWAYS broken tests and right now I have to remember the list or open two images. Lukas not everybody has the chances to work on system with not broken tests. Stef >> icons to see which tests failed since last run and a summary >> >> previous run: current: >> 150 green 149 green >> 2 failure 2 failutres >> 1 errors >> >> could be presented differently > > I doubt that this is useful within an image. I run different sub-sets > of my tests far too often to see something meaningful between the > current and previous run. > > Hudson shows the deltas of errors/failures/passes and added/removed > tests between builds in various graphs and tables. sure but do I want to want 20 minutes for a run to be scheduled on a server I do not control? > > Lukas > > -- > Lukas Renggli > 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

Sept. 3, 2010

Re: [Pharo-project] PluggableShoutMorph >> okToStyle still make a reference to Preferences

by Lukas Renggli

Not if you use the latest version. I fixed that a long time ago. Lukas 2010/9/3 Cyrille Delaunay <cy.delaunay(a)gmail.com>: > PluggableShoutMorph >> okToStyle still make a reference to Preferences, > which is no longer present in pharo 1.2. It generate problem when opening a > debugger for example (which is a problem :)). > I opened an issue: > http://code.google.com/p/pharo/issues/detail?id=2905 > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli www.lukas-renggli.ch

Sept. 3, 2010

[Pharo-project] PluggableShoutMorph >> okToStyle still make a reference to Preferences

by Cyrille Delaunay

PluggableShoutMorph >> okToStyle still make a reference to Preferences, which is no longer present in pharo 1.2. It generate problem when opening a debugger for example (which is a problem :)). I opened an issue: http://code.google.com/p/pharo/issues/detail?id=2905

Sept. 3, 2010

Re: [Pharo-project] Experimental Cocoa OS-X based Squeak Cog JIT VM 5.8b7

by Tudor Girba

Hi John, I get no debug.log. The only thing I get is the Apple reporting window saying that it crashed. I attach here the text output of the problem details and system configuration. Cheers, Doru On 3 Sep 2010, at 09:36, John M McIntosh wrote: > Doru, can you send me the crash report? To fix I'll need that. The > VM is compiled with the 10.5.x SDK and > should work on it. > > On 2010-09-02, at 10:25 PM, Tudor Girba wrote: > >> Hi John, >> >> I tried the VM on Mac OS X 10.5.8 and it just crashes on an image >> that works perfectly with 5.8.b4. >> >> I will soon upgrade to Snow Leopard (finally :)), but I can still >> play around today if you want me to test further. >> >> Cheers, >> Doru >> > > -- > = > = > = > = > = > ====================================================================== > John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: > squeaker68882 > Corporate Smalltalk Consulting Ltd. http:// > www.smalltalkconsulting.com > = > = > = > = > = > ====================================================================== > > > > -- www.tudorgirba.com "Obvious things are difficult to teach."

Sept. 3, 2010

Re: [Pharo-project] [Moose-dev] Re: Re: load moose in Pharo1.2

by Cyrille Delaunay

I removed them. Tell me if there is any problem 2010/9/2 Tudor Girba <tudor.girba(a)gmail.com> > I was more considering the issue from a transitory point of view. But, > indeed, given that 1.1 is out, there is no point in being backward > compatible anymore. > > Cheers, > Doru > > > > On 2 Sep 2010, at 16:51, Guillermo Polito wrote: > > But, that's why we have metacello configs? don't we? We have to use a >> specific version for 1.1 and another one for 1.2. >> >> If we want to download the lastVersion always, It's not going to work >> never :). >> >> On Thu, Sep 2, 2010 at 11:46 AM, Tudor Girba <tudor.girba(a)gmail.com> >> wrote: >> No, because if you remove it you break 1.1. I would suggest to just rename >> those variables. >> >> Cheers, >> Doru >> >> >> >> On 2 Sep 2010, at 16:43, Cyrille Delaunay wrote: >> >> There is already an issue for that: >> >> >> http://code.google.com/p/pharo/issues/detail?id=2734&q=PluggableShoutMorph&… >> >> Should we (I) remove those variables from PluggableShoutMorph? >> >> 2010/9/2 Cyrille Delaunay <cy.delaunay(a)gmail.com> >> Now I have exactly the same problem with 'PluggableShoutMorph' in the >> package Shout (This package is loaded with ConfigurationOfPetitParser). >> PluggableShoutMorph (like MOEaselTextEditor) declare the two instance >> variables 'styler' and 'unstyledAcceptText' which are already declared in >> the superclass PluggableTextMorph (in Pharo 1.2). Maybe those variable have >> been integrated in the superclass for pharo 1.2 and are no longer usefull ? >> Anyone know? >> >> 2010/9/2 Alexandre Bergel <alexandre(a)bergel.eu> >> >> Strange indeed. This method is apparently never called. This is related >> somehow to the completion (which does not work for me. I will contact >> Lukas). >> >> Alexandre >> >> >> On 2 Sep 2010, at 08:22, Cyrille Delaunay wrote: >> >> > What is strange, is that there is only one reference to >> unstyledAcceptText, without affecting it a value. >> > >> > 2010/9/2 Cyrille Delaunay <cy.delaunay(a)gmail.com> >> > No, same problem now with 'unstyledAcceptText' >> > >> > >> > 2010/9/2 Tudor Girba <tudor.girba(a)gmail.com> >> > And does the loading work now? >> > >> > Doru >> > >> > >> > On 2 Sep 2010, at 13:08, Cyrille Delaunay wrote: >> > >> > done >> > >> > 2010/9/2 Tudor Girba <tudor.girba(a)gmail.com> >> > Yes, please rename it to shoutStyler. >> > >> > Cheers, >> > Doru >> > >> > >> > >> > On 2 Sep 2010, at 12:25, Cyrille Delaunay wrote: >> > >> > So that means that a 'styler' instance variable has been defined in >> PluggableTextMorph between pharo 1.1 and Pharo 1.2? Should we rename the >> Mondrian instance variable? >> > >> > 2010/9/2 Cyrille Delaunay <cy.delaunay(a)gmail.com> >> > So a solution is to load in a version of OmniBrowser that is compatible >> with 1.2, before loading moose: >> > >> > (ConfigurationOfOmniBrowser project version: '1.1-baseline') load. >> > >> > Now, I have another error: >> > The class MOEaselTextEditor from Mondrian-Easel re-declare the instance >> variable 'styler', which is already defined in its superclass >> PluggableTextMorph. >> > >> > 2010/9/1 Lukas Renggli <renggli(a)gmail.com> >> > >> > Metacello is loading an ancient version of OB. References to >> > Preferences have been removed a long time ago. However there is still >> > a problem with the highlighting in Pharo 1.2. You only get a working >> > environment if you do not load the package OB-Shout. >> > >> > Lukas >> > >> > On 1 September 2010 16:10, Tudor Girba <tudor.girba(a)gmail.com> wrote: >> > > Hi Cyrille, >> > > >> > > That means that OB needs to be fixed :). Could you raise the issue on >> the >> > > pharo mailing list? >> > > >> > > Cheers, >> > > Doru >> > > >> > > >> > > On 1 Sep 2010, at 14:48, Cyrille Delaunay wrote: >> > > >> > >> When I try with the configuration, I get an error when loading the >> class >> > >> OBMercuryPanel (from the package OB-Standard, that seems to be loaded >> with >> > >> ConfigurationOfMetacello): >> > >> The initialize method is using the old class "Preferences" (that is >> no >> > >> longer present in Pharo 1.2). >> > >> >> > >> 2010/9/1 Tudor Girba <tudor.girba(a)gmail.com> >> > >> What do you mean by script? Did you try with the configuration? >> > >> >> > >> Doru >> > >> >> > >> >> > >> >> > >> On Sep 1, 2010, at 11:12, Cyrille Delaunay <cy.delaunay(a)gmail.com> >> wrote: >> > >> >> > >> > Hello, >> > >> > Is moose loadable in Pharo 1.2 ? Is there a special script somwhere >> to >> > >> > that? >> > >> > _______________________________________________ >> > >> > Moose-dev mailing list >> > >> > Moose-dev(a)iam.unibe.ch >> > >> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> > >> >> > >> _______________________________________________ >> > >> Moose-dev mailing list >> > >> Moose-dev(a)iam.unibe.ch >> > >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> > >> >> > >> _______________________________________________ >> > >> Moose-dev mailing list >> > >> Moose-dev(a)iam.unibe.ch >> > >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> > > >> > > -- >> > > www.tudorgirba.com >> > > >> > > "When people care, great things can happen." >> > > >> > > >> > > >> > > _______________________________________________ >> > > Moose-dev mailing list >> > > Moose-dev(a)iam.unibe.ch >> > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> > > >> > >> > >> > >> > -- >> > Lukas Renggli >> > www.lukas-renggli.ch >> > _______________________________________________ >> > Moose-dev mailing list >> > Moose-dev(a)iam.unibe.ch >> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> > >> > >> > _______________________________________________ >> > Moose-dev mailing list >> > Moose-dev(a)iam.unibe.ch >> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> > >> > -- >> > www.tudorgirba.com >> > >> > "When people care, great things can happen." >> > >> > >> > >> > _______________________________________________ >> > Moose-dev mailing list >> > Moose-dev(a)iam.unibe.ch >> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> > >> > _______________________________________________ >> > Moose-dev mailing list >> > Moose-dev(a)iam.unibe.ch >> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> > >> > -- >> > www.tudorgirba.com >> > >> > "Being happy is a matter of choice." >> > >> > >> > >> > >> > _______________________________________________ >> > Moose-dev mailing list >> > Moose-dev(a)iam.unibe.ch >> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> > >> > >> > _______________________________________________ >> > Moose-dev mailing list >> > Moose-dev(a)iam.unibe.ch >> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> -- >> www.tudorgirba.com >> >> "If you interrupt the barber while he is cutting your hair, >> you will end up with a messy haircut." >> >> >> _______________________________________________ >> 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 > > "When people care, great things can happen." > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev >

Sept. 3, 2010