Hi everybody,
I'm currently trying to parse a Delphi project into an .mse model so
that I can import it into Moose.
So far I have found "Petit Delphi":
http://ss3.gemstone.com/ss/PetitDelphi.html/Overview
I managed to add the Monticello Repository and I can now see the
"PPDelphiAssemblyParser" and "PPDelpiLexicon" when I open the Tools ->
PetitParser GUI.
But now I'm a bit stuck - how can I create an .mse file out of the
Delphi files on my disk now?
It seems now that I have the parser I don't know how to use it...
P.S.: the whole Smalltalk and Pharo environment is totally new to me,
so please forgive the beginner questions :-)
Thank you very much and best regards,
Torben
Status: New
Owner: tu...(a)tudorgirba.com
Labels: Type-Enhancement Priority-Medium Component-Finder Milestone-4.7
New issue 844 by tu...(a)tudorgirba.com: Moose Finder should let one browse
the implementing method of a navigation item
http://code.google.com/p/moose-technology/issues/detail?id=844
When browsing one entity, the first tab shows the navigation items from
this entity. Especially for newbies it is important to see how these
navigation methods are implemented.
Thus, the contextual menu should offer the possibility to browse the
corresponding methods.
For example, when browsing a class, selecting the invoked methods should
offer a menu item that opens a browser on FAMIXType>>invokedMethods.
Hello,
How to we add horizontal and vertical scroll bars to a Roassal
visualization. I browsed through some examples but could not find one with
these.
tx.
usman
Hi all,
I'd like to customize lines with arrows a little bit more than seems to be
possible out of the box at the moment and am looking for some pointers.
I have attached a screenshot to explain what I'd like to achieve.
I'd like to be able to:
1. Define a certain distance from the arrows beginning and end to the
objects they are attached to - so they are not directly 'glued' to the
objects.
2. Make lines wider, without just affecting the width of the line (and
in the same extend the line the arrow is made up), but instead it should
scale to nice looking arrows.
3. To place lines besides each other from and to the same object.
Are some of these points already possible but I missed them?
How would I best go on about modifying, extending Roassal to allow for edge
styling in this way?
Cheers,
Dennis
Just one more thing that has been playing on my mind. It is really a
nice feature that the parent element grows when the child is moved past
its boundary, but would be more good if it also shrank when the child
element is moved back towards center.
cheers ben
Guillermo wrote:
>Maybe you can use a -completely separate- pre-parser? :)
>
>It takes the input with the pre processor directives, and answers a new
>processed string which the original parser will handle?.
Yes, I guess so. I'm fighting a bit with PetitParser, wondering if the traditional
style of building parsers wouldn't be faster. But that might be just about trying
something new. I like the tests, the separate lexicon, syntax and semantics
subclassing not so much better than preprocessing, scanning, parsing.
I definitely don't like having 80 productions in a class (growing to 300, not
sure how to grow over the max nr of instVars ). Is there an array or dictionary
based PPCompositeParser?
Stephan
I have been looking at the ROExample "Nesting" examples and expanded
#nesting2 with another level as shown in the code below, such that there
is the outer view, middle "#1" nodes and inner "#2" nodes. However the
initial state of this has much of the middle node1 and inner node2 nodes
overlapping.
How can these be made for the circle layout to leave spacing between the
middle node1 nodes?
cheers -ben
--------------------
| view nodes1 |
view := ROView new.
view add: (ROElement sprite addAll: (nodes1 := ROElement spritesOn:
(1 to: 10))).
nodes1 do: [:n | n addShape: ROLabel].
nodes1 do:
[ :node1 |
( (node1 model) *100+1 to: (node1 model)*100+5 ) do:
[ :x |
node1 add: ( (ROElement spriteOn: x) addShape: ROLabel).
].
ROGridLayout on: node1 elements.
].
ROCircleLayout on: nodes1.
view openInWindow.