Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 932 by alan.mcn...(a)gmail.com: Moose Meta Browser - Comments
Accepted but orange "edited" border not removed
http://code.google.com/p/moose-technology/issues/detail?id=932
Pharo2.0
Latest update: #20594
Moose 4.8 - downloaded about 3 weeks ago
There is a comment panel in the Moose Meta Browser.
Comments can be altered in this panel. When the comment text is altered,
the panel aquires an orange border. This is standard Pharo behaviour.
These changes to the comments can be committed, or accepted in Pharo
terminology, by clicking the tick box in the top right corner. That this
accept function is working correctly has been checked and all is OK.
However, as a feedback to the user, it is expected that after the "accept"
the orange border indicating that the text has been changed would go away.
This is the standard behaviour of accept in, for example, the System
Browser.
However, in this case, the orange border remains until the Comment panel is
replaced by other information.
--
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 933 by alan.mcn...(a)gmail.com: Moose Meta Browser - Scope Map by
scope of Entities
http://code.google.com/p/moose-technology/issues/detail?id=933
Type-Enhancement
Background
----------
The moose Meta Browser has a nice feature that by clicking on the tag shown
against an entity, the list of entities is restricted to those in that tag
or as parent entities.
For example, if within the expanded Moose.Entity tree, the "Dynamix" tag is
selected, and the FAMIX.Entity, Moose.AbstractGroup etc. are hidden, and
only Moose.Entity (as a parent) and Dynamix.Entity (tagged Dynamix) is
shown.
It is also useful that clicking on this tage again reverses this
restriction and all Entities are shown.
Enhancement
-----------
Currently the Map panel shows the Entities and relationships for
eveything. It has no way of focussing in on a sub-set of interest.
It would be useful if the Map reflected these changes in scope. In the
above example, the Map would be re-drawan, but only showing the
Moose.Entity and the set of Entities tagged as Dynamix, and perhaps with
entities with relationships to those tagged to these Dynamix Entities.
Obviously, when the Dynamix tag in the Entity panel is clicked the second
time and restores the full list of Entities, the Map would be re-drawn
again, this time with all Entities and relationships.
--
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 928 by usman.bh...(a)gmail.com: OB browser related code in glamour
http://code.google.com/p/moose-technology/issues/detail?id=928
Glamour provides a browser based on the OBBrowser but I think the latter
one has been removed from Pharo 2.0. The code can be found in
GLMBasicExamples>>startBrowser.
--
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
Hi
So I've been working on the forcebasedlayout for more than a week now,
here are some news.
I've translated the D3 code, and have implemented a new quadtree, the
mondrian one wasn't that compatible.
But, I have a problem, it seems there is no more bug in th code, but it
still doesn't do what is expected, so I read and read th D3 code and
don't find where are my mistakes. I've started to write test, so maybe I
will find something that way. I've made some simplifications but as I do
translate javascript to smalltalk, I can't do exactly the same things,
and ....
Ok... made a new test, before to send this email, and in fact the
problem that I have and that does not appear in javascript is due to the
length of the links.
It seems that in D3, the node position is kinda relative (maybe
something with the window border, or something like that), but in Pharo,
its more 'static', so it needs to be chosen well for each graph.
Still need to be checked, but with a length of 20, in initialize, you
got a good result with Collection.
-----------------
| view rawView |
rawView := ROView new.
view := ROMondrianViewBuilder view: rawView.
"-------------"
"-------------"
ROEaselMorphic new populateMenuOn: view.
view open.
view interaction on: ROMouseEnter do: [ :n |
| nodes |
nodes := view raw elementsFromModels: n element model
allSubclasses.
ROHighlightElements on: nodes ].
view interaction on: ROMouseLeave do: [ :n |
| nodes |
nodes := view raw elementsFromModels: n element model
allSubclasses.
ROUnhighlightElements on: nodes ].
view shape rectangle size: 10.
view nodes: (Collection withAllSubclasses).
view edgesFrom: #superclass.
view layout: ROForceBasedLayout_N.
view applyLayout.
-------------
Enjoy
Mathieu
Yeah
I do apologize, but first I commit a code that I did think wasn't
working, and then do a quick commit, without looking at the self and so.
Do another commit tomorrow, cleaner.
Regards
Mathieu
Hello,
I have to merge user's annotations (added with Metanool) from two different
models (created from sources of the same project at two different time) in
order to keep these annotations in the newly generated one.
Does something exist to do that?
Thanks in advance.
--
*Guillaume Larcheveque*
Status: New
Owner: ----
CC: chisvasi...(a)gmail.com
Labels: Type-Defect Priority-Medium Component-Glamour Milestone-4.8
New issue 929 by tu...(a)tudorgirba.com: Editors break when there is a
compile error
http://code.google.com/p/moose-technology/issues/detail?id=929
Try this:
1. GLMRoassalEditor open
2. Type ","
3. Run => exception (normal)
4. Type "view nodes: #(1 2 3)"
5. Run => nothing happens
--
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