- Pharo-dev - lists.pharo.org

Re: [Pharo-project] "A Mentoring Course on Smalltalk" Code License

by Andres Valloud

I am not sure the code in the book needs a license. After all, eventually you will get the distribution for the source code in question and then you will (should) have an MIT license... does that make sense? On 9/30/10 19:23 , Sean P. DeNigris wrote: > > > Andres Valloud-4 wrote: >> >> Well, since this discussion is public now :) >> > hee hee > > > Andres Valloud-4 wrote: >> >> ... exactly what seems to be >> the problem? The book talks about code that is often in the public >> Store repository. Is the problem that the code in the public Store >> repository doesn't have an MIT license? Or is the problem that the book >> that talks about the code in the public Store repository doesn't say >> "and the code has an MIT license"? >> > > Would a license expert weigh in here? Andres, would it be difficult to add > a note to the book specifying that the code in it is MIT?

Oct. 2, 2010

Re: [Pharo-project] [ANN] Pharo-1.1.1-dev10.09.1

by GermÃ¡n Arduino

Excellent work, thanks Mariano! 2010/10/1 Mariano Martinez Peck <marianopeck(a)gmail.com>: > Hi folks. We are releasing Pharo 1.1.1. This image is exactly same as Pharo > 1.1 but based on PharoCore 1.1.1. The versions of the external packages is > the same as in Pharo 1.1. The difference is that PharoCore1.1.1 has > integrated some fixes and the support for CogVM. This means that > Pharo-1.1.1-dev10.09.1 can be run with both, normal PharoVM and CogVM. For > CogVM we recommend to use the last binaries that can be found in > http://www.mirandabanda.org/files/Cog/VM/. Right now the last one is > http://www.mirandabanda.org/files/Cog/VM/VM.r2313/ > > This CogVM version fixes the problem with "Objects as methods", and thus, > all the #run:with:with are working. This means that tools like TestCoverage > and AutoTest are working correctly with CogVM. > > The link to the image is: > https://gforge.inria.fr/frs/download.php/27543/Pharo-1.1.1-dev10.09.1.zip > > Cheers > > Mariano > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 1, 2010

Re: [Pharo-project] Source in image [WAS] Re: [Pharo-users] Distributing 'minimal' image

by Levente Uzonyi

On Fri, 1 Oct 2010, Mariano Martinez Peck wrote: > On Fri, Oct 1, 2010 at 8:26 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> On 1 October 2010 08:48, Mariano Martinez Peck <marianopeck(a)gmail.com> >> wrote: >>> >>> >>> On Thu, Sep 30, 2010 at 11:07 PM, Johan Fabry <jfabry(a)dcc.uchile.cl> >> wrote: >>>> >>>> Hi all, >>>> >>>> I am planning to put online a minimal image that contains AspectMaps, >> with >>>> some models pre-loaded. Two questions: >>>> - Is there an easy way to strip this image of dev tools et cetera? >>> >>> Not really. The easiest way is to have a Configuration of Metacello that >>> takes care of loading all your code with all your dependencies. Then, >> take a >>> PharoCore and load your code there. >>> In addition, you may want to evaluate "ScriptLoader cleanUpForProduction" >> at >>> the end. Check the method to see what it does. >>> >>>> >>>> - How can I make it so that I can distribute it without the changes >> file? >>>> (Right now the image complains of a missing changes file if it is not >> there >>>> ...) >>>> >>> >>> I am aware of "Smalltalk abandonSources" to avoid using .sources. You >> won't >>> see things like the temp names, and stuff will be decompiled instead. >> >> With a little effort, you can embed source code into method trailers. >> Then you won't need .sources nor .chanes to see the real source >> instead of decompiling it. >> But you will loose method stamps. >> > > I WOULD LOVE that. I mean, I don't care if the dev image is 10 mb bigger, if > I will improve performance since I don't need to fetch a .sources file. > what would be awesome is if we can have both, this is: for the dev image, I > would like to have the sources in the image, but not for PharoCore. Or maybe > also in PharoCore but to be sure to be able to remove them, and use > .sources/decompiler as it is now. Maybe put that in #cleanUpForProduction or > similar. > > thoughts? You'd also lose versioning, since a trailer can only hold one version of the source code. Btw, do you really have a performance issue reading the sources? With Cog and Squeak 4.2, I get: methods := CompiledMethod allInstances shuffle. [ methods do: #getSource ] timeToRun "===> 1162" So it takes ~25 microseconds to fetch the source of a method on average. That's more than 39000 methods per second. It should be enough IMHO. Levente > > > > >> >>> For the .changes you can start the image without them, there will raise a >>> popup at the beginning. The problem is if you then do sometthing that >> should >>> be written there. Not sure here... >>> >> yeah. >> >>> cheers >>> >>> Mariano >>> >>> >>> >>>> >>>> Thanks in advance! >>>> -- >>>> Johan Fabry >>>> jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry<http://dcc.uchile.cl/%7Ejfabry> >>>> PLEIAD Lab - Computer Science Department (DCC) - University of Chile >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Pharo-users mailing list >>>> Pharo-users(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users >>> >>> >>> _______________________________________________ >>> Pharo-users mailing list >>> Pharo-users(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users >>> >>> >> >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> >> _______________________________________________ >> Pharo-users mailing list >> Pharo-users(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users >> >

Oct. 1, 2010

Re: [Pharo-project] Introducing smallUML: a little project to help us document :)

by Sean P. DeNigris

Carla F. Griggio wrote: > > Let me know what are your projects about and how you would use this :O > I've been working on a mind-mapping-like app and some visual browsing tools (e.g. an implementorsOF browser that draws a graph of possible execution paths), and have been implementing connectors-like functionality from scratch, but I'd be happy to give the "from scratch" part up ;-) Sean -- View this message in context: http://forum.world.st/Introducing-smallUML-a-little-project-to-help-us-docu… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Oct. 1, 2010

Re: [Pharo-project] Chilean mailing list

by Alexandre Bergel

> We've just create a mailing list for discussing about Pharo/Smalltalk in Chile. > pharo-chile(a)googlegroups.com > http://groups.google.com/group/pharo-chile > > Does it make sense ? I ask because maybe with clubSmalltalk (in Spanish) is enough..... Yes it makes sense because most of the members list are from the University of Chile. This means that people know each other. The effect will be different with ClubSmalltalk. Moreover, during my lectures and presentations I talk much more about "Pharo" than "Smalltalk". Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Oct. 1, 2010

[Pharo-project] Source in image [WAS] Re: [Pharo-users] Distributing 'minimal' image

by Mariano Martinez Peck

On Fri, Oct 1, 2010 at 8:26 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 1 October 2010 08:48, Mariano Martinez Peck <marianopeck(a)gmail.com> > wrote: > > > > > > On Thu, Sep 30, 2010 at 11:07 PM, Johan Fabry <jfabry(a)dcc.uchile.cl> > wrote: > >> > >> Hi all, > >> > >> I am planning to put online a minimal image that contains AspectMaps, > with > >> some models pre-loaded. Two questions: > >> - Is there an easy way to strip this image of dev tools et cetera? > > > > Not really. The easiest way is to have a Configuration of Metacello that > > takes care of loading all your code with all your dependencies. Then, > take a > > PharoCore and load your code there. > > In addition, you may want to evaluate "ScriptLoader cleanUpForProduction" > at > > the end. Check the method to see what it does. > > > >> > >> - How can I make it so that I can distribute it without the changes > file? > >> (Right now the image complains of a missing changes file if it is not > there > >> ...) > >> > > > > I am aware of "Smalltalk abandonSources" to avoid using .sources. You > won't > > see things like the temp names, and stuff will be decompiled instead. > > With a little effort, you can embed source code into method trailers. > Then you won't need .sources nor .chanes to see the real source > instead of decompiling it. > But you will loose method stamps. > I WOULD LOVE that. I mean, I don't care if the dev image is 10 mb bigger, if I will improve performance since I don't need to fetch a .sources file. what would be awesome is if we can have both, this is: for the dev image, I would like to have the sources in the image, but not for PharoCore. Or maybe also in PharoCore but to be sure to be able to remove them, and use .sources/decompiler as it is now. Maybe put that in #cleanUpForProduction or similar. thoughts? > > > For the .changes you can start the image without them, there will raise a > > popup at the beginning. The problem is if you then do sometthing that > should > > be written there. Not sure here... > > > yeah. > > > cheers > > > > Mariano > > > > > > > >> > >> Thanks in advance! > >> -- > >> Johan Fabry > >> jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry<http://dcc.uchile.cl/%7Ejfabry> > >> PLEIAD Lab - Computer Science Department (DCC) - University of Chile > >> > >> > >> > >> > >> _______________________________________________ > >> Pharo-users mailing list > >> Pharo-users(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > > > > > > _______________________________________________ > > Pharo-users mailing list > > Pharo-users(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > > > > > > > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users >

Oct. 1, 2010

Re: [Pharo-project] Chilean mailing list

by Mariano Martinez Peck

On Fri, Oct 1, 2010 at 10:18 PM, Alexandre Bergel <alexandre(a)bergel.eu>wrote: > Hi All! > > We've just create a mailing list for discussing about Pharo/Smalltalk in > Chile. > pharo-chile(a)googlegroups.com > http://groups.google.com/group/pharo-chile > Does it make sense ? I ask because maybe with clubSmalltalk (in Spanish) is enough..... > > Cheers, > Alexandre > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > 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 >

Oct. 1, 2010

[Pharo-project] Chilean mailing list

by Alexandre Bergel

Hi All! We've just create a mailing list for discussing about Pharo/Smalltalk in Chile. pharo-chile(a)googlegroups.com http://groups.google.com/group/pharo-chile Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Oct. 1, 2010

Re: [Pharo-project] Introducing smallUML: a little project to help us document :)

by Carla F. Griggio

I've just arrived home this week, so I made no progress over the last two weeks. But at ESUG I talked a little with Fernando Olivero and made me realize that I'm very close to finish the Minimal Connectors package, at least the minimal minimal connectors XD I'll let you know :) Let me know what are your projects about and how you would use this :O On Fri, Oct 1, 2010 at 4:19 PM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > > > Carla F. Griggio wrote: > > > > OK, although I tried to use what I separated in the Minimal Connectors > > package and there are still some things missing to be able to use it > > independently. So (although we're already talking about that here XD) we > > shouldn't announce that yet. > > > > Any progress with Minimal Connectors? I would love to use it in several of > the projects I'm working on. > > Thanks. > Sean > -- > View this message in context: > http://forum.world.st/Introducing-smallUML-a-little-project-to-help-us-docu… > 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 >

Oct. 1, 2010

Re: [Pharo-project] [Metacello] Re: loading groups with metacello

by Dale Henrichs

Mariano Martinez Peck wrote: > > > On Fri, Oct 1, 2010 at 7:13 PM, Dale Henrichs <dhenrich(a)vmware.com > <mailto:dhenrich@vmware.com>> wrote: > > Mariano Martinez Peck wrote: > > > > On Fri, Oct 1, 2010 at 2:16 PM, Veronica Isabel Uquillas Gomez > <vuquilla(a)vub.ac.be <mailto:vuquilla@vub.ac.be> > <mailto:vuquilla@vub.ac.be <mailto:vuquilla@vub.ac.be>>> wrote: > > Hi Mariano, > > You already saw my problem. > > With this you can check what is happening: (ConfigurationOfGlamour > project version: 'default') record: #('Core' 'Tests' 'Extras') > > > I don't understand why this loads Grease for example. Dale any idea? > I checked loadDirective but I didn't understand. > > Cheers > > Mariano > > > all the pre-requisites are being loaded and not only the groups. > > > Regards, Veronica > _______________________________________________ Pharo-project > mailing list Pharo-project(a)lists.gforge.inria.fr > <mailto:Pharo-project@lists.gforge.inria.fr> > <mailto:Pharo-project@lists.gforge.inria.fr > <mailto:Pharo-project@lists.gforge.inria.fr>> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > Okay, Here's the printString of the loadDirectives: > > linear load : > linear load : default [ConfigurationOfGlamour] > load : ConfigurationOfGrease > linear load : default [ConfigurationOfGlamour] > load : ConfigurationOfMondrian > atomic load : default [ConfigurationOfGlamour] > load : Glamour-Announcements > load : Glamour-Helpers > load : Glamour-Core > load : Glamour-Presentations > load : Glamour-Browsers > load : Glamour-Tests-Core > load : Glamour-Morphic-Theme > load : Glamour-Examples > load : Glamour-Tools > linear load : default [ConfigurationOfMondrian] > load : ConfigurationOfHealthReportProducer > linear load : default [ConfigurationOfMondrian] > load : ConfigurationOfProfStef > atomic load : default [ConfigurationOfMondrian] > linear load : 1.3 [ConfigurationOfProfStef] > load : ConfigurationOfShout > linear load : 1.3 [ConfigurationOfProfStef] > linear load : 1.1.1 [ConfigurationOfShout] > load : Shout-lr.90 > load : ShoutWorkspace.pharo-1-1-SeanDeNigris.6 > load : ProfStef-Core-LaurentLaffont.11 > load : ProfStefBrowser-LaurentLaffont.26 > load : ProfStef-Tests-LaurentLaffont.8 > load : ProfStef-Help-LaurentLaffont.1 > load : Mondrian > load : CollectionExtensions > atomic load : 0.1-baseline [ConfigurationOfHealthReportProducer] > load : HealthReportProducer > load : Glamour-Scripting > linear load : 1.0-alpha9.1 [ConfigurationOfGrease] > load : ConfigurationOfRefactoringBrowser > linear load : 1.0-alpha9.1 [ConfigurationOfGrease] > load : Grease-Core-lr.37 > load : Grease-Pharo-Core-jok.18 > linear load : 1.3 [ConfigurationOfRefactoringBrowser] > load : AST-Core-lr.73 > load : Refactoring-Core-lr.136 > load : Grease-Slime-jok.5 > load : Magritte-Model > load : Magritte-Morph > load : Glamour-Morphic-Renderer > load : Glamour-Tests-Morphic > > and here's the section related to Grease (very end of directives): > > > load : Glamour-Scripting > linear load : 1.0-alpha9.1 [ConfigurationOfGrease] > load : ConfigurationOfRefactoringBrowser > linear load : 1.0-alpha9.1 [ConfigurationOfGrease] > load : Grease-Core-lr.37 > load : Grease-Pharo-Core-jok.18 > linear load : 1.3 [ConfigurationOfRefactoringBrowser] > load : AST-Core-lr.73 > load : Refactoring-Core-lr.136 > load : Grease-Slime-jok.5 > load : Magritte-Model > load : Magritte-Morph > load : Glamour-Morphic-Renderer > load : Glamour-Tests-Morphic > > The load directive is in "load order" which is "reverse prerequisite > order". In other words, the clue for why Grease is loaded lies in > the directives _following_ the Grease directives... > > > > ahhhhhhhh I was looking BEFORE, not after hehehe.. what an idiot I am :) Not necessarily ... I didn't "figure that out" until after I'd understood why Grease was being loaded ... haha! Dale

Oct. 1, 2010