I have a package with classes and I want to get all the subclasses of all the classes in this packages.
How can I do that?
As a general remark: To me the navigation is not there. For example in the visualization we cannot annotate, query, select
connected entities. Even codecrawler was better to select. Now we have some visualisation
but they give the feeling that they are just there because they are cool.
Stef
Really I do not get why roassal does not take advantage of the idea of MalKontrakor.
I cannot imagine that when we work for real with visualzaition we do not want to cut, condense names.
This is the key difference between nice looking visualization and really useful ones.
This tells to me that roassal has never been used to support a real reverse engineering tool.
I will see and may be I will propose to build a specific tools for reverse engineering because right now
the gap is so large.
Stef
Hi
Where are the Mondrian examples?
It was cool when they were accessible from the EaselEditor.
I never understood the motivation to move them out the reach to the user.
Stef
Hi
this is annoying to see the name of the namespace followed by (namespace) and this for all the chain.
especially when we represent packages :)
What was the reason to get the ( )?
In my image I systematically change
printOn: aStream
self belongsTo ifNotNil: [:parent |
parent printOn: aStream.
aStream
nextPut: $:;
nextPut: $: ].
self name ifNotNil: [ aStream nextPutAll: self name ].
aStream nextPutAll: ' (Namespace)'
=>
printOn: aStream
self belongsTo ifNotNil: [:parent |
parent printOn: aStream.
aStream
nextPut: $:;
nextPut: $: ].
self name ifNotNil: [ aStream nextPutAll: self name ].
same for packages.
Stef
Hi
just to let you know that people reported to me (but I cannot find a way to reproduce it) that Moose 4.9 does not restart after a while on windows win XP.
I tried to get some more information but I could not.
May be this is because this is windows XP.
Stef
Hi!
Something important that has been lost from the traditional debugger and GTDebugger, is to see the instance variables and temporary variables in two different panes.
Maybe coloring can be used to tell which variable is a temporary or not.
When I step in / over, maybe you can indicate in bold what are the variables that have been modified. A simple idea that is not there with the standard debugger.
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
