importers page

Hi,

I created a page dedicated to importing instructions:
http://www.moosetechnology.org/docs/importers

A good example of how these instructions should look like can be found here:
http://www.moosetechnology.org/docs/importers/importJavaWithinFusion 

We would need more detailed information about:
- Import C# with PMCS
http://www.moosetechnology.org/docs/importers/importCSharpWithPMCS

- Import C with CAnalyzer
http://www.moosetechnology.org/docs/importers/importCWithCAnalyzer


Cheers,
Doru


--
www.tudorgirba.com

"Obvious things are difficult to teach."



_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

I created a MSE file with PMCS to see if it accurately generates MSE files. The program runs correctly and offers a UI to understand the model and generate MSE files. However, It seems that the current MSEs imported in Moose are following a different model e.g. not starting with Moose.Model. I have tried to play a bit but it didn't work. I'll make it compatible with the current version and see what do we have to do to make it work completely with the current version of Moose.
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Hi Usman,

Thanks for looking into this.

Indeed, it looks like PMCS exports for FAMIX 2.1 and the MSE for Meta in VW.

The format should definitely be changed if we want to load it out of the box in the Pharo version.

Cheers,
Doru


On 1 Apr 2011, at 22:58, Usman Bhatti wrote:

--
www.tudorgirba.com

"Every successful trip needs a suitable vehicle."





_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

I'm trying to use Moose as a framework for data analysis - i.e. beyond code analysis.  It happens to be for system development, in particular project schedules.

I have downloaded Pharo 2.0, and added Moose 2.8 (http://www.moosetechnology.org/download/4.8).

I've created an FM3 model (based on the pattern for the library meta-model described in http://scg.unibe.ch/wiki/projects/fame/mse) to create a new FM3 package called Kleio.  This meta-model is specific to my data domain, and is defined in terms of FM3.Class, FM3.Property, etc.

How do I import this meta-model into Moose?

One possible entry point is the Moose Panel MSE Model Import, but this fails as the FM3 classes are not in the model - i.e. this function imports models, not meta-models.

Another possible entry point is the Moose Meta Browser - but unlike say the PetitParser Browser, the Meta Browser does not include an "add" interface function.

Any suggestions please.

Regards,
Alan.

Yes - I of course meant Moose 4.8.

I'm trying to use Moose as a framework for data analysis - i.e. beyond code
analysis.  It happens to be for system development, in particular project
schedules.

I have downloaded Pharo 2.0, and added Moose 2.8
(http://www.moosetechnology.org/download/4.8).

I've created an FM3 model (based on the pattern for the library meta-model
described in http://scg.unibe.ch/wiki/projects/fame/mse) to create a new FM3
package called Kleio.  This meta-model is specific to my data domain, and is
defined in terms of FM3.Class, FM3.Property, etc.

How do I import this meta-model into Moose?

One possible entry point is the Moose Panel MSE Model Import, but this fails
as the FM3 classes are not in the model - i.e. this function imports models,
not meta-models.

Another possible entry point is the Moose Meta Browser - but unlike say the
PetitParser Browser, the Meta Browser does not include an "add" interface
function.

Any suggestions please.

Regards,
Alan.



--
View this message in context: http://forum.world.st/importers-page-tp3419669p4679950.html
Sent from the Moose mailing list archive at Nabble.com.
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

What kind of data analysis you want to do ? You should have a look at quicksilver a very nice framework for data visualization based on hierarchic graphs: http://smalltalkhub.com/#!/~Quicksilver/Quicksilver

Envoyé de mon iPhone

Le 6 avr. 2013 à 12:52, badja <[hidden email]> a écrit :

I'm trying to use Moose as a framework for data analysis - i.e. beyond code
analysis.  It happens to be for system development, in particular project
schedules.

I have downloaded Pharo 2.0, and added Moose 2.8
(http://www.moosetechnology.org/download/4.8).

I've created an FM3 model (based on the pattern for the library meta-model
described in http://scg.unibe.ch/wiki/projects/fame/mse) to create a new FM3
package called Kleio.  This meta-model is specific to my data domain, and is
defined in terms of FM3.Class, FM3.Property, etc.

How do I import this meta-model into Moose?

One possible entry point is the Moose Panel MSE Model Import, but this fails
as the FM3 classes are not in the model - i.e. this function imports models,
not meta-models.

Another possible entry point is the Moose Meta Browser - but unlike say the
PetitParser Browser, the Meta Browser does not include an "add" interface
function.

Any suggestions please.

Regards,
Alan.



--
View this message in context: http://forum.world.st/importers-page-tp3419669p4679950.html
Sent from the Moose mailing list archive at Nabble.com.
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

> I'm trying to use Moose as a framework for data analysis - i.e. beyond code
> analysis.  It happens to be for system development, in particular project
> schedules.

Sounds great!
I often analyze data that are not directly source code, such as software process specification or user profiles.
What you need are essentially:
  - a description of your metamodel, Pharo classes, subclass of MooseEntity
  - a parser: I usually use XML files or simple-to-parse file input

> I have downloaded Pharo 2.0, and added Moose 2.8
> (http://www.moosetechnology.org/download/4.8).
>
> I've created an FM3 model (based on the pattern for the library meta-model
> described in http://scg.unibe.ch/wiki/projects/fame/mse) to create a new FM3
> package called Kleio.  This meta-model is specific to my data domain, and is
> defined in terms of FM3.Class, FM3.Property, etc.
>
> How do I import this meta-model into Moose?

The meta-model is defined in terms of subclasses of MooseEntity.

> One possible entry point is the Moose Panel MSE Model Import, but this fails
> as the FM3 classes are not in the model - i.e. this function imports models,
> not meta-models.
>
> Another possible entry point is the Moose Meta Browser - but unlike say the
> PetitParser Browser, the Meta Browser does not include an "add" interface
> function.

I am not expert in FM3 specification, but I guess that to be able to load the code example in http://scg.unibe.ch/wiki/projects/fame/mse you need some classes:

MooseEntity subclass: #MyLibrary
        instanceVariablesNames: 'librarian books'.

MyLibrary class>>annotation
        <MSEClass: #Library super: #Object>
        <package: #LIB>
        ^ self

MooseEntity subclass: #MyBook
        instanceVariablesNames: 'title authors'.

MyBook class>>annotation
        <MSEClass: #Book super: #Object>
        <package: #LIB>
        ^ self

...

I guess you also need to meta-describe the instance variables. Have a look at the class FAMIXClass to have an example

Cheers,
Alexandre

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Many thanks Alexandre.

Following your advice I have been able to code my FM3 classes as MooseEntity classes and get them displaying correctly in the Moose Meta Browser (once I have reinitialized the definitions).

I'm now working on defining the instance variables.

I'd highlight for any other developers following that the annotations are class methods, and following the pattern set by other Moose classes, annotation should be under the "meta" protocol.  The annotation method often has no return.

Regards,
Alan.

Jannik developped a MSE2.1 to MSE3.0 converter at some point in the past ...

nicolas

On 04/01/2011 11:22 PM, Tudor Girba wrote:
--
Nicolas Anquetil -- RMod research team (Inria)

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Hi Alan,

Welcome in our community :).

I am happy that you were able to fix your problem. It would so great if you would document the experience on some blog, or if not, we can host a it on the moose webpage.

In any case, please keep the questions coming.

Cheers,
Doru


On Apr 7, 2013, at 9:32 AM, badja <[hidden email]> wrote:

--
www.tudorgirba.com

"Some battles are better lost than fought."




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Doru,

I would like to document my Kleio project on a Moose web page.

Perhaps the moose wiki, although that appears dormant.  I prefer a wiki over a blog as much of my development is trial and error, with a lot of error.

Regards,
Alan.

Hi,

The Moose page is not dormant :).

I will create a user for you.

But, before we go there, could you tell us:
- Where to look for a demo?
- Is the code open-source?

Cheers,
Doru


On Apr 27, 2013, at 8:07 AM, badja <[hidden email]> wrote:

--
www.tudorgirba.com

"If you can't say why something is relevant,
it probably isn't."


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Doru,

Kleio is work in progress, so no demo yet.

I want to describe the project goals, design and experience in using Moose as much as the coding.  I hope this will make a good case study for Moose.

You may be interested that I'm using the Hismo meta-model.  In the same way you analysed the history of JBoss code, I'll be analysing the history of a portfolio of project schedules.  System development, rather than Software Development I'm afraid :-). I'm currently reading your PhD as part of my literature search.

Slow going, as this isn't my day job.  Part time (very part time) PhD at UTS, Sydney.

The source code will be made available on SqueakSource 3 under MIT.  I'm keeping this code private until I have something I can demonstrate, and then I'll make the Kleio source publicly available.

Regards,
Alan.

Sound exciting!

Alexandre

Le 27 avr. 2013 à 22:44, badja <[hidden email]> a écrit :

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev