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

Re: [Pharo-project] XMLRPC Project - Progress Report

by Mariano Martinez Peck

On Thu, Sep 23, 2010 at 12:49 AM, Miguel CobÃ¡ <miguel.coba(a)gmail.com> wrote: > El miÃ©, 22-09-2010 a las 19:16 -0300, GermÃ¡n Arduino escribiÃ³: > > Hi Everybody: > > > > I reorganized the XMLRPC packages, integrating the changes of Skrish > > (currently on PharoGoodies) renaming the packages in four categories: > > > > XMLRPC-Client-Core > > XMLRPC-Client-Tests > > XMLRPC-Server-Core > > XMLRPC-Server-Tests > > > > Next step: Build the following metacello configurations: > > > > ConfigurationOfXMLRPCClient > > ConfigurationOfXMLRPCServer > > ConfigurationOfXMLRPCAll > > You don't need three configurations, just create one and create 3 groups > 'All','Server', 'Client'. > > You were faster than :) I was going to answer exactly the same...one ConfigurationOfXMLRPC and different groups: - 'All' - 'Server' - 'Server with Tests' - 'Client' - 'Client with Tests' -etc.... Check ConfigurationOfMagma since it does almost the same I think. cheers mariano Cheers > > > > > > I want to ask to any person wanting to contribute with XMLRPC project > > take contact with me to coordinate efforts. > > > > > > Cheers. > > > > > > -- > Miguel CobÃ¡ > http://miguel.leugim.com.mx > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 23, 2010

Re: [Pharo-project] I am missing userful functionality?

by StÃ©phane Ducasse

Hi igor I cannot help but indeed we need a real brand new classbuilder with a nice MOP for instance migrating too. We will start to work on that probably december/january. Stef On Sep 23, 2010, at 12:03 AM, Igor Stasenko wrote: > Hello, guys > > i want to do a simple thing, which can be expressed by following: > > oldClass replaceWith: newClass migrateInstances: [:inst | > ... ] > > In my case, first, i installing a WeakFinalizationRegistry class, > and then want to replace an old WeakRegistry class with it, > silently and painlessly. > > I end up with following script: > > | old new oldClass newClass | > old := OrderedCollection new. > new := OrderedCollection new. > > > "migrate instances" > WeakRegistry allInstancesDo: [:registry | | newr | > old add: registry. > newr := WeakFinalizationRegistry basicNew initialize. > registry migrateTo: newr. > new add: newr ]. > old asArray elementsForwardIdentityTo: new asArray. > > "replace the class" > > oldClass := WeakRegistry. > newClass := WeakFinalizationRegistry. > > Smalltalk forgetClass: #WeakFinalizationRegistry logged: false. > newClass superclass removeSubclass: newClass. > newClass setName: #WeakRegistry. > oldClass becomeForward: newClass. > > -- > > it looks a bit hackish, and i wonder how to do that in more 'standard' way. > > Initially replacing classes was: > > oldClass removeFromSystem. > newClass rename: #WeakRegistry > > the problem with that, is that all compiled methods , which was > referring to old class through association, > still using it, and to get rid of them i have to recompile them. > > > > -- > 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

Sept. 23, 2010

Re: [Pharo-project] Changes in external packages for Pharo 1.2

by StÃ©phane Ducasse

keep it simple for now. Let us focus on fixing 1.2 > Hi folks. I would like to write now the changes for the development image for Pharo 1.2. > > Right now I have the following: > > - Let (load) NewInspector in the image, but put the old one as the default. Several people were against NewInspector. I like it for example, but anyway, if it is present in the image then I would be able to use it. > - Add Memory Monitor tool from Alexandre Bergel. > - Add AutoTest from Laurent Laffont. > - Add GoferProjectLoader from Esteban Lorenzano, to easily manage Metacello. > > For any package we include, it would be AWESOME to have: > - tests > - a Metacello configuration > > So, questions: > > 1) do you more ore less agree with them??? (we cannot be all agree with ALL items) > 2) for package developers: do you agree we include all of them in PharoDev? will you help maitaining them? are they all MIT? (I think so) Please, confirm us this. > 3) do you think there are more packages/projects we should include? What about, for example: > Keep that for later. > - WorkingSet from Romain Robbes > - Algernon (still doesn't work in 1.1) > - TDDFacilties from Hernan Wilkinson > - SimpleLogger from German Arduino > > I know this is not Dev, but I hope in Pharo1.2 we will have: > - The new method finder from Benjamin that mixes both, and remove the old ones. > - The new RecentSubmisons, and remove the old one. > > Thanks > > Mariano > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 23, 2010

Re: [Pharo-project] DejaVu extra sizes Re: DemoMode should not change Fonts only sizes?

by StÃ©phane Ducasse

Yes I think that we should just get better at packaging/loading.... But this package is important so it should be a supported package. Stef > Due to the size issue, I wouldn't include them all by default. > > Maybe we could make some clever set of MC packages that you can load for each font size that you want ? > Or load the spec data from a file/url ? > > You have a point here. Maybe we don't need to put all the families and all the size in the core....just the most used ones. > > Then, in the Dev image we can load all the rest, and the settings to set the Demo Fonts. > > what do you think alain? > > Anyway, all these fonts should be removed in #cleanUpForProduction I think. > > cheers > > mariano > > > I think most people will only need one or two sizes. The fallback should just be miminal. > > Sven > > > _______________________________________________ > 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. 23, 2010

Re: [Pharo-project] Class comment in OB

by StÃ©phane Ducasse

but can you check in latest 1.2 to be sure. On Sep 22, 2010, at 10:34 PM, Schwab,Wilhelm K wrote: > Stef, > > I noticed it in 1.1, so it's probably old news. >

Sept. 23, 2010

Re: [Pharo-project] ESUG actions (was: Best Spreading Smalltalk Actions)

by StÃ©phane Ducasse

:) This is fun because one of the board member raised the question just before this remark. We are not sure that rebranding is good but so far I like your slogan. And we welcome any smalltalker. The goals of esug are simple (you can see that in the first talk of esug and also the one of serge about future actions) - create energy in the community (via the conf via new user groups) - support open-source development - support business in Smalltalk - push/help teacher teaching Smalltalk - bring open-source and business together (check my last talk at Barcelona - we need strong vendors and strong open-source) ESUG never took into account geographic perspective, we sent books all over the world in the past. And student volunteers came from everywhere :) Stef > > I think ESUG has been an outstanding success for Smalltalk globally and > therefore deserves to be called The Smalltalk Users Group. TSUG. Such a name > change will also give a better impression to Smalltalk and is not untrue. > > All the best, > Aik-Siong Koh > -- > View this message in context: http://forum.world.st/Best-Spreading-Smalltalk-Actions-tp2542307p2551292.ht… > 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. 23, 2010

Re: [Pharo-project] [squeak-dev] Morphic

by Hannes Hirzel

> > Why can't we have stuff from Sophie back to Squeak/Pharo? > - only the Sophie developers are familiar with the code and they are not > motivated enough to extract it Not necessarily their task..... :-) Writing libraries and reusable components is a different project. > - the license is BSD, so the code can't be included in Pharo/Squeak I googled for BSD MIT license compatibility and found some interesting information see for example http://www.dwheeler.com/essays/floss-license-slide.html the paragraph about BSD in http://producingoss.com/en/license-choosing.html The license might be compatible depending on the "version" of the BSD license. And if not you could extract code and then ask the developers to release it as MIT. MIT and BSD are very close (or the same depending on the version) To summarize: The statement "the license is BSD, so the code can't be included in Pharo/Squeak" is too strong. There might be some problems including code, but they may be solved easily with by writing a few emails.... --Hannes

Sept. 23, 2010

Re: [Pharo-project] ESUG actions (was: Best Spreading Smalltalk Actions)

by Norbert Hartl

On 23.09.2010, at 03:42, askoh wrote: > > I think ESUG has been an outstanding success for Smalltalk globally and > therefore deserves to be called The Smalltalk Users Group. TSUG. Such a name > change will also give a better impression to Smalltalk and is not untrue. > So you would say it is "Everyones Smalltalk User Group" ? :) The abbreviation would than be .... ESUG .. oh, great! Norbert

Sept. 23, 2010

[Pharo-project] osprocess does not work on Squeak 5.8b10

by Tudor Girba

Hi, On the Coq VM from Eliot, invoking OSProcess on a Mac worked well. On Squeak 5.8b10 it crashes by saying: "process accessor module not available". Is there a way to fix this? Cheers, Doru -- www.tudorgirba.com "Speaking louder won't make the point worthier."

Sept. 23, 2010

Re: [Pharo-project] ESUG actions (was: Best Spreading Smalltalk Actions)

by Tudor Girba

+1 Doru On 23 Sep 2010, at 03:42, askoh wrote: > > I think ESUG has been an outstanding success for Smalltalk globally and > therefore deserves to be called The Smalltalk Users Group. TSUG. Such a name > change will also give a better impression to Smalltalk and is not untrue. > > All the best, > Aik-Siong Koh > -- > View this message in context: http://forum.world.st/Best-Spreading-Smalltalk-Actions-tp2542307p2551292.ht… > 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 -- www.tudorgirba.com "Some battles are better lost than fought."

Sept. 23, 2010