Hi,
I've started to play around with moose a bit. The tools page on the moose site has quite impressive tools to offer. But as soon as I took a pharo image and loaded moose into it I recognized that it is (again) not as easy as I hoped.
For a lot of the tools I don't meet the smalltalk dialect requirements and/or I don't meet the operating system requirements. So, is there a matrix where I can see which of the tools are usable in which dialect or operating system?
Thanks,
Norbert
Hi Norbert,
You made a good point. Indeed, the situation is not clear.
Alexandre
On 23 Dec 2009, at 10:21, Norbert Hartl wrote:
Hi,
I've started to play around with moose a bit. The tools page on the moose site has quite impressive tools to offer. But as soon as I took a pharo image and loaded moose into it I recognized that it is (again) not as easy as I hoped.
For a lot of the tools I don't meet the smalltalk dialect requirements and/or I don't meet the operating system requirements. So, is there a matrix where I can see which of the tools are usable in which dialect or operating system?
Thanks,
Norbert _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Sorry guys but this kind of remarks are not constructiv.
From what I read how can I take ***any*** actions to improve?
Stef
On Dec 23, 2009, at 10:39 AM, Alexandre Bergel wrote:
Hi Norbert,
You made a good point. Indeed, the situation is not clear.
Alexandre
On 23 Dec 2009, at 10:21, Norbert Hartl wrote:
Hi,
I've started to play around with moose a bit. The tools page on the moose site has quite impressive tools to offer. But as soon as I took a pharo image and loaded moose into it I recognized that it is (again) not as easy as I hoped.
For a lot of the tools I don't meet the smalltalk dialect requirements and/or I don't meet the operating system requirements. So, is there a matrix where I can see which of the tools are usable in which dialect or operating system?
Thanks,
Norbert _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
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:
Hi,
I've started to play around with moose a bit. The tools page on the moose site has quite impressive tools to offer. But as soon as I took a pharo image and loaded moose into it I recognized that it is (again) not as easy as I hoped.
For a lot of the tools I don't meet the smalltalk dialect requirements and/or I don't meet the operating system requirements. So, is there a matrix where I can see which of the tools are usable in which dialect or operating system?
Thanks,
Norbert _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
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:
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:
Hi,
I've started to play around with moose a bit. The tools page on the moose site has quite impressive tools to offer. But as soon as I took a pharo image and loaded moose into it I recognized that it is (again) not as easy as I hoped.
For a lot of the tools I don't meet the smalltalk dialect requirements and/or I don't meet the operating system requirements. So, is there a matrix where I can see which of the tools are usable in which dialect or operating system?
Thanks,
Norbert _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On 23 déc. 2009, at 10:21, Norbert Hartl wrote:
Hi,
I've started to play around with moose a bit. The tools page on the moose site has quite impressive tools to offer. But as soon as I took a pharo image and loaded moose into it I recognized that it is (again) not as easy as I hoped.
For a lot of the tools I don't meet the smalltalk dialect requirements and/or I don't meet the operating system requirements. So, is there a matrix where I can see which of the tools are usable in which dialect or operating system?
You are right. The main problem is that since we are porting Moose from Pharo to VW, many tools still reside in the VW platform, since there is nobody to port or maintain them. We port them on an as-needed basis. So the webpage is outdated with respect to that.
So you have two choices: use the VW suite (stable) or use the Moose suite (ongoing development). Now what tools do you want to use?
-- Simon
On 23.12.2009, at 12:56, Simon Denier wrote:
On 23 déc. 2009, at 10:21, Norbert Hartl wrote:
Hi,
I've started to play around with moose a bit. The tools page on the moose site has quite impressive tools to offer. But as soon as I took a pharo image and loaded moose into it I recognized that it is (again) not as easy as I hoped.
For a lot of the tools I don't meet the smalltalk dialect requirements and/or I don't meet the operating system requirements. So, is there a matrix where I can see which of the tools are usable in which dialect or operating system?
You are right. The main problem is that since we are porting Moose from Pharo to VW, many tools still reside in the VW platform, since there is nobody to port or maintain them. We port them on an as-needed basis. So the webpage is outdated with respect to that.
So you have two choices: use the VW suite (stable) or use the Moose suite (ongoing development). Now what tools do you want to use?
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
OK for Pharo to analyse Pharo code take the latest version on Pharo.
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.
why? There is a pharo version which is working well. You can get it by taking Pharo dev Gofer new squeaksource: 'Moose'; addPackage: 'ConfigurationOfMoose'; load. (Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault
Maybe I have to move to windows even to get the most out of it which I like to avoid
Thanks,
Norbert
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
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:
OK for Pharo to analyse Pharo code take the latest version on Pharo.
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.
why? There is a pharo version which is working well. You can get it by taking Pharo dev
Gofer new squeaksource: 'Moose'; addPackage: 'ConfigurationOfMoose'; load. (Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault
Maybe I have to move to windows even to get the most out of it which I like to avoid
Thanks,
Norbert
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- 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:
Hi Norbert,
When you say that you want to use Moose, what exactly is your goal?
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.
Do you have a particular system that you want to analyze? If yes, in what language is it written in?
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
Cheers, Doru
On 24 Dec 2009, at 13:14, Stéphane Ducasse wrote:
OK for Pharo to analyse Pharo code take the latest version on Pharo.
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.
why? There is a pharo version which is working well. You can get it by taking Pharo dev
Gofer new squeaksource: 'Moose'; addPackage: 'ConfigurationOfMoose'; load. (Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault
Maybe I have to move to windows even to get the most out of it which I like to avoid
Thanks,
Norbert
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Problem solving efficiency grows with the abstractness level of problem understanding."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Do you have a particular system that you want to analyze? If yes, in what language is it written in?
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.
To keep the other up to date. Nobert has a translater Javascript source -> XML. Yesterday evening I spent some time on trying to import the generated files into Moose using XMLParser and Pastell. No big result so far. I can reify functions with their parameters and variables defined in it.
I would be glad to collaborate on this if someone is interested in getting JavaScript in Moose.
Cheers, Alexandre
On 24 Dec 2009, at 13:14, Stéphane Ducasse wrote:
OK for Pharo to analyse Pharo code take the latest version on Pharo.
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.
why? There is a pharo version which is working well. You can get it by taking Pharo dev
Gofer new squeaksource: 'Moose'; addPackage: 'ConfigurationOfMoose'; load. (Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault
Maybe I have to move to windows even to get the most out of it which I like to avoid
Thanks,
Norbert
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Problem solving efficiency grows with the abstractness level of problem understanding."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
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:
Do you have a particular system that you want to analyze? If yes, in what language is it written in?
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.
To keep the other up to date. Nobert has a translater Javascript source -> XML. Yesterday evening I spent some time on trying to import the generated files into Moose using XMLParser and Pastell. No big result so far. I can reify functions with their parameters and variables defined in it.
I would be glad to collaborate on this if someone is interested in getting JavaScript in Moose.
Cheers, Alexandre
On 24 Dec 2009, at 13:14, Stéphane Ducasse wrote:
OK for Pharo to analyse Pharo code take the latest version on Pharo.
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.
why? There is a pharo version which is working well. You can get it by taking Pharo dev
Gofer new squeaksource: 'Moose'; addPackage: 'ConfigurationOfMoose'; load. (Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault
Maybe I have to move to windows even to get the most out of it which I like to avoid
Thanks,
Norbert
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Problem solving efficiency grows with the abstractness level of problem understanding."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"To lead is not to demand things, it is to make them happen."
I see that Pastell does not have an explicit license. Perhaps this should be clarified.
Ok.
Alexandre
Stef,
On 24.12.2009, at 13:14, Stéphane Ducasse wrote:
OK for Pharo to analyse Pharo code take the latest version on Pharo.
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.
why? There is a pharo version which is working well.
I played with the pharo moose and it is working. I started this thread because when it comes to moose tools I don't know what moose tools I can use in pharo on Mac Os. I think it is clearly stated in the subject of this thread.
Norbert
You can get it by taking Pharo dev
Gofer new squeaksource: 'Moose'; addPackage: 'ConfigurationOfMoose'; load. (Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault
Maybe I have to move to windows even to get the most out of it which I like to avoid
Thanks,
Norbert
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-
Alexandre Bergel -
Norbert Hartl -
Simon Denier -
Stéphane Ducasse -
Tudor Girba