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
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 :)
Status: New
Owner: ----
Labels: Type-Enhancement Priority-Medium
New issue 664 by jannik.l...(a)gmail.com: MooseMenu - export GML graph
http://code.google.com/p/moose-technology/issues/detail?id=664
It should be cool to specify the place of the new file.
For now, it is saved just near the image.
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 661 by jannik.l...(a)gmail.com: browse package blueprint: DNU
http://code.google.com/p/moose-technology/issues/detail?id=661
#menuItems: does not exist in Mondrian anymore. (maybe a deprecated would
have been good?) What's the replacement?
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.
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.)
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 655 by cy.delau...(a)gmail.com: export a moose model raise an error
http://code.google.com/p/moose-technology/issues/detail?id=655
Try to import a smalltalk model in moose. Right click on the model
and 'export to mse' . at the end of the export you will get:
MessageNotUnderstood: receiver of "sender" is nil
I think it is related this issue :
http://code.google.com/p/moose-technology/issues/detail?id=635
At the end of the export there is a notification signaling that the export
succeed.
The new way announcements are dealing now with exception signals lead to
those kind of behavior
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
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)))