[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [modeling-pmc] Re: [emft-dev] Proposal for Texo Component
|
Hi, Martin,
Certainly, there's nothing blocking a WTP component from using modeling
technologies; indeed, they do this already. Other projects such as STP and
DTP go even beyond WTP in their re-use and extension of our modeling
frameworks. Also, WTP is an extensible platform for web tooling just as
Modeling is an extensible platform for model tooling; this is just what
Eclipse projects are about.
I guess my point is really whether the purpose of Texo aligns more with the
mandate of the WTP project or the Modeling project, from the perspective of
its target user community. I'm not sure that the technology integrations
are as important a consideration. I definitely understand that there are
good reasons for both alignments.
Anyway, I raised the question because I hadn't seen much discussion of it
-- probably I just missed something. I'm coming rather late into this
discussion, and I don't want to derail it. My motivation is that,
personally, I'd like to see our modeling technology reaching out and making
more of an impact on the rest of Eclipse. Wouldn't it be great to see all
Eclipse projects not only building on the core platform, but also embracing
the MDD promise that is the Modeling project's raison d'etre?
Just my $0.02,
Christian
Christian W. Damus
Component Lead, Eclipse OCL and EMF MQ/MT/VF
IBM Rational Software
From: Martin Taal <mtaal@xxxxxxxxx>
To: PMC members mailing list <modeling-pmc@xxxxxxxxxxx>
Cc: EMFT Developer Mailing List <emft-dev@xxxxxxxxxxx>
Date: 04/16/2008 09:54 AM
Subject: Re: [modeling-pmc] Re: [emft-dev] Proposal for Texo Component
Hi Christian,
Depends on how you look at it. On the one hand the artifacts generated
are editable using wtp (for example jsp editor, dali project). On the
other hand the Texo project does not need to make use of any component
currently present in wtp while it uses (and tightly integrates with)
emf, mwe, jmerge, teneo and xpand. Also the ideas for a ui-model (the
presentation modeling framework) will be used by Texo. In addition it is
the idea to make it possible to extend the solution with custom
templates/workflows. So as there is a definite and large modeling side
to it I would say that it belongs to modeling.
gr. Martin
Christian Damus wrote:
> Hi,
>
> Can one also make an argument for locating this component in the Web
Tools
> Platform project? It seems to me that Texo is more of a model-driven web
> application development tool (and WTP is all about developing web apps)
> than it is a framework for building modeling tools or even a big-M
modeling
> app.
>
> Cheers,
>
> Christian
-----8<-----
--
With Regards, Martin Taal
Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Tel: +31 (0)84 420 2397
Fax: +31 (0)84 225 9307
Mail: mtaal@xxxxxxxxxxxxxx - mtaal@xxxxxxxxx
Web: www.springsite.com - www.elver.org
_______________________________________________
emft-dev mailing list
emft-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/emft-dev
