Moose-dev June 2013

moose-dev@list.inf.unibe.ch

36 participants
163 discussions

by Stephan Eggermont

Andre Hora wrote: >I see space to investigate the use of a graph database such as http://www.neo4j.org in order to store the model. The >Moose model is "just" a graph. What do you hope to achieve by using a graph database? From my POV it just looks like a very inefficient java based image. 64 bit though. Stephan

11 years, 1 month

Moose on the web - interaction

by Usman Bhatti

Some thoughts on the interaction with a Moose server retained from the discussion with Anne and Vincent (it was also Vincent in my previous mail but i misspelt :-). With the current implementation, one can start by interacting with a model at any level (allClasses, allMethods, etc.) and then narrow his search on an entity or a set of entities. Every entity returns in the results the list of msgs it implements. We are working on how to correctly choose a specific moose entity from the returned collection (see my previous mail). Scoping information is essential to correctly identify/find an entity. So scoping information can be retained by the way user interacts with the server. For example: http://mooseserver/allPackage/first/allClasses/first/allMethod/first But that would mean interaction is restrictive, one has to start with the highest level of container (allPackages in java) and drill down to search for the required entity. Not retained. Nicolas P. suggested to keep a way to search entities by their mooseIDs as well so we'll implement it as well. Specify the number of entities to return. Be able to specify an element by its position in the collection returned. http://mooseserver/allPackage/3/allClasses What do you think? Usman

11 years, 1 month

Question for Roassal (sizing ..) (part two)

by mathieubmddehouck＠mailoo.org

(* I send the other part without finishing it *) Wouldn't it be nice (useful) if a layout could have a legend easily ? I mean automatically making a kind of grid layout representing different nodes and edges, with the possibility of telling what they mean ? Regards Mathieu

11 years, 1 month

Moose on the web - searching for an Entity

by Usman Bhatti

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

11 years, 1 month

no roassal buttons

by Tudor Girba

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."

11 years, 1 month

VisualID: generating icons using any arbitrary object

by Alexandre Bergel

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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

11 years, 1 month

Issue 939 in moose-technology: FamixEntity annotation not coherent with FAMIXEntity implementation

by moose-technology＠googlecode.com

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

11 years, 1 month

problem with jenkins slaves

by Usman Bhatti

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

11 years, 1 month

All the visualisations are ported into Roassal

by Juraj Kubelka

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

11 years, 1 month

Issue 870 in moose-technology: ROFocusView focuses on the wrong spot

by moose-technology＠googlecode.com

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

11 years, 1 month

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev June 2013