Hi,
In the latest version from jenkins the MoosePanel in not very usable
because PPTextHighlighter is missing from the image,
and it's still used in FAMIXJavaSourceLanguage and MooseMSEFilesExplorer.
I saw it was removes in the latest version of PetitGui.
Cheers,
Andrei
Status: New
Owner: ----
CC: anquetil...(a)gmail.com
Labels: Type-Enhancement Priority-Medium Component-VerveineJ Milestone-4.7
New issue 880 by andreho...(a)gmail.com: Improving VerveineJ stub
invocations/methods
http://code.google.com/p/moose-technology/issues/detail?id=880
When creating models without classpath, invocations/methods (where the
biding are not found) are created in the format:
anInvocation(???)
This is the case even if the real invocation in source code contains
parameters such as:
anInvocation(a, b)
It would be good maintain the information with respect to the number of
parameters in such invocation/method, and then export the #signature with
something like:
anInvocation(?, ?)
Like that we can at least count the number of parameters.
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-Famix
New issue 909 by anquetil...(a)gmail.com:
FAMIXNamedEntity>>receivingInvocations ?!?
http://code.google.com/p/moose-technology/issues/detail?id=909
Why is there a receivingInvocations attribute in FAMIXNamedEntity ?
Is that a remnant of MooseCook ?
Status: New
Owner: ----
CC: anquetil...(a)gmail.com
Labels: Type-Defect Priority-Medium Component-VerveineJ
New issue 838 by tudor.gi...(a)gmail.com: VerveineJ does not export
non-javadoc comments
http://code.google.com/p/moose-technology/issues/detail?id=838
VerveineJ exports javadoc comments for both types and methods.
However, it does not export line comments like:
//This is also a relevant comment