Hi!
Just to share a small use I had of Moose.
I am working on Roassal2. Roassal2 will be largely compatible with Roassal1. I am trying to make GraphET use Roassal2, and I need to know where Roassal is actually used by GraphET. Moose is ideal for this.
I opened the moose panel, imported GraphET and type the following script in a Roassal easel opened on a class group:
-=-=-=-=-=-=-=-=-=-=-=-=
view shape rectangle
if: #isStub fillColor: Color veryVeryLightGray;
if: #isSUnitTestCase borderColor: Color green.
view nodes: classGroup forEach: [ :cls |
view shape rectangle
if: [ :m | (m queryAllOutgoingAssociations atTypeScope select: [:c | c name beginsWith: 'RO' ] ) notEmpty ] fillColor: Color red;
if: [ :m | (m queryAllOutgoingAssociations atTypeScope select: [:c | c name beginsWith: 'RT' ] ) notEmpty ] fillColor: Color blue.
view interaction
popupText: [ :m | ((m queryAllOutgoingAssociations atTypeScope select: [:c | c name beginsWith: 'RO' ]) inject: '' into: [ :s :e | s, ' ', e name ]), String cr, '-----', String cr, m sourceText ];
action: #inspect;
on: ROMouseClick do: [:event | event model browseSource ].
view nodes: cls methods.
view gridLayout.
].
view edgesFrom: #superclass.
view treeLayout
-=-=-=-=-=-=-=-=-=-=-=-=
It gives a pictures as the following one:
large squares are classes
link are inheritance: superclass is above its subclasses
Inner squares are methods
red square are methods of GraphET that reference to Roassal1 classes
blue square are methods that have been migrated to Roassal2.
Gray classes are stub classes
A popup window details what is the reference. E.g.,
This is a popup I get by having the mouse above a method initialize. The reference to Roassal is because of the use of “ROElement”. I can click on the class to open a code browser on it. I can then modify the reference of ROElement to RTElement...
Happy new year!
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi!
Daniel is looking for usage scenarios with GraphET. It would be great to hear about your need.
Currently, we will work on:
- PDF Export using Artefact
- support for legend
- smarter way to put labels on axis
Anything else?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Status: New
Owner: ----
Labels: Type-Defect Priority-High Component-Glamour
New issue 1041 by alexandr...(a)gmail.com: GTInpsector
http://code.google.com/p/moose-technology/issues/detail?id=1041
If nothing is selected, and I press Cmd-o, can the line be used as a
selection instead?
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 1040 by v.blonde...(a)gmail.com: No autocompletion under Moose
Environment
http://code.google.com/p/moose-technology/issues/detail?id=1040
Describe the problem: what do you get? what do you expect?
Under any Moose Image, the shortcut MAJ + SPACE doesn't show the possible
completions in the source editors (Workspace, Nautilus, Debugger...). In
Pharo's latest version, it's working.
I don't know, if it's a issue or if I have to use another shortcut.
By the way, in some images depending of Moose (FAST-Pharo and FAST-Java),
when I write some lines in the source editors the auto-completion isn't
automatically offer (but it's works fine in Moose 5.0)
Additional information: platform, context which may impact the problem
Linux Ubuntu x64
Please fill in the labels with the following information:
* Type-Defect
* Milestone-5.0
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-EyeSee
New issue 690 by andreho...(a)gmail.com: Change the font size of labels in a
chart
http://code.google.com/p/moose-technology/issues/detail?id=690
Change the font size of labels in a chart using #defaultFontSize: is not
working.
Status: New
Owner: ----
CC: andreho...(a)gmail.com
Labels: Type-Defect Priority-Medium Component-EyeSee
New issue 1013 by usman.bh...(a)gmail.com: Eye line diagrams do not allow
changing line width
http://code.google.com/p/moose-technology/issues/detail?id=1013
Changing lineWidth: block in the example lineDiagram2 does not have an
effect on the line width. To reproduce, have a look on this example:
ESExamples new lineDiagram2
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
Yup!
Sam
Adams/Raleigh/IBM
To
01/08/2014 02:03 Moose-related development
PM <moose-dev(a)iam.unibe.ch>
cc
David Ungar/Almaden/IBM@IBMUS
Subject
Re: [Moose-dev] GTInspector
(Document link: David Ungar)
I can hear David Ungar cheering!
That's basically what the Self user interface is like.
Regards,
Sam
Sam S. Adams, CTO - Contextual Computing
IBM Distinguished Engineer, IBM Research
Mobile: 919-696-6064, email: ssadams(a)us.ibm.com
Assistant: Linda R. Morrison. (720) 395-0460 Fax: (845) 491-4318, Tie:
676-0460, linda.r.morrison(a)us.ibm.com
<<Hebrews 11:6, Proverbs 3:5-6, Romans 1:16-17, 1 Corinthians 1:10>>
From: Alexandre Bergel <alexandre.bergel(a)me.com>
To: Moose-related development <moose-dev(a)iam.unibe.ch>
Date: 01/08/2014 04:50 PM
Subject: [Moose-dev] GTInspector
Sent by: moose-dev-bounces(a)iam.unibe.ch
Thanks to the GTInspector, I am in a very good mood today.
The Cmd-o command is so powerful.
Maybe, one day, we will not have code browser anymore, but simply powerful
inspector.
Some small requests:
- If nothing is selected, and I press Cmd-o, can the line be used as a
selection instead?
- can the list of superclasses be reversed when I browse a method?
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-Roassal
New issue 1019 by usman.bh...(a)gmail.com: Roassal shows an error (red
rectangle) when image reopned
http://code.google.com/p/moose-technology/issues/detail?id=1019
Roassal gives an error (the red rectangle) problem when an image is saved
and reopened.
Steps to reproduce:
Do: ROMondrianExample new lines (or open any other Roassal visualization)
save image
quit image
reopen image
You should see a red rectangle in the Roassal window instead of the drawing.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
First of all, thanks much for the delightful Glamour framework!
I'm seeing a layout problem that is happening across a number of browsers
where the bottom panes are rendered larger than the top window's bounds and
are being clipped.
I have worked around this sometimes by adding a no-op presentation with a 0
size as the last row, but I must be missing the better way.
Any clues?
Regards,
Sam
Sam S. Adams, CTO - Contextual Computing
IBM Distinguished Engineer, IBM Research
Mobile: 919-696-6064, email: ssadams(a)us.ibm.com
Assistant: Linda R. Morrison. (720) 395-0460 Fax: (845) 491-4318, Tie:
676-0460, linda.r.morrison(a)us.ibm.com
<<Hebrews 11:6, Proverbs 3:5-6, Romans 1:16-17, 1 Corinthians 1:10>>