I would like to release a Moose 4.5 sometime next week. There are several fixes that came in Moose after 4.4, and it would be a pity to wait to integrate them.
I would still like to get the tests working on the server, but I do not know how. Can anyone take a look?
"Every thing has its own flow."
I now got the following error when parsing a proprietary piece of code:
Exception in thread "main" ch.akuhn.fame.internal.RepositoryVisitor$UnknownElementError: Unknown element: null found via description: FAMIX.ParameterizedType.arguments
I did not know how to isolate this, but it seems to me that the problem is somehow related to FAMIX. Am I right?
"In a world where everything is moving ever faster,
one might have better chances to win by moving slower."
could be interesting in the future
Begin forwarded message:
> From: Johan Brichau <johan(a)inceptive.be>
> Date: June 8, 2011 7:08:52 PM GMT+02:00
> To: Pharo-project(a)lists.gforge.inria.fr
> Subject: Re: [Pharo-project] Report generation? (I need an update)
> Reply-To: Pharo-project(a)lists.gforge.inria.fr
> On 08 Jun 2011, at 17:37, Esteban Lorenzano wrote:
>> So... my question:
>> what do you use to generate reports to clients?
>> if pdf generation... which strategy?
> We use Jasper reports: www.jasperforge.org
> It's a feature-rich library for generation of any report to about any format you can think of, and it's open source.
> The downside is: it is a Java library but we use http communication between our Seaside app and the jasper application.
> In the future, I hope to get my own Javaconnect library (working in Visualworks) rolling completely in Pharo to have native communication from Pharo to Java.
> In the meantime, you might try JNIPort since that one has Pharo version already.
> We can try to develop everything in Smalltalk but we will fail to keep up.
Hi all, I'm working with Java code using Verveine as the parser and Moose
Currently I'm having some problems, and I want to debug them to collaborate
with the Moose project. But I'm stuck trying to load the latest version of
I used the instructions from
http://www.themoosebook.org/book/internals/development/load but as some
people commented previously in the list I got a dependency error with Pharo
What is the best way to load the latest version of Moose? Can I update the
image from the Moose 4.4 one-click installation? I have to try with the
Pharo dev version?
PS: The problems that I'm trying to resolve are:
- DNUs with the FAMIX model (from the previous comments on the list it seems
that some methods needs to be implemented to work with the FAMIX model
generated from Java).
- When working with a large FAMIX model, Moose crashes (I'm working with
MacOSX Leopard 10.5.8, and the one-click Moose 4.4 download). I loaded a
medium size Java app, the MSE loads fine, but when I click in the "All
famixaccesses" of the Moose Panel the VM crashes.
I learned something today. While talking about the maximum number of instance variabes I always thought it is a limit per class. But now I know it is a limit on an object. As I reached 230 instance variables I started to split the parser into two. But now I reached the limit and cannot add instance variables.
I need some ideas about how to structure the parser. I think it will be too hard to find parts of the grammar that are distinct so it would be possible to separate them into different classes. Another way would be to access some of the parser via method calls instead of accessing the instVar parsers.
So does anybody has some experience in how to structure parsers?
Sounds interesting. I did not see that. Where was it announced?
On 7 Jun 2011, at 23:38, Stéphane Ducasse wrote:
> did you see what we did with igor today?
> we improve the start up so that you can get a much better infrastructure to script image and do not get problem with ui none present?
> On Jun 7, 2011, at 10:43 PM, Alexandre Bergel wrote:
>> I had a look at the failed tests. Many of them are due to what Doru pointed out with opening graphical user interface in a headless mode. Really bad.
>> • Moose.Tests.Core.MooseFinderForSimpleClassesTest.testMenuEntriesForAllClasses
>> • Famix.Tests.Java.VerveineJMooseFinderTest.testMenuEntriesForClasses
>> • Moose.Tests.Core.MooseFinderForSimpleNamespacesTest.testMenuEntriesForNamespaces
>> • Moose.Tests.Core.MooseFinderForSimplePackagesTest.testMenuEntriesForPackages
>> • Moose.Tests.Core.MooseFinderForSimpleClassesTest.testMenuEntriesForClasses
>> • Moose.Tests.Core.MooseFinderForSimpleClassesTest.testMenuEntriesForMethods
>> • Moose.Tests.Core.MooseTaskTest.testRunWithProfiler
>> On 7 Jun 2011, at 16:21, admin(a)moosetechnology.org wrote:
>>> See <http://hudson.moosetechnology.org/job/moose-latest-dev/415/>
>> Alexandre Bergel http://www.bergel.eu
All of them, except for the Glamour.Tests.Morphic.GLMFinderMorphicTest.testDefaultFixedSizePanes one are due to the GUI problems in headless mode.
I do not know what can be done about it.
On 7 Jun 2011, at 22:43, Alexandre Bergel wrote:
> I had a look at the failed tests. Many of them are due to what Doru pointed out with opening graphical user interface in a headless mode. Really bad.
> • Moose.Tests.Core.MooseFinderForSimpleClassesTest.testMenuEntriesForAllClasses
> • Famix.Tests.Java.VerveineJMooseFinderTest.testMenuEntriesForClasses
> • Moose.Tests.Core.MooseFinderForSimpleNamespacesTest.testMenuEntriesForNamespaces
> • Moose.Tests.Core.MooseFinderForSimplePackagesTest.testMenuEntriesForPackages
> • Moose.Tests.Core.MooseFinderForSimpleClassesTest.testMenuEntriesForClasses
> • Moose.Tests.Core.MooseFinderForSimpleClassesTest.testMenuEntriesForMethods
> • Moose.Tests.Core.MooseTaskTest.testRunWithProfiler
> On 7 Jun 2011, at 16:21, admin(a)moosetechnology.org wrote:
>> See <http://hudson.moosetechnology.org/job/moose-latest-dev/415/>
> Alexandre Bergel http://www.bergel.eu
Cool stuff in it:
I will work soon on adding a query engine to Mondrian. Quickly finding a node is a graph is important.
Alexandre Bergel http://www.bergel.eu