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

Re: [Pharo-dev] [ann] moose 4.8

by Tudor Girba

Yeah, I used to work with Smalltalk quite a lot. Now, I only work with Pharo, and I do not miss Smalltalk at all :) Doru On Fri, Sep 13, 2013 at 11:11 AM, Damien Cassou <damien.cassou(a)gmail.com>wrote: > On Fri, Sep 13, 2013 at 11:05 AM, Serge Stinckwich > <serge.stinckwich(a)gmail.com> wrote: > > Ouaa, there is still PL/1 on the earth ? > > > yes! and Smalltalk too :-) > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > > -- www.tudorgirba.com "Every thing has its own flow"

Sept. 13, 2013

Re: [Pharo-dev] [ann] moose 4.8

by Damien Cassou

On Fri, Sep 13, 2013 at 11:05 AM, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > Ouaa, there is still PL/1 on the earth ? yes! and Smalltalk too :-) -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Sept. 13, 2013

Re: [Pharo-dev] [ann] moose 4.8

by Serge Stinckwich

Ouaa, there is still PL/1 on the earth ? EnvoyÃ© de mon iPhone Le 13 sept. 2013 Ã 09:43, "phil(a)highoctane.be" <phil(a)highoctane.be> a Ã©crit : > Very nice. > > Congratulations! I've started using Moose for some software visualizations (currently for PL/1 code, but not parsing etc, just metrics I get my own way). > > Keep up the good work. > > Phil > > > > On Fri, Sep 13, 2013 at 7:04 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> We are happy to announce version 4.8 of the Moose Suite: >> http://moosetechnology.org/download/4.8 >> >> Description >> -- >> >> This was supposed to be a minor release, but in the end it turned out to be a major release with significant improvements. >> >> The key highlights are: >> - Based on Pharo 2.0. >> - All built-in visualizations use Roassal. >> - Roassal received a significant performance boost and new smart graph layouts like TreeMapLayout or ForceBasedLayout. >> - Roassal uses Athens for nice looking vectorial graphics. >> - New charting engine based on Roassal: Graph-ET. >> - Glamour changed to enable dynamic scripts, while still remaining backward compatible. >> - Glamour received a RubricTextPresentation for using the new Rubric text morph. >> - Glamour, Roassal, EyeSee, Graph-ET editors are more robust when dealing with errors in scripts.- New GTDebugger with dedicated workflows for Announcements, PetitParser and Glamour itself. >> - Extended GTInspector for several object types. >> - Usable version of GTMetaceller for handling Metacello configurations. >> - FAMIX was strengthen to handle functions better in various programming languages. >> - New free type fonts and simpler whitespace-loving theme. >> - Lower memory footprint for large models. >> - Faster MSE import. >> >> A list of issues addressed in this release can be found at: >> http://code.google.com/p/moose-technology/issues/list?can=1&q=status=Fixed%… >> >> >> Installation >> -- >> >> The Moose Suite 4.8 comes for each platform as a separate bundle: >> - Mac: https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_8-mac.zip >> - Windows: https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_8-win.zip >> - Linux: https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_8-linux.zip >> >> The Moose Suite 4.8 can also be loaded in a Pharo 2.0 image either from the Configuration Browser, or by executing the following script: >> >> Gofer new >> smalltalkhubUser: 'Moose' project: 'Moose'; >> package: 'ConfigurationOfMoose'; >> load. >> ((Smalltalk at: #ConfigurationOfMoose) >> project version: '4.8-snapshot') load >> >> >> Enjoy, >> The Moose Team >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >

Sept. 13, 2013

Re: [Pharo-dev] [Moose-dev] [ann] moose 4.8

by Andrei Vasile Chis

On Fri, Sep 13, 2013 at 8:11 AM, Ben Coman <btc(a)openinworld.com> wrote: > ** > Great news. Well done all the Moose Team. I've been on a bit of a hiatus > until recently and can't wait to get more stuck into Roassal on Athens. > Are there any videos on the different GTdebugger workflows? > Right now there is just one video with a short introduction: http://scg.unibe.ch/research/moldabledebugger More will come :)

Sept. 13, 2013

Re: [Pharo-dev] Pharo Sprint in Buenos Aires - this saturday!

by Goubier Thierry

Le 12/09/2013 20:15, StÃ©phane Ducasse a Ã©crit : > >> Overall synchronisation is nice. >> >> I've replaced MessageBrowser and the Finder UI in my own Pharo > with what? A RBEnvironment scoped version of my AltBrowser, with a bit of tree filtering on the display. Finder is like the Finder plugin in Nautilus, except that it opens a scoped instance of the browser. MessageBrowser is replaced by a scoped instance of the browser. And the browser knows how to adjust the tree display depending on the scope (pruning the tree and adapting the display of items). Makes exploring code a lot easier mostly because of smart suggestions, otherwise I would do implementorsOf:, get the message browser, and use browse on each result one by one to open a new browser, and there have smart suggestions to do implementorsOf: to be able to follow a cascade of message sends :( I hated being in the finder, looking at the code pane and a multi arguments message and saying to myself 'but how will I do sendersOf or implementorsOf of that message?' >> , and I now have unified menus, shortcuts and smart suggestions and I find it really, really nice. > > do you have suggestion for the menus unification? Have a single code source editor* for all code panes, with the same menu building** code in each :) * This is probably the case in the old framework and the reason for having all thoses menu actions inside SmalltalkEditor. ** But something pluggable so that we may still be able to experiment! Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Sept. 13, 2013

human language translation service

by btc＠openinworld.com

Through another application I just bumped into a human language translation service that is apparently free to open source projects. I haven't looked into it yet, but thought it might be of interest to others here. https://www.transifex.com/features/translation-management/ https://www.transifex.com/plans/ cheers -ben

Sept. 13, 2013

Re: [Pharo-dev] [ann] moose 4.8

by phil＠highoctane.be

Very nice. Congratulations! I've started using Moose for some software visualizations (currently for PL/1 code, but not parsing etc, just metrics I get my own way). Keep up the good work. Phil On Fri, Sep 13, 2013 at 7:04 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > We are happy to announce version 4.8 of the Moose Suite: > http://moosetechnology.org/download/4.8 > > Description > -- > > This was supposed to be a minor release, but in the end it turned out to > be a major release with significant improvements. > > The key highlights are: > - Based on Pharo 2.0. > - All built-in visualizations use Roassal. > - Roassal received a significant performance boost and new smart graph > layouts like TreeMapLayout or ForceBasedLayout. > - Roassal uses Athens for nice looking vectorial graphics. > - New charting engine based on Roassal: Graph-ET. > - Glamour changed to enable dynamic scripts, while still remaining > backward compatible. > - Glamour received a RubricTextPresentation for using the new Rubric text > morph. > - Glamour, Roassal, EyeSee, Graph-ET editors are more robust when dealing > with errors in scripts.- New GTDebugger with dedicated workflows for > Announcements, PetitParser and Glamour itself. > - Extended GTInspector for several object types. > - Usable version of GTMetaceller for handling Metacello configurations. > - FAMIX was strengthen to handle functions better in various programming > languages. > - New free type fonts and simpler whitespace-loving theme. > - Lower memory footprint for large models. > - Faster MSE import. > > A list of issues addressed in this release can be found at: > > http://code.google.com/p/moose-technology/issues/list?can=1&q=status=Fixed%… > > > Installation > -- > > The Moose Suite 4.8 comes for each platform as a separate bundle: > - Mac: > https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_8-mac.zip > - Windows: > https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_8-win.zip > - Linux: > https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_8-linux.zip > > The Moose Suite 4.8 can also be loaded in a Pharo 2.0 image either from > the Configuration Browser, or by executing the following script: > > Gofer new > smalltalkhubUser: 'Moose' project: 'Moose'; > package: 'ConfigurationOfMoose'; > load. > ((Smalltalk at: #ConfigurationOfMoose) > project version: '4.8-snapshot') load > > > Enjoy, > The Moose Team > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Sept. 13, 2013

Re: [Pharo-dev] Annotating classes

by kilon

I like to hear some more details on this and other opinions too. One of the thing I want to work is a new SystemBrowser with more flexible browsing system. I take inspiration from preset browsers in software sysnthesizers. Each preset represent a sound that can be manipulated with real time controls, the problem is that there thousands of presets the same way there are thousands of classes. The initial implementation was to brake presets to groups / categories , same way SystemBrowser has packages. Unfortunately that still made browsing through presets very tedious and long process. The modern system is tag based , for example if I want to select a sound present I a presented with a row and columns of buttons, each row is a category of tags , each cell is a tag. For example I could choose Timbre : metalic , Type: pad, Speed: fast, Rythm : non-rythmic etc these criterias then would allow me to browse only a limited amount of presets having those tags. I would have to reset the browser (which disables all tag choices) to view all presets again. I am considering implementing something similar for class and even methods. At first I was considering what Igor said, an instance variable that contained a dictionary/hash-table associating tags with their categories providing also a gui to set those tags easily. However I was wondering like the original poster if there is a better way to "annotate" classes and if there is any way to "annotate" methods . Esteban A. Maringolo wrote > Isn't answering to a message not enough? > > Like #nbStruc #ormTableName etc. > > Pragmas are somehow orthogonal to the common message sending and method > lookup. > > > Esteban A. Maringolo > > > 2013/9/12 Igor Stasenko < > siguctua@ > > > >> >> >> >> On 12 September 2013 13:56, Torsten Bergmann < > astares@ > > wrote: >> >>> We can mark methods with pragmas and ask the pragma collector >>> to give the methods marked with it. >>> >>> Do we (already) have some kind of pragma like mechanism to annotate >>> classes? I mean a general mechanism that one can use to mark classes >>> with pragmas/settings/ ...? >>> >>> There are various scenarios where this might be useful: >>> - an ORM mapper would like to associate a persistence class with a >>> table name >>> - an NBExternalStructure subclass wrapping a structure can be >>> annotated >>> with >>> the original struct name >>> - ... >>> >>> >> Why so complicated (e.g. pragmas) ? Just add one more inst var , like >> 'annotation' for Class object >> and you have it. >> >> >>> Thx >>> T. >>> >>> >>> >> >> >> -- >> Best regards, >> Igor Stasenko. >> -- View this message in context: http://forum.world.st/Annotating-classes-tp4707854p4708033.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 13, 2013

Re: [Pharo-dev] Workspace Moprh Bug with image 30389

by kilon

Thank you for the fix, latest image worked for me without any issues. Fernando Olivero-3 wrote > Sure! > > It was my original intent for the design, thanks for pointing that out. > > The 11586 issue includes the fix and refactoring. > > Fernando > > On Thu, Sep 12, 2013 at 1:30 PM, Torsten Bergmann < > astares@ > > wrote: >> Hi Fernando, >> >> Now I see #initializeTranslucentPatterns is there. >> >> BUT: I expected it ON THE CLASS SIDE since usually initializing class >> variables is done >> with class side methods. This is my opinion also a better style of >> coding in >> Smalltalk. >> >> For instance if one resets a class variable in the browser: >> >> TranslucentPatterns := nil. >> >> or sets it to other values for experiments one can easily reinitialize by >> sending a >> class side message. >> >> FormCanvas initializeTranslucentPatterns >> >> No need to create instances (which may be hard to construct in some >> cases). >> >> Would you mind moving it to the class side? >> >> Thx >> T. >> >> >>> I found the bug! it is that FormCanvas>>translucentMaskFor: alphaValue >>> depth: d, should use the accessor ! >>> >>> Maybe when my settings our initialised the >>> FormCanvas>>translucentPatterns get evaluated... >>> >>> I'll open an ISSUE and submit the code ASAP. >>> >>> >>> >>> >>> On Thu, Sep 12, 2013 at 1:12 PM, Fernando Olivero >>> < > fernando.olivero.mail@ > > wrote: >>> > Hi,this is strange, because everything works just fine for me. >>> > >>> > I'm using Pharo3.0: Latest update: #30391 >>> > >>> > That's ok, the class var is lazy initialized. See >>> > FormCanvas>>translucentPatterns. >>> > >>> > I don't understand which missing method are you referring to, because >>> > FormCanvas class>>initializeTranslucentPatterns is there. >>> > >>> > Are you using #30391 ? >>> > >>> > Fernando >>> > >>> > >>> > On Thu, Sep 12, 2013 at 1:05 PM, Marcus Denker < > marcus.denker@ > > wrote: >>> >> >>> >> On Sep 12, 2013, at 12:59 PM, Torsten Bergmann < > astares@ > > wrote: >>> >> >>> >>> Marcus wrote: >>> >>>> This should be fixed in 3.0 390â¦. at least I can't reproduce it >>> anymore. >>> >>> >>> >>> Hi Marcus, >>> >>> >>> >>> No its not. I tried in the latest 3.0 image from today. To make sure >>> I cleanly downloaded a fresh >>> >>> Pharo3.0 Latest update: #30391 and still can reproduce the problem. >>> >>> One has to do some moving on the Workspace. >>> >>> >>> >>> If you look you will into an updated image you will also see that >>> still class var >>> >>> "TranslucentPatterns" in FormCanvas is uninitialized and class side >>> methods on FormCanvas for >>> >>> initialization are missing. So the problem still persists ... >>> >> >>> >> This is strange. now I can reproduce it, but when I tested it before >>> I could not. >>> >> >>> >> Marcus >>> -- View this message in context: http://forum.world.st/Workspace-Moprh-Bug-with-image-30389-tp4707822p470802… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 13, 2013

Re: [Pharo-dev] Naming of Global Session

by StÃ©phane Ducasse

so could you do another iteration on it. Stef On Sep 13, 2013, at 1:51 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > Even more, it feels like we introducing another global (so users can write 'Session current' , but why not just 'Session' then?) and so a step backwards as to me. > Because we trying to get rid of all those Display, World, InputSensor , ActiveHande etc globals for years. > > And last thing: there should be only one way to get current session object. now there's two: > Smalltalk session > and > Session current > > and so, users now will inevitably raise the question: what is the right 'true' API for accessing it? > and inevitably we will have two fighting camps, if we leave this thing in image and be used in various projects. > > > > > On 13 September 2013 01:33, Igor Stasenko <siguctua(a)gmail.com> wrote: > +1 too. > Session is a bad name for a class. > More than that, the people who introduced it, > didn't care about: > - removing unused session ivar from SmalltalkImage class > - that putting #reset in Session class side, means exposing resetting mechanism to > public, instead of keeping it private (and it is quite important to keep it private, > because session should be reset once and only once and only in single , fully controllable place) > > from that perspective, i'd prefer using 'session' ivar in SmalltalkImage instead of > 'current' in Session. > > > > > On 12 September 2013 15:13, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > +1 > > Very abstract names are fine when you have namespaces, otherwise I rather chose more specific names. > > Regards! > > Esteban A. Maringolo > > > 2013/9/12 Torsten Bergmann <astares(a)gmx.de> > In Pharo 3.0 there is a new class "Session" - to represent the current smalltalk > session. Using the term "Session" is very abstract. > > IMHO I would rather like to see it named more specific like "ImageSession", > "PharoSession" or "SmalltalkSession" before it get used too much. > > Any comments? > T. > > > > > > > -- > Best regards, > Igor Stasenko. > > > > -- > Best regards, > Igor Stasenko.

Sept. 13, 2013