Moose-dev February 2011

moose-dev@list.inf.unibe.ch

23 participants
136 discussions

Issue 499 in moose-technology: Port & transmission in Mondrian

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Mondrian New issue 499 by alexandr...(a)gmail.com: Port & transmission in Mondrian http://code.google.com/p/moose-technology/issues/detail?id=499 Hi Alex, -=-=-=-=-= Previous discussion: What we did in Glamour was to attach to each Presentation a kind of default interaction. In your example, I would make #mouseEnter, #mouseClick ... default ports that are populated when the corresponding interactions happen on a graph element. Then of course, these ports will belong to graph elements. Like this transmissions are created between the ports of a graph element. Perhaps there will also be a need to identify graph elements by name so that you can refer to them from outside the context of a script. -=-=-=-=-= Previous discussion: Why not having ports that belong to an interaction instead? Consider the following script: view nodes: (1 to: 1000). Figure selection will imply a transmission between the root and each of these nodes. It could be a single transmission between 'root interaction' and the unique interaction of the nodes? -=-=-=-=-= Doru answer: At least two reasons. First, the ports are not just for transmitting information, but ports also allow you to store arbitrary values that model the graph element, and thus you can model the state of a visualization (including side-effects). Second, using ports you will be able to let the shape populate ports by default without writing any explicit interaction (only write transmission when you want to deal with them). Now, about we can be smart about transmissions and do what we do for shapes: we share the object between multiple graph elements. For this, we will just need a lookup of the origins instead of hardcoding them. Actually in Glamour, we have: GLMTransmission>>originatesAt: aPort and thus, you can have a smart transmission that performs a more complex check by checking if the port is part of any elements from a collection. Like this you will have only one the transmission object. You could write: view nodes: #(1 2 3) labeled: #interestingNodes. view nodes: #(5 6 7) labeled: #otherNodes. view transmitTo: #otherNodes fromAny: #interestingNodes port: #selection. Cheers, Doru

12 years, 11 months

Re: Issue 114 in moose-technology: Resizable panes in Finder

by moose-technology＠googlecode.com

Updates: Labels: -Milestone-4.2 Milestone-4.3 Comment #6 on issue 114 by tudor.gi...(a)gmail.com: Resizable panes in Finder http://code.google.com/p/moose-technology/issues/detail?id=114 The basic structure is in place. There are still a couple of things to do: - include the changes to GeneralScrollPane - solve the small scrolling animation problem

13 years, 1 month

Verveine-PHP

by Cyrille Delaunay

Hello, With nicolas we started to have a look at the eclipse-php-parser (provide with PDT), to export a famix-mse file from a PHP project. We already started to build an eclipse plugin that does some work: => We create an AST for each php file of the project => Then we have a visitor on this ast, and we are therfore able to make a specific action for each kind of node visited => For now, we just export some FAMIXNamespace, FAMIXClass, FAMIXMethods. So what's left is to implement each visit-method to extract informations for each node visited. For that we will have to know a bit more PHP :) Maybe the metamodel will have to be extended to take into account some PHP-specific elements, I don't know. If you want to have a look, sources are available via svn at: https://scm.gforge.inria.fr/svn/lse/Projects/Verveine Vervaine provide the extractor (not yet finished) for Java ans this one for PHP. Both are using a common mechanism to generate famix entities and extract them to mse. I will be on holidays until august and will probably no longer work on it until august. So if you want to have a look (and have the courage to install eclipse to read java code:)), have some suggestions, want to implement something, feel free to participate :)

13 years, 1 month

Issue 542 in moose-technology: Completion in Glamour text presentation for Smalltalk

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Glamour Milestone-4.4 New issue 542 by tudor.gi...(a)gmail.com: Completion in Glamour text presentation for Smalltalk http://code.google.com/p/moose-technology/issues/detail?id=542 The Glamour TextPresentation for Smalltalk should offer completion as well.

13 years, 3 months

Re: Issue 106 in moose-technology: Disable the default Smalltalk shortcuts from the Text Morphic widget in Glamour

by moose-technology＠googlecode.com

Updates: Labels: -Milestone-4.2 Milestone-4.4 Comment #5 on issue 106 by tudor.gi...(a)gmail.com: Disable the default Smalltalk shortcuts from the Text Morphic widget in Glamour http://code.google.com/p/moose-technology/issues/detail?id=106 (No comment was entered for this change.)

13 years, 3 months

Issue 536 in moose-technology: inFusion should export parentScope instead of container in Function

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: georgega...(a)gmail.com Labels: Type-Defect Priority-Medium Component-ExternalTools New issue 536 by tudor.gi...(a)gmail.com: inFusion should export parentScope instead of container in Function http://code.google.com/p/moose-technology/issues/detail?id=536 currently it exports container, but it should be parentScope

13 years, 3 months

Issue 537 in moose-technology: inFusion should export explicit sourceAnchor for Function

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: georgega...(a)gmail.com Labels: Type-Defect Priority-Medium Component-ExternalTools New issue 537 by tudor.gi...(a)gmail.com: inFusion should export explicit sourceAnchor for Function http://code.google.com/p/moose-technology/issues/detail?id=537 Currently, it exports sourceAnchor as a string like this: (FAMIX.Function (sourceAnchor 'path') ...) It should be (FAMIX.FileAnchor (id: 1) ...) (FAMIX.Function (sourceAnchor (ref: 1)))

13 years, 3 months

Issue 544 in moose-technology: inFusion should point the C++ source text to the implementation, not definition

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: georgega...(a)gmail.com Labels: Type-Defect Priority-Medium Component-ExternalTools New issue 544 by tudor.gi...(a)gmail.com: inFusion should point the C++ source text to the implementation, not definition http://code.google.com/p/moose-technology/issues/detail?id=544 Currently, the source anchor for a c/c++ class or methods points to the definition in the header. It should point to the implementation from the c/cpp file.

13 years, 3 months

Re: Issue 464 in moose-technology: Actions that open new browsers should go through Renderer

by moose-technology＠googlecode.com

Updates: Labels: -Milestone-4.2 Comment #1 on issue 464 by tudor.gi...(a)gmail.com: Actions that open new browsers should go through Renderer http://code.google.com/p/moose-technology/issues/detail?id=464 (No comment was entered for this change.)

13 years, 4 months

Re: Issue 273 in moose-technology: The Morphic Glamour should update the selectedText in a TextPresentation

by moose-technology＠googlecode.com

Updates: Labels: -Milestone-4.2 Comment #2 on issue 273 by tudor.gi...(a)gmail.com: The Morphic Glamour should update the selectedText in a TextPresentation http://code.google.com/p/moose-technology/issues/detail?id=273 (No comment was entered for this change.)

13 years, 5 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev February 2011