Hi Charles, see comments inline as well as my answer to Ernesto.
On 11/08/2016 05:37 PM,
charles+zeligsoft.com wrote:
Hi Patrik,
From an Ericsson perspective, is this something that
is of high priority? We need to properly understand our end user
priorities for releases.
As I answered to Ernesto I've started to go though the code and
don't have a specific set of methods that are required yet. In the
short term while identifying the actual needs (the concrete method
etc) maybe I can implement this myself. However what would be good
is if the structuring of the major components could be address so it
would be easier to push this back.
In the long run I'd see this as a high prio requirement from
Ericsson (and others) since to be able to easily build custom code
gen, validation, refactoring etc on top of UML-RT.
Also, and just as important, we would need a
description of what you need to have to make this easier.
Without requirements, we could only guess at what you want/need
and we would not be able to properly estimate the amount of work
required.
As it stands, getting this in place for v0.9 would
be difficult as we already have too much work identified for the
deadline requested by Ericsson.
Not sure that is has to be addressed by 0.9 (maybe the structuring
part though)
Regards,
Charles
Rivet
Senior Product Manager, Papyrus-RT product lead
Hi Patrick.
Yes, indeed that we can and will split the
codegen feature. It has been proposed (thanks to Peter)
to refactor the code generator into components for
different target languages, and have a generic "core
codegen" in common.
I already started some of this refactoring,
but it is not there yet, and it is not in the list of
bugs for 0.9 which are the priority.
Nevertheless, this generic codegen component
is supposed to have a "skeleton" of the code generator
(there are several alternatives, perhaps a Template method or Strategy pattern or go with an MWE2
workflow). In the "core" component that you'd like,
would you include that "generic" code generator
skeleton, or are you looking for including only core
utility classes? If the latter, then we should have two
"core" components: one with the generic codegen and the
other with just utilities. By the way, which classes
would you like to see in that component?
By the way, the code generator can be run
stand-alone, as in really stand-alone, i.e. no Papyrus
runtime service, not even headless Eclipse, just plain
Java. See the oeprt.codegen.standalone plugin. (I spent
quite a bit of time on making this work).
--
Ernesto Posse
Zeligsoft
Hi,
A question regarding the
org.eclipse.papyrusrt.codegen.utils plugin. It
ocontains some nice utils I'd like to use for our
custom code genrator
etc but it is bundled into the
org.eclipse.papyrusrt.codegen-feature
which includes a lot of things that I don't need and
that just would
bloat our custom installation.
Would it be possible to split that feature into two
where one contains
the more generic utils etc and the one the specific
Papyrus-RT code
generator details? If the genric sould be a new
feature och part of core
or soemthing aready existing, I don't know.
The important thing is that these utils can be used in
standalone mode,
ie without the Papyrus service runtime, something that
I understand also
is needed by the Papyrus-RT C++ codegen.
/Patrik
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your
password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
|