|Re: Target Platforms Extensions and Eclipse compatibility issues [message #1113231 is a reply to message #1113129]
||Fri, 20 September 2013 20:57
| Miles Parker
Registered: July 2009
Francesco Farina wrote on Fri, 20 September 2013 13:32|
Dear Miles Parker,
I'm working on AMP for Academic purpose, looking whether it would be possible to add MASON as a target platform for AMP.
I would like to ask some questions:
- Could you give me some advices on how to start and where to look. Moreover, has this feature (MASON as a target platform) already been developed? Considered? Would it be possible?
Glad you're interested! I would look at all of the stuff in the amf gen projects:
Basically, the idea would be to create a
Specializing the templates based on for example:
- The second question is about the AMP compatibility with Eclipse's releases.
I was able to let it work with Indigo but I had some problem with other releases. I've noticed your commit (Update to use Juno p2), and tried to follow the build from the source guide but I had some problems, for example:
"No suitable provider for component org.eclipse.amp.releng:Buckminster was found in resourceMap
Could I get AMP working with Eclipse Juno or later?
Oh, that's ironic. I think buckminster is saying that it can't find itself. Sigh.
Actually, it isn't too hard to deal with the dependencies manually. I'd suggest installing all of the dependencies manually. You can see the various update sites in amp-platform.cspec.
My only concern would be w/ xpand. We're using an elder version of that (not the new xtend support) so you need to be sure to get the appropriate version.
It should run fine under Juno, but I can't voich for Kepler+..
|Re: Target Platforms Extensions and Eclipse compatibility issues [message #1150018 is a reply to message #1113129]
||Tue, 22 October 2013 13:22
| Marco Amoruso
Registered: September 2013
I'm Francesco's collaborator, we would like to inform you on our work about Mason integration in AMP.
First we added a new project called org.mason.core and another one called org.mason.core-feature, to have Mason as a plugin. Then, as you suggested, we created the org.eclipse.amp.amf.gen.mason project, specializing the xpt templates. In particular, we had some problems with Java.xpt, and since it's used by Ascape and Escape, we decided to add the file JavaMason.xpt in org.eclipse.amp.amf.gen.mason.
Moreover we added org.eclipse.amp.amf.ide.mason in order to create a new Agent Modeling Mason Project that includes the Mason plugin as a dependence. The execution and the visualization of the running simulation is not integrated in Eclipse such as Escape for example, because we don't use AXF and AGF for the moment.
In the last 2 or 3 weeks we have been working on Mason code generation. Our purpose is to lay the foundations about it.
Currently we aren't going to map every AMP features in Mason code.
We built a simple model (Particles, Tutorial3 of Mason) and we reached on having it running by adding a few lines of code using the Method feature.
We would like to have some feedbacks from you and we would will be pleased if you could give us some advice or ideas.
|Re: Target Platforms Extensions and Eclipse compatibility issues [message #1154957 is a reply to message #1150258]
||Fri, 25 October 2013 15:35
| Francesco Farina
Registered: September 2013
it's nice to see that you are glad of this job.
We've just uploaded the AMP source code complete of our projects to GitHub.
Here is a guide to let it work with Eclipse Kepler or Luna. It contains the repository link.
This is a metamodel compatible with the MASON target platform, it is a simplified version of Particles as it is shown in the MASON Tutorial 3.
Your feedbacks will be appreciated.
[Updated on: Fri, 25 October 2013 17:54]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.05616 seconds