Hi Christian,
there is no direct dependency of the deisgner plugins to the C++
library. However, the examples depend on it. it would be an option
to move the library into the Papyrus model repository. But it would
only work in a practical way, if technical aspects such a s model
registration and pathmap definition would be handled by this
repository. Of course, we could split the "bare" model definition
and the pathmap aspect (separate plugin), but it would foster a
common use of these libraries, if all user models reference them in
the same way.
Ansgar
On 06/04/2016 17:30, Christian Damus wrote:
Hi, Ansgar,
A question that I have is, what is the specific affinity of this
library with Designer? It’s simply (today) a collection of
primitive types as recognized in the ANSI C standard.
This library seems to me a good candidate for a new Papyrus Model
Repository project after the fashion of the UPR project (which is
dedicated to providing OMG-standard profiles, so not appropriate
for our purposes). I am not sure, but I feel like the notion
of a common provider of shared model libraries has been discussed
before. If not, perhaps we should start that discussion
now.
cW
On 6 April, 2016 at 11:25:46, Ansgar
Radermacher (ansgar.radermacher@xxxxxx)
wrote:
Hi Peter,
the first release of designer is planned for Friday morning.
I talked to Francois (in CC) who knows build issues much better
than I do: I understand that it is possible to declare additional
repositories in the Papyrus-RT update site configuration. These are
searched automatically when the user installs Papyrus-RT. I.e. the
user does not have to add further update sites manually.
Thus, the main issue is an additional configuration in the
build/update site of Papyrus-RT. While it may seem a certain
additional effort for a small library, it will keep the possibility
open to have more common code in the future (e.g. the reverse
mechanisms)
The two alternatives are (1) keeping a separate copy (that might
involve independently) and (2) keeping the Ansi C library in the
Papyrus repository (and remove it from designer). Both options are
in my opinion less good.
Best regards
Ansgar
--
Ansgar Radermacher CEA/DRT/DILS/LISE
http://www-list.cea.fr/index.htm
phone: +33 16908 3812
mailto: ansgar.radermacher@xxxxxx
_______________________________________________
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
--
Ansgar Radermacher CEA/DRT/DILS/LISE
http://www-list.cea.fr/index.htm
phone: +33 16908 3812
mailto: ansgar.radermacher@xxxxxx
_______________________________________________
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
