Hello,
Tomorrow, there is a pharo sprint in Lille. We, people working on Moose in
Lille, thought of doing a Moose sprint/dojo and the purpose is to port
Moose on Pharo 2.0.
Is there someone who has tried to make Moose work on Pharo 2.0? If so, do
we have a list of bugs for Moose 4.8 that we can kill tomorrow?
Usman
Hi Mariano,
I just stumbled across the paper, and it looks really nice. I definitely would like to have it used in Moose. I actually started to prototype a cache based on Fuel, but obviously Marea is way better.
In the paper, you mention that the use in Moose is to be able to handle multiple models. That is a use case, but I think it's not a critical one. A more interesting use case is the one in which we want to store an AST alongside FAMIX. There are two challenges here:
- The size of AST data is really prohibitive for being loaded in memory all the time
- For the AST to be most valuable, we need to be able to link parts of the model to the corresponding AST nodes. See the picture in the attachment for an example: an invocation between methodA and methodB would have a corresponding message send node in the AST of methodA.
If I understand Marea right, we could consider as roots all the AST root nodes, and essentially have them all swapped until we get to use one for some detailed analysis such as whether the invocation happens inside a loop or not. Is that correct?
Cheers,
Doru
--
www.tudorgirba.com
"It's not what we do that matters most, it's how we do it."
Hi,
is it possible to analyse Eclipse source code with VerveineJ? I always
got various OutOfMemoryException
Thank you
--
Damien Cassou
http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without
losing enthusiasm."
Winston Churchill
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
Status: New
Owner: andreho...(a)gmail.com
Labels: Type-Enhancement Priority-Medium Component-EyeSee Milestone-4.8
New issue 908 by andreho...(a)gmail.com: Kiviat should have popups
http://code.google.com/p/moose-technology/issues/detail?id=908
Kiviat diagrams should have popups which is not possible now.