Hello,
We discussed with Anne and Mathieu about the project moose on the web and
how would we search for an entity in a model by interacting with the moose
server implementing REST API.
- The first API request to the server is allModels and then the server
responds with the list of the moose models (JSON data). Once the user has
got a list of model, how can one choose the model one wants to explore. One
can select a moose model based on: i) its name, ii) its position in the
collection returned by the server (1 for first, 2 for second, etc.) or iii)
its mooseID. The name of a moose model is not unique so it does not help
choosing the correct unique model. For the time, we choose the position in
the collection returned by the server but if we have huge list, the
position is difficult to remember. mooseID does not have semantic meaning.
A meaningful solution would be to make all moose models have a unique name.
What do you think?
- Generalizing the search to all the entities in the model, how do you
select an Entity with its name in the model knowing that the names are not
unique (there can be two "add:" in a model). Scoping information can help
and we have mooseName that concatenates the name with the scoping
information of an entity. So a method named get() in java with class and
package information appended looks like "java.utils::Scanner.get()". Is the
name uniqueness guaranteed with this mechanism?
We had a discussion regarding the interaction with the server, I'll send a
separate mail for it.
Usman
Hi Juraj,
I just saw that the zoom-in, zoom-out and export are part of all visualizations in Moose (like blueprint of system complexity). They should not be there. The reason is that these visualizations are meant to be embedded in all sorts of places, and typically the utility actions like zooming and exporting are part of the surrounding browser. The visualizations should display the data and offer data interaction only.
Please remove these.
Cheers,
Doru
--
www.tudorgirba.com
"Don't give to get. Just give."
Hi!
Matias has worked on implementing VisualID (http://scribblethink.org/Work/VisualIDs/visualids.html) in Roassal.
This is an idea Doru and I have had for a long time.
Where to find it:
MCHttpRepository
location: 'http://smalltalkhub.com/mc/mnip91/Roassal-VisualID/main'
user: ''
password: ''
Example:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| view rawView elements |
rawView := ROView new.
view := ROMondrianViewBuilder view: rawView.
elements := ROElement spritesOn: (1 to: 11).
elements do: [:elem|
elem addShape: (ROVisualID new). ].
rawView addAll: elements.
rawView addAll: (ROEdge linesFor: (Array with: elements first ->
elements second with: elements second -> elements fifth with: elements second ->
elements third )).
ROTreeLayout on: elements.
view noLayout.
view open
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-Famix
New issue 939 by anquetil...(a)gmail.com: FamixEntity annotation not coherent
with FAMIXEntity implementation
http://code.google.com/p/moose-technology/issues/detail?id=939
FAMIXEntity class>>annotation
<MSEClass: #Entity super: #Object>
i.e. FamixEntity inherits from Object
but FAMIXEntity has for superclass MooseEntity
I guess annotation should be changed
--
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
There is a problem with jenkins infrastructure because of some network
problem. That means we cannot connect to the slaves and launch them. For
testing purposes, I added another slave to Moose jenkins and I think we
should keep it for redundancy purposes. I'll see with Christophe when its
resolved so that the jobs are relaunched.
Usman
Hi!
I think I have just ported all the staff into Roassal. So, I think it is
ready to remove Mondrian. If something is missing, please let me know.
What do you suggest for the next step? Do you want to remove Mondrian from
Moose 4.8?
Cheers,
Jura
Status: New
Owner: ----
CC: alexandr...(a)gmail.com
Labels: Type-Defect Priority-Medium Component-Roassal Component-Glamour
New issue 870 by tu...(a)tudorgirba.com: ROFocusView focuses on the wrong spot
http://code.google.com/p/moose-technology/issues/detail?id=870
Open a Roassal Easel and paste this:
| node |
node := view node: #a.
ROFocusView new on: node view: view raw.
The node is selected somewhere at the bottom. The reason is likely to be
that the canvas has a static size, instead of adapting by default to the
size of the surrounding pane
Hi,
I started to integrate Rubric in Glamour.
At the moment, only the basic text widget is integrated, and it is integrated with a different factory method (rubricText instead of text). The longer term idea is to replace the rendering of the existing TextPresentation. Once TxText will be adopted we will move again.
Furthermore, the interface is basic, but given that Rubric offers a couple of nice features (such as decorations and wrapping), we should adopt that as well in the interface.
An example:
wrapper := GLMCompositePresentation new.
wrapper with: [ :w |
w show: [ :a | a rubricText ] ].
wrapper openOn: 'text'
Cheers,
Doru
--
www.tudorgirba.com
"Things happen when they happen,
not when you talk about them happening."
Hmm,
What combination of configurations, images , vm, plugins is supposed to work?
cairo install through port is broken on 10.6.8 with xcode 4.0.2, glib2 won't compile.
I'm not very happy with package management on mac, btw. Brew interferes with
port...
Stephan
Hi,
Andrei joined Camillo and extended a bit the ZeroConf infrastructure to make it easy for other projects to generate install scripts.
As a consequence, we now have:
http://get.moosetechnology.org
The Moose-specific customization code can be found in the Moose-Development-Tools package from:
http://www.smalltalkhub.com/mc/Moose/Moose/main
The scripts are generated via the Pharo command line like:
Pharo/pharo-ui moose-latest-dev-4.8.image moosezeroconf
Cheers,
Doru
--
www.tudorgirba.com
"No matter how many recipes we know, we still value a chef."