Hi!
I am wondering whether a context can be attached to a GTInspector.
For example, I would like to keep some properties about the roassal camera and the position of all the elements to have smooth animation when updating.
Maybe the class GTInspector or GLMCompositePresentation may be a variable attributes with a dictionary in it?
Does this make sense?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
I added a new Source anchor, similar to FileAnchor but with the absolute
position instead of the line+column
called it IndexedFileAnchor
Common parts with old FileAnchor (not renamed to minimize the impact)
have been put in a superclass of both:
AbstractFileAnchor
famix tests are green
nicolas
Just wondering now that Moose 5 is out :-)
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi!
On my quest to inject all the features of the GraphBuilder into Mondrian, I have just improved Mondrian with the (i) the #notUseInLayout option when building edges and (ii) the bezier line that follow a path.
It sounds like very technical, but this effort is to make the Mondrian and the edge/layout builders more expressive.
Here is a small example:
-=-=-=-=-=-=-=-=-=-=-=-=
classes := RTShape withAllSubclasses, TRShape withAllSubclasses.
b := RTMondrian new.
b shape circle.
b nodes: classes.
b edges connectFrom: #superclass.
b shape bezierLineFollowing: #superclass;
color: (Color blue alpha: 0.2).
b edges notUseInLayout; connectToAll: #dependentClasses.
b normalizer
normalizeSize: #numberOfMethods using: #sqrt;
normalizeColor: #numberOfMethods using: (Array with: Color green with: Color red) using: #sqrt.
b layout cluster.
b build.
-=-=-=-=-=-=-=-=-=-=-=-=
Another example:
-=-=-=-=-=-=-=-=-=-=-=-=
classes := RTObject withAllSubclasses, RTTest withAllSubclasses.
b := RTMondrian new.
b shape circle.
b nodes: classes.
b edges connectFrom: #superclass.
b shape bezierLineFollowing: #superclass;
color: (Color blue alpha: 0.2).
b edges
notUseInLayout;
connectToAll: #dependentClasses.
b normalizer
normalizeSize: #numberOfMethods using: #sqrt;
normalizeColor: #numberOfMethods using: (Array with: Color green with: Color red) using: #sqrt.
b layout cluster.
b build.
^ b
-=-=-=-=-=-=-=-=-=-=-=-=
Doru, on some point we discussed whether it was a good idea to have a clause
#if: [ :fromObject :toObject | … return a boolean … ]
You argued that it was not a good idea and I agree with you. However, I cannot see how to avoid it.
For example, how can I have only edges going from the tests to the base code, and not between classes of the base code?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hello,
I’ve just posted some pictures of the execution of Roassal and Glamour.
More pictures on:
https://www.facebook.com/ObjectProfile/posts/753449881408278
Roassal:
Glamour:
Merry Christmas!
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi Giorgio,
Thanks for the kind words.
Cheers,
Doru
On Wed, Dec 24, 2014 at 1:20 AM, giorgio ferraris <
giorgio.ferraris(a)gmail.com> wrote:
> Hi, Guys,
>
> I'm not (yet) working on Pharo (still VW and some VisualSmalltalk in the
> few time left free from my main job), but I follow what you do (not just
> you but all the community) and I have to admit you (all) work really hard.
> Bergel is doing a fantastic job, and your Moose is very nice, etc.
> But, I really liked the presentation of the GT stuff, I can understand the
> energy you put behind your work.
>
> Great work. I'm happy you are on the ST community and working on the
> language (ST) i like the most. Thanks!
> (Oh, I know you don't like to have Pharo called Smalltalk, but I don't
> like religion's wars, so that is yet smalltalk, for me).
>
> BTW: Happy Holidays to all.
>
> Giorgio
>
> On Wed, Dec 24, 2014 at 12:09 AM, Tudor Girba <tudor(a)tudorgirba.com>
> wrote:
>
>> We are happy to announce Moose 5.0:
>> *http://moosetechnology.org/#install*
>>
>>
>> Description
>> ---
>>
>> This is by far the most extensive Moose release to date. Just take a look
>> at these two trailers.
>> - Spotter: https://vimeo.com/113832673
>> - Inspector: https://vimeo.com/103463364
>>
>> The key highlights are:
>> - It is based on Pharo 3.0.
>> - Roassal2 is a complete reimplementation of the core visual engine of
>> Moose.
>> - Roassal2 replaced Roassal, EyeSee and Graph-ET, and it features many
>> new things including smooth animations, new composeable builders and
>> several new layouts.
>> - All built-in Moose visualizations use Roassal2.
>> - Glamour has been extended with a Pager browser and with Rubric as the
>> main text editor.
>> - GTSpotter is a new tool that makes it possible to find objects fast.
>> - GTInspector saw major usability improvements based on the Pager
>> browser, and it now comes with many object specific extensions.
>> - GTPlayground provides a new way to handle scripts and when combined
>> with GTInspector, it can replace the dedicated easels and editors.
>> - Moose Finder has been extended with the ability of handling in place
>> visualizations.
>> - GTDebugger has been strengthen and was made more robust.
>> - PetitParser has been extended with the notion of context which enables
>> elegant island parsing.
>>
>> 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 5.0 comes for each platform as a separate bundle:
>> - *Moose Suite 5.0 for Mac>http://moosetechnology.org/res/download/
>> moose_suite_5_0-mac.zip
>> <https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_5_0-mac.zip>
>> *
>> <https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_8-mac.zip*>
>> - *Moose Suite 5.0 for Windows>http://moosetechnology.org/res/download/
>> moose_suite_5_0-win.zip
>> <https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_5_0-win.zip>
>> *
>> <https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_8-win.zip*>
>> - *Moose Suite 5.0 for Linux>http://moosetechnology.org/res/download/
>> moose_suite_5_0-linux.zip
>> <https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_5_0-linux.zip>
>> *
>> <https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_8-linux.zi…>
>>
>> The Moose Suite 5.0 can also be loaded in a Pharo 3.0 image either from
>> the Configuration Browser, or by executing the following script:
>>
>> ==Gofer new
>> == smalltalkhubUser: 'Moose' project: 'Moose';
>> == configuration;
>> == loadStable
>>
>>
>> Happy holidays!
>> The Moose team
>>
>
>
--
www.tudorgirba.com
"Every thing has its own flow"
Apparently when I move the moose from the finder elements (classes) to the model item I get
a DNU point:from:
MoprhTreeListManager>>clicked: event inTheCheckboxOf: aTargetMorph
| position |
position := aTargetMorph point: event position from: client.
^ self isCheckList and: [ (aTargetMorph checkClickableZone translateBy: 2 @ 0) containsPoint: position ]
Stef
Hi,
As you know, Pharo Days will take place at the end of January. It is a
great place to learn and exchange ideas about Pharo (and indirectly Moose).
If you plan to attend, please register as soon as possible:
http://pharodays2015.pharo.org
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
