Strange What steps did you follow. You take rc dev Moose ConfigurationOfMoose loadDefault and this is it. On Dec 23, 2009, at 10:21 AM, Norbert Hartl wrote:

Yes, but there are many tools advertised on http://moose.unibe.ch/ tools , which is cool. But if you load Moose, you have only a very few of them. This is not a problem per ser, but the website does not say anything about that. Alexandre On 23 Dec 2009, at 10:45, Stéphane Ducasse wrote: -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

On 23.12.2009, at 12:56, Simon Denier wrote: I encounter the problem in a slightly different manner. I don't know what tools I want to use, yet. So I would go and play with all of them and then I would decide which to use in the long run. It would be easy to decide where to start if there would be any matrix that shows what can be used where. It is not too difficult to create this but I thought I ask just in case it exists anywhere. I would like to use moose in pharo because I'm familiar with squeak and pharo. VW I just know little but it seems it's my only choice at this time. Maybe I have to move to windows even to get the most out of it which I like to avoid Thanks, Norbert

Hi Norbert, When you say that you want to use Moose, what exactly is your goal? Do you have a particular system that you want to analyze? If yes, in what language is it written in? Cheers, Doru On 24 Dec 2009, at 13:14, Stéphane Ducasse wrote: -- www.tudorgirba.com "Problem solving efficiency grows with the abstractness level of problem understanding."

Hi Tudor, On 24.12.2009, at 15:45, Tudor Girba wrote: at the moment I'm researching and collecting tools for code analysis. After that I need to toy around with all of them to get the overall picture of what can be shown by using those tools. I like to analyze the software of the company I'm working for. The software is written in javascript and there aren't any tools I know to analyze that. I talked to Alexandre about that and I think you were on CC. Anyway so far I wrote a small utility with rhino that does an XML export of the javascript AST. And Alexandre started to write an moose importer for that. If that does work I like to see results of different moose tools hence the thread. Norbert

Hi, It would be great to have JavaScript support. If you can control the export format, it would be even nicer if you would export in MSE. For the actual reified model, is there anything missing in FAMIX? Regarding the Moose tools, the situation will be significantly clearer on the website in the neat future. In the meantime, here is a list: Pharo • Fame • Glamour • Mondrian • C Analyzer • Enriched DSM • Moose Finder • Moose JEE • SmallDude VW • Yellow Submarine • Softwarenaut • Code City • DynaMoose • Chronia • Evolution Radar • Hapax • Maispion • Software Cartographer • Basil • Edsm • EyeSee • Package DNA • Metanool • Mondrian • Moose Finder • SmallDude • Meta I see that Pastell does not have an explicit license. Perhaps this should be clarified. Cheers, Doru On 25 Dec 2009, at 15:44, Alexandre Bergel wrote: -- www.tudorgirba.com "To lead is not to demand things, it is to make them happen."