Home » Modeling » eTrice » Another product based on ROOM and ObjecTime
| Another product based on ROOM and ObjecTime [message #1718751] |
Tue, 29 December 2015 18:48  |
 Ken Webb
Messages: 1
Registered: December 2015 |
Junior Member |
|
|
I only learned about eTrice a few weeks ago, and have been quite keen to explore it. I'm the author of Xholon, which is also based on the concepts in ROOM and ObjecTime, especially as specified in the UML 2 document. I hope these comments might be of interest to members of the eTrice community.
I've written a Java class that generates an eTrice .room file, for any app created using Xholon. The early incomplete version of the Xholon2ETrice converter can export the main features of Structure (ActorClass, inheritance, ActorRef, Binding, ports, conjugated ports, relay ports) to a .room file, that the eTrice standalone generators and the Eclipse plugin can then successfully process.
The Xholon exporter can also convert state machine Behavior, but for now I'm getting errors with the eTrice standalone generators and in Eclipse. The Xholon state machine sample app was itself automatically generated from a MagicDraw UML model.
As a bit of background, I worked for ObjecTime for a few years in the late 1990s, and am mentioned in the ROOM book (Selic et al, 1994) on page xxxi. At the time, I was very excited by the ROOM and ObjectTime appproach. I wrote Xholon because I missed having such a tool, and because I wanted to extend the ROOM concepts in various ways, based on the published UML 2 descriptions.
There are many differences between eTrice and Xholon. In general, Xholon has intentionally become a lot less rule-bound and more informal. Current applications include children's stories, models of biological cells, animating Hollywood movie scripts, teaching elementary school kids to code, and anything else I'm interested in. I still feel that ROOM is a great conceptual basis for any type of application. Xholon is written in Java, but I use GWT to commpile it to JavaScript so all apps can be run as a web page in any modern browser. I use XML to specify inheritance and composite-structure hierarchies, and XPath expressions to specify port bindings.
I would also like to be able to parse eTrice .room files to generate a Xholon app. It would be especially nice to use eTrice state machine diagrams. If I decide to do that, I'll ask some questions on this forum to determine what might be the best way to proceed.
The forum won't allow me to include links in this email. The generated .room files are at my github site: kenwebb Xholon - Xholon exports etrice
Ken Webb
|
|
|
| Re: Another product based on ROOM and ObjecTime [message #1719741 is a reply to message #1718751] |
Mon, 11 January 2016 18:17  |
Henrik Rentz-Reichert
Messages: 261
Registered: July 2009 |
Senior Member |
|
|
Hi Ken,
your Xholon project sounds interesting - even though I have to admit
that I didn't understand too much of the approach. The web world is
pretty far from my what I do.
Nevertheless glad that an ObjecTime veteran shows interest in our
project (meanwhile we have contact to quite a few).
If you need help with your transformation efforts you are always welcome
to contact us. We will do our best.
Henrik
Am 29.12.2015 um 20:18 schrieb Ken Webb:
> I only learned about eTrice a few weeks ago, and have been quite keen to
> explore it. I'm the author of Xholon, which is also based on the
> concepts in ROOM and ObjecTime, especially as specified in the UML 2
> document. I hope these comments might be of interest to members of the
> eTrice community.
>
> I've written a Java class that generates an eTrice .room file, for any
> app created using Xholon. The early incomplete version of the
> Xholon2ETrice converter can export the main features of Structure
> (ActorClass, inheritance, ActorRef, Binding, ports, conjugated ports,
> relay ports) to a .room file, that the eTrice standalone generators and
> the Eclipse plugin can then successfully process.
>
> The Xholon exporter can also convert state machine Behavior, but for now
> I'm getting errors with the eTrice standalone generators and in Eclipse.
> The Xholon state machine sample app was itself automatically generated
> from a MagicDraw UML model.
>
> As a bit of background, I worked for ObjecTime for a few years in the
> late 1990s, and am mentioned in the ROOM book (Selic et al, 1994) on
> page xxxi. At the time, I was very excited by the ROOM and ObjectTime
> appproach. I wrote Xholon because I missed having such a tool, and
> because I wanted to extend the ROOM concepts in various ways, based on
> the published UML 2 descriptions.
>
> There are many differences between eTrice and Xholon. In general, Xholon
> has intentionally become a lot less rule-bound and more informal.
> Current applications include children's stories, models of biological
> cells, animating Hollywood movie scripts, teaching elementary school
> kids to code, and anything else I'm interested in. I still feel that
> ROOM is a great conceptual basis for any type of application. Xholon is
> written in Java, but I use GWT to commpile it to JavaScript so all apps
> can be run as a web page in any modern browser. I use XML to specify
> inheritance and composite-structure hierarchies, and XPath expressions
> to specify port bindings.
>
> I would also like to be able to parse eTrice .room files to generate a
> Xholon app. It would be especially nice to use eTrice state machine
> diagrams. If I decide to do that, I'll ask some questions on this forum
> to determine what might be the best way to proceed.
>
> The forum won't allow me to include links in this email. The generated
> .room files are at my github site: kenwebb Xholon - Xholon exports etrice
>
> Ken Webb
|
|
|
Goto Forum:
Current Time: Fri Apr 26 14:07:01 GMT 2024
Powered by FUDForum. Page generated in 0.03828 seconds |
] 
Search
Help
Register
Login
Home
