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

Re: [Pharo-project] Gettext package?

by Hilaire Fernandes

I ported the gettext package from Etoys to Pharo with help of other (Henrik). I have to admit I mostly forgot about its internal, even if I amn using it for DrGeo. In between, some part of the gettext package in Etoys was improved, I forgot which part exactly. Bert may remember a bit more. Do whatever you think is appropriate with the package. As you hacked the package recently you are definitely in a better position to split it in different component. Hilaire Le 24/05/2011 11:11, Johan Brichau a Ã©crit : > Hi guys, > > What is the future of the Gettext package in the PharoNonCorePackages repository? > Is the intention to include it in Pharo core? Should that package become a separate project? Something else? > > I am asking this because I am using it for internationalization support in our Seaside apps (together with the Gettext-Seaside package by Philippe Marschall). > Hence, I created a port of the relevant parts to GemStone, following the "develop in Pharo, deploy in GemStone" philosophy. > > Now, the ported package is a complete duplicate + appropriate changes, but it's better if we create a common package and separate the platform-specific parts out. > But I would not want to interfere with anyone's plans, specifically Hilaire Fernandes' plans, probably (who seems to be the author of the package). > > So, I would like to get in touch with the stakeholders of the package and discuss where it's going. > > cheers > Johan > > (see more info below -- mails > > > Begin forwarded message: > >> From: Johan Brichau <johan(a)inceptive.be> >> Date: 24 May 2011 08:26:33 GMT+02:00 >> To: Philippe Marschall <philippe.marschall(a)gmail.com> >> Cc: GemStone Seaside beta discussion <beta(a)seaside.gemstone.com> >> Subject: Re: [GS/SS Beta] Gettext (for use by Gettext-Seaside) ported to Gemstone >> Reply-To: GemStone Seaside beta discussion <beta(a)seaside.gemstone.com> >> >> Hi Philippe, >> >> Yes, those are classes I left out (but they don't have the WA prefix). >> >> I also prefer that there is a shared common package for both platforms but there are more differences spread over several methods. >> Off the top of my head, most differences are located in the MOFile class. Also, the 'startup' methods that are used to trigger a locale refresh when starting the Pharo image are not applicable in Gemstone. >> >> I'm willing to work towards a common package + platform-specific packages. Probably, we have to hear what the Pharo people (and specifically Hilaire Fernandes) think about it. >> >> cheers >> Johan >> >> On 23 May 2011, at 20:08, Philippe Marschall wrote: >> >>> 2011/5/23 Johan Brichau <johan(a)inceptive.be>: >>>> Hi all, >>>> >>>> The Gettext [1] implementation of Pharo has now been ported to Gemstone, such that we can use it for internationalization in web applications together with Gettext-Seaside. >>>> More precisely, the Gettext package is a prerequisite for Gettext-Seaside. >>>> >>>> With the "develop in Pharo, deploy in Gemstone" philosophy, I ported only those parts that are required to deploy the translation files in the Seaside web apps. >>>> The implementation that generates translation files from the codebase is a bit more entrenched into platform-specific libraries. So, one has to generate the translation catalogs to disk in Pharo, edit them with a tool like poedit, and deploy the locale with the Gemstone deployment. >>> >>> Clever. I guess WAGetTextExporter and WATranslatedArgumentsFinder are >>> the classes that don't work in Gemstone. If so I could split the >>> package into a portable part and a Pharo part so you don't need to >>> load them im GemSonte. >>> >>> Cheers >>> Philippe >> > > > -- Education 0.2 -- http://blog.ofset.org/hilaire

May 24, 2011

Re: [Pharo-project] [Seaside] ESUG SummerTalk - Fuel, binary object serializer

by Tudor Girba

Congratulations, Martin! This is great news. I am looking forward to using it even tighter in Moose :) Cheers, Doru On 24 May 2011, at 22:39, Martin Dias wrote: > Hi folks. I am really happy to announce that ESUG is sponsoring me for Fuel development through the ESUG SummerTalk. I am Martin Dias, a student at Buenos Aires, Argentina. The idea behind this SummerTalk is to implement Fuel, a binary, fast and general-purpose object graph serializer in Pharo. It is based on VisualWorks' Parcels ideas. > > Actually, the project has already started since several months. Tristan Bourgois and I started with the project while doing an internship with RMoD, INRIA. Since a couple of months, Mariano Martinez Peck joined the team, and now he is the official mentor in the SummerTalk. > > ESUG website for SummertTalk: http://www.esug.org/wiki/pier/Promotion/SummerTalk/SummerTalk2011 > > The website with all the necessary information is here: http://rmod.lille.inria.fr/web/pier/software/Fuel > It even includes slides explaining the algorithm. In addition, a paper is in progress. > > For the moment, Fuel already provides the following features: > > - Fast pickle format. It is much faster to materialize than to serialize. > - Correctly support class reshape (when the class of serialized objects has changed). > - Serialize ANY kind of object. For the moment there is no object to our knowledge that we cannot serialize and materialize. > - Be able to completely serialize classes and traits (not just a global name). > - Support cycles and avoid duplicates in the graph. > - Integration to Moose with an extension to export and import their models. > - Detection of globals: for example if you serialize Transcript, it is not duplicated and instead managed as a global reference. > - Solve common problems like Set rehash. > - Buffered writing: we use a buffered write stream for the serialization part (thanks Sven!). > - No need of special support from the VM. > - Try to have a good object oriented design. > - Well tested (about 120 tests, for the moment). > - Large set of benchmarks (even benchmarks for Moose extension). > > And of course, there are a lot features for the future. You can see some of them in the website and some in the issue tracker: http://code.google.com/p/fuel/issues/list > > We really appreciate all kind of feedback and comments. If you want to try it, check in the website how to do it. It is extremely easy. > > Once again, I want to thank a lot to ESUG for sponsoring the project. I plan to create a "news" section in the website with some RSS. I will keep you informed. > > Best regards, > Martin > > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside -- www.tudorgirba.com "Being happy is a matter of choice."

May 24, 2011

[Pharo-project] ESUG SummerTalk - Fuel, binary object serializer

by Martin Dias

Hi folks. I am really happy to announce that ESUG is sponsoring me for Fuel development through the ESUG SummerTalk. I am Martin Dias, a student at Buenos Aires, Argentina. The idea behind this SummerTalk is to implement Fuel, a binary, fast and general-purpose object graph serializer in Pharo<http://www.pharo-project.org/>. It is based on VisualWorks' Parcels ideas. Actually, the project has already started since several months. Tristan Bourgois and I started with the project while doing an internship with RMoD, INRIA <http://rmod.lille.inria.fr/web/pier>. Since a couple of months, Mariano Martinez Peck <http://marianopeck.wordpress.com/> joined the team, and now he is the official mentor in the SummerTalk. ESUG website for SummertTalk: http://www.esug.org/wiki/pier/Promotion/SummerTalk/SummerTalk2011 The website with all the necessary information is here: http://rmod.lille.inria.fr/web/pier/software/Fuel It even includes slides explaining the algorithm. In addition, a paper is in progress. For the moment, Fuel already provides the following features: - Fast pickle format. It is much faster to materialize than to serialize. - Correctly support class reshape (when the class of serialized objects has changed). - Serialize ANY kind of object. For the moment there is no object to our knowledge that we cannot serialize and materialize. - Be able to completely serialize classes and traits (not just a global name). - Support cycles and avoid duplicates in the graph. - Integration to Moose <http://www.moosetechnology.org/> with an extension to export and import their models. - Detection of globals: for example if you serialize Transcript, it is not duplicated and instead managed as a global reference. - Solve common problems like Set rehash. - Buffered writing: we use a buffered write stream for the serialization part (thanks Sven!). - No need of special support from the VM. - Try to have a good object oriented design. - Well tested (about 120 tests, for the moment). - Large set of benchmarks (even benchmarks for Moose extension). And of course, there are a lot features for the future. You can see some of them in the website and some in the issue tracker: http://code.google.com/p/fuel/issues/list We really appreciate all kind of feedback and comments. If you want to try it, check in the website how to do it. It is extremely easy. Once again, I want to thank a lot to ESUG for sponsoring the project. I plan to create a "news" section in the website with some RSS. I will keep you informed. Best regards, Martin

May 24, 2011

Re: [Pharo-project] Smalltalk/Pharo User Group in Spain

by Rafael Luque

Thank you Mariano, I've just joined to this group. 2011/5/24 Mariano Martinez Peck <marianopeck(a)gmail.com> > > > On Tue, May 24, 2011 at 12:46 PM, Rafael Luque < > rafael.luque.leiva(a)gmail.com> wrote: > >> >> I don't know the spanish mailing list about Smalltalk or Pharo. > > > <clubSmalltalk(a)googlegroups.com>, > > we are all there :) > > >

May 24, 2011

[Pharo-project] [COTDC] 68 - MultiNewParagraph

by laurent laffont

Today: MultiNewParagraph Comment Of The Day Contest - One Day One Comment Rules: #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). #2: If you cannot comment it, deprecate it. Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest Laurent

May 24, 2011

Re: [Pharo-project] [Pharo-users] [COTDC] 67#2 - MultiDisplayScanner

by laurent laffont

On Mon, May 23, 2011 at 10:51 PM, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr> wrote: > I'm a class related to the computation of characters counting for text > flow. > > I'm probably wrong but this is what I think I remember from what I guessed > :) > COTDC new guessCommentOf: MultiDisplayScanner. :) Laurent. > Stef > > > On May 23, 2011, at 9:40 PM, laurent laffont wrote: > > > Today: MultiDisplayScanner > > > > > > Comment Of The Day Contest - One Day One Comment > > Rules: > > #1: Each day a not commented class is elected. Each day the best comment > will be integrated with name of the author(s). > > #2: If you cannot comment it, deprecate it. > > Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest > > > > Laurent > > > > >

May 24, 2011

Re: [Pharo-project] Tiling windows

by laurent laffont

On Tue, May 24, 2011 at 9:48 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Ok we need a 1.3 version because now we get excited. > Here's a first shot (not integrated to TaskBarMorph though) which works in 1.3: Gofer it squeaksource: 'TilingWindowManager'; package: 'TWM'; load. TWMBar new open. The real manager is TilingWM. Try: (TilingWM forWorld: World) tileVisibleWindows. (TilingWM forWorld: World) tileBrowsers. (TilingWM forWorld: World) tileWorkspaces. Laurent. > Stef > > On May 24, 2011, at 8:51 AM, laurent laffont wrote: > > > > > > > 2011/5/24 GastÃ³n Dall' Oglio <gaston.dalloglio(a)gmail.com> > > Laurent and corious :) > > > > I add some TasklistMorph behavior. With the open list (cmd-rigth or > cmd-left): > > * cmd-up: maximize all windows > > * cmd-down: minimize all windows > > * cmd-b: apply SystemBrowser windows's filter > > * cmd-w: apply Worspace windows's filter > > * cmd-a: remove windows's filter > > > > ** The cmd-b work in 1.2.1, in 1.3 you have to change > TasklistMorph>>keyStroke: because I use OBSystemBrowser class by way of > example and therefore does not perform properly filtered. > > > > > > I did not understand until I enable the setting "Keep task list open" :) > > > > I've started a TilingWindowManager project (I will upload it this evening > on SS) so we can put all our stuff + tests without polluting TaskBar & > Tasklist too much. > > > > Indeed, after 3 days I can't live without the tiling buttons :) > > > > Laurent. > > > > > > > > 2011/5/23 laurent laffont <laurent.laffont(a)gmail.com> > > 2011/5/23 GastÃ³n Dall' Oglio <gaston.dalloglio(a)gmail.com> > > Laurent, I attached a package I've added some improvements to your work, > I have found useful. Of course I am not knowledgeable about morph, just > added some and perhaps can serve as inspiration. > > > > Thanks GastÃ³n, I like the idea. It will be a good step forward in having > better window management. Now we should rewrite this clean + tests (may be > adding the notion of widgets like in KDE / Gnome). > > > > As windows fill all the space, would be good to have a button to open the > world menu. > > > > I would love having the possibility of splitting the World + back and > forward configuration like Emacs winner mode, keyboard driven. > > > > Since several days I use http://most-advantageous.com/optimal-layout/ on > OSX and there's some great ideas too. > > > > Laurent. > > > > > > > > 2011/5/23 laurent laffont <laurent.laffont(a)gmail.com> > > On 1.2: > > > > Gofer it > > squeaksource: 'LaurentLSandbox'; > > version: 'Polymorph-Widgets-LaurentLaffont.388'; > > load. > > > > > > Then open or move a window so the TaskBar is updated and you have a new > "magic" button on bottom left. > > > > (note this is hacky actually, I will write a nicer version this week if > people like it). > > > > Laurent. > > > > On Mon, May 23, 2011 at 9:06 AM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > > send a cs that we can play with it :) > > > > On May 22, 2011, at 8:25 PM, laurent laffont wrote: > > > > > Hi, > > > > > > what do you think of adding this in Pharo ? > > > > > > |taskbar tileWindowsBlock| > > > > > > tileWindowsBlock := [ > > > |windows numberOfColumns numberOfRows windowWidth windowHeight| > > > windows := (World submorphs select: [:m| m isSystemWindow and: [m > isNotMinimized]]) asOrderedCollection. > > > numberOfColumns := windows size sqrtFloor. > > > numberOfRows := (windows size / numberOfColumns) rounded. > > > windowWidth := World width // numberOfColumns.. > > > windowHeight := World height - taskbar height // numberOfRows. > > > > > > Matrix > > > rows: numberOfRows > > > columns: numberOfColumns > > > tabulate: [:row :column| |window| > > > windows ifNotEmpty: [ > > > window := windows remove: windows first. > > > window > > > bounds: ( > > > ((column - 1 * windowWidth) @ (row - 1 * > windowHeight)) > > > extent: (windowWidth) @ windowHeight) > > > ] > > > ] > > > ]. > > > > > > > > > taskbar := (World submorphs detect: [:m| m isTaskbar]). > > > > > > taskbar > > > addMorph: (IconicButton new > > > target: tileWindowsBlock; > > > actionSelector: #value; > > > labelGraphic: taskbar theme smallWindowIcon; > > > color: Color transparent; > > > yourself). > > > > > > > > > Laurent Laffont - @lolgzs > > > > > > Pharo Smalltalk Screencasts: http://www.pharocasts.com/ > > > Blog: http://magaloma.blogspot.com/ > > > Developer group: http://cara74.seasidehosting.st > > > > > > > > > > > > > > > > > > > >

May 24, 2011

Re: [Pharo-project] Questions of understanding

by Mariano Martinez Peck

On Tue, May 24, 2011 at 5:37 PM, Friedrich Dominicus < frido(a)q-software-solutions.de> wrote: > Ok I spend my time today on building a new virtual machine. And my > assumptions in my last mail were wrong. The code is not hand-written > but is generated. Now I understand that. But now I see that while > building the virtual machine the stuff probabably is taken form the > PharoV10.sources file from which it seems SerialPlugin.c is build. > > Sorry, I didn't read the email until now, the subject was not very good ;) > Now in PharoV10.sources there is are not the patches to use ports by > Name as needed in Linux. So now my question is. After I've build a new > virtual machine how can I modify one of the plugins to update them. > > For the plugins, there are two parts: the VMMaker part (usually a plugin is a subclass of InterpreterPlugin) and the C part. Some plugins are directly included in the VMMaker package/repostitory and some others are in different places (usually when they are not "core" plugins). The VMMaker part of SerialPlugin, is in VMMaker package, so if you followed my instructions, when you downloaded VMMAker, you should have downloaded the class SerialPlugin which is in the 'VMMaker-Plugins' category. Now, if you need to modify something to the "platform code", hand written C code, then such plugins can be found in Git or in the SVN. In git, they are in https://gitorious.org/cogvm/ For your case it should be: https://gitorious.org/cogvm/blessed/blobs/master/platforms/unix/plugins/Ser… > So the sources file contains things like openPort but not > openPortByName. So what do I have to do to get into the patches such > that the new SerialPlugin.c can be generated? > > Ah yes I used the pages at > > http://marianopeck.wordpress.com/2011/04/10/building-the-vm-from-scratch-us… > > now you can read: http://marianopeck.wordpress.com/2011/04/05/first-stop-vms-scm-and-related-… :) > for learning that.... > > Regards > Friedrich > > -- Mariano http://marianopeck.wordpress.com

May 24, 2011

Re: [Pharo-project] Questions of understanding

by Marcus Denker

On May 24, 2011, at 5:37 PM, Friedrich Dominicus wrote: > Ok I spend my time today on building a new virtual machine. And my > assumptions in my last mail were wrong. The code is not hand-written > but is generated. Now I understand that. But now I see that while > building the virtual machine the stuff probabably is taken form the > PharoV10.sources file from which it seems SerialPlugin.c is build. > PharoV10.sources should not contain any VM Related sources... the VMMaker package has the source for the VM. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

May 24, 2011

Re: [Pharo-project] Questions of understanding

by Friedrich Dominicus

Ok I spend my time today on building a new virtual machine. And my assumptions in my last mail were wrong. The code is not hand-written but is generated. Now I understand that. But now I see that while building the virtual machine the stuff probabably is taken form the PharoV10.sources file from which it seems SerialPlugin.c is build. Now in PharoV10.sources there is are not the patches to use ports by Name as needed in Linux. So now my question is. After I've build a new virtual machine how can I modify one of the plugins to update them. So the sources file contains things like openPort but not openPortByName. So what do I have to do to get into the patches such that the new SerialPlugin.c can be generated? Ah yes I used the pages at http://marianopeck.wordpress.com/2011/04/10/building-the-vm-from-scratch-us… for learning that.... Regards Friedrich

May 24, 2011