Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [modeling-pmc] Re: [emft-dev] Proposal for Texo Component

This sounds very cool!


Ed Merks schrieb:

Once-only code generators really do suck, so you have to wonder at their
preponderance given how relatively trivial it was to build Java merge
support. The original design and implementation of JMerge took roughly a
week of effort, as a I recall.  EMP is definitely a great basis for
building DSLs with the added benefit that they all have a common underlying
meta model to ensure that we don't end up with just a Tower of Babel.  In
addition, we aren't suffering from the misguided belief that XML syntax is
the be-all-and-end-all of human readable notations.

In our quest toward a grand vision, I think it's best to start small and to
build the little pieces bottom rather than carve out a grand high level
space top down.  We also have to consider our project's charter and be
sensitive to the concerns that the scope of the modeling project could just
creep out to consume all other projects.   Many DSLs would most logically
live in other projects and we'd be best off to ensure that things evolve in
that direction when it makes the most sense.  So for the time being, I'd
rather avoid creating more direct child projects under the modeling
project.  Having a small number of projects to group the large number of
components seems appropriate...

Ed Merks/Toronto/IBM@IBMCA
mailto: merks@xxxxxxxxxx
905-413-3265  (t/l 313)

Sven Efftinge <sven@xxxxxxxxxxx > To Sent by: EMFT Developer Mailing List modeling-pmc-boun <emft-dev@xxxxxxxxxxx>, PMC members ces@xxxxxxxxxxx mailing list <modeling-pmc@xxxxxxxxxxx> cc 04/16/2008 07:12 AM Subject [modeling-pmc] Re: [emft-dev] Proposal for Texo Component Please respond to PMC members mailing list <modeling-pmc@ecl>

Hi all,

this sounds very cool. We all know that there are many general
frameworks (web, RCP, SOA, etc,) out there which would profit from
Some of them (Ruby on Rails, Grails, SEAM just to name a few) already
use code generation a lot.
Unfortunately they use wizard-style passive code generation, where you
generate once and further change the generated code manually.
So most of the time generators are just used to get users up and
running as fast as possible.
Also they come up with concise languages to descibe domain models
(internal DSLs).
Those languages are not statically typed, have to fit into the host's
syntax and have no tool support at all (EMP can do better).
IMHO there should be some more projects like Texo, which show how EMP
can be used.

As EMFT is for EMF technology I find that those projects don't fit
well there. We should create a new Project for such domain-specific
applications of EMP.
What do you think?


btw: +1

On Apr 16, 2008, at 12:34 , Ed Merks wrote:
Extended EMF Community,

Martin Taal, the lead for the Teneo component, recently announced his
intent to work on the Texo component which will focus on exploiting
modeling technology for building web applications.

I request the community's approval to create this new component as
part of
the EMFT subproject with Martin Taal as the component lead.  Please
with +1 or -1 on this thread.  Obviously I recommend you give a +1,
Martin's outstanding track record with Teneo and his exemplary
support for
it.  All EMF and EMFT committers are eligible to vote, so please
take a
moment to do so.

Ed Merks/Toronto/IBM@IBMCA
mailto: merks@xxxxxxxxxx
905-413-3265  (t/l 313)

emft-dev mailing list

Sven Efftinge

Phone: +49 431 5606335
Fax     :  +49 431 5606339
Mobile: +49 175 5274726

mail: sven.efftinge@xxxxxxxxx

itemis AG
Schauenburgerstra├če 116
24118 Kiel

Rechtlicher Hinweis:
Amtsgericht Dortmund, HRB 20621
Vorstand: Wolfgang Neuhaus, Jens Wagener, Dr. Georg Pietrek
Aufsichtsrat: Dr. Burkhard Igel(Vors.), Stephan Grollmann, Michael

modeling-pmc mailing list

emft-dev mailing list

Arno Haase
Langemarckstr. 16
53227 Bonn

Mobil: +49 160 98525085
Tel:   +49 228 9654443
Fax:   +49 228 9654448

Attachment: signature.asc
Description: OpenPGP digital signature

Back to the top