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

Re: [Pharo-dev] Maybe fixed?

by Benjamin

You should: 1) Create an account here: http://bugs.pharo.org/issues/register 2) Log in here: https://pharo.fogbugz.com/ 3) Click on "New Case": https://pharo.fogbugz.com/default.asp?command=new&pg=pgEditBug 4) Keep the newly created case issue id Then to create something you can send to the community, create a slice with the kept issue id (more info here: https://pharo.fogbugz.com/default.asp?W39) If you need more informations, tell us :) Ben On Sep 13, 2013, at 8:49 AM, Friedrich Dominicus <frido(a)q-software-solutions.de> wrote: > I guess I found a bug in Browser>openAsMorphClassEditing > in my Version there was > window > addMorph: self buildMorphicMessageList > fullFrame: ((0.5@0 corner: 1.0@hSepFrac) topOffset: switchHeight). > > I had to change it to: > window > addMorph: self buildMorphicMessageList > fullFrame: ((0.5@0 corner: 1.0@hSepFrac) asLayoutFrame topOffset: switchHeight). > > Otherwise I get an MNU for Rectangle topOffset: > > > I guess I've to figure out on how to send proper patches to this mailing > list. > > Regards > Friedrich >

Sept. 13, 2013

[update 3.0] #30394

by Marcus Denker

30394 ----- 11575 Add a Spec model for DiffMorph https://pharo.fogbugz.com/f/cases/11575 11533 Change testEnsureDeleted into testEnsureDelete https://pharo.fogbugz.com/f/cases/11533 11593 MCMergeOrLoadWarning actions should use #resume: instead of #return https://pharo.fogbugz.com/f/cases/11593 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Widgets-MarcusDenker.241… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Polymorph-Tools-Diff-MarcusDe… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Monticello-MarcusDenker.861.d… http://smalltalkhub.com/mc/Pharo/Pharo30/main/FileSystem-Tests-Core-MarcusD…

Sept. 13, 2013

Maybe fixed?

by Friedrich Dominicus

I guess I found a bug in Browser>openAsMorphClassEditing in my Version there was window addMorph: self buildMorphicMessageList fullFrame: ((0.5@0 corner: 1.0@hSepFrac) topOffset: switchHeight). I had to change it to: window addMorph: self buildMorphicMessageList fullFrame: ((0.5@0 corner: 1.0@hSepFrac) asLayoutFrame topOffset: switchHeight). Otherwise I get an MNU for Rectangle topOffset: I guess I've to figure out on how to send proper patches to this mailing list. Regards Friedrich

Sept. 13, 2013

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

by Ben Coman

Sept. 13, 2013

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

by Sven Van Caekenberghe

Impressive. On 13 Sep 2013, at 07:04, 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] [Esug-list] [ann] moose 4.8

by Alexandre Bergel

Well done!!!! Alexandre On 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" > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 13, 2013

[ann] moose 4.8

by Tudor Girba

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 Esteban A. Maringolo

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(a)gmail.com> > > > > On 12 September 2013 13:56, Torsten Bergmann <astares(a)gmx.de> 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. >

Sept. 13, 2013

Re: [Pharo-dev] How to state up to date with Pharo ?

by Esteban A. Maringolo

Yeap. It certainly does help. Thank you Norbert! Esteban A. Maringolo 2013/9/12 Norbert Hartl <norbert(a)hartl.name> > > Am 11.09.2013 um 14:35 schrieb Esteban A. Maringolo <emaringolo(a)gmail.com > >: > > Is there some guide to do the same in a private environment? > I is... using an HTTP/FTP/Git server as the monticello repo (SmalltalkHub > seems overkill). > > > I wrote this once for turning apache into a monticello repository > > http://norbert.hartl.name/blog/2009/06/08/public-monticello-repository/ > > Maybe it is what you are looking for, > > > Norbert >

Sept. 13, 2013

Re: [Pharo-dev] Naming of Global Session

by Camillo Bruni

Session is a class, not an instance that is a BIG difference. The same goes for VirtualMachine, OSPlatform, OSEnvironment etc. These are all classes, but you only work with their instances: OSPlatform current == Smalltalk os VirtualMachine current == Smalltalk vm OSEnvironment current == Smalltalk os environment and thus, it is quite natural to deduce Session current == Smalltalk session it's all symmetric, not strange objects that have names like classes but are actually instances. On 2013-09-12, at 20:51, 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