| An appeal for modeling community review to new "EMF Build Manager Project" Proposal [message #622062] |
Mon, 01 February 2010 00:41 |
Eclipse User |
|
|
|
Hello,
Attached is the PDF version of the forementioned EMF Build Manager Project
Proposal.
I kindly ask EMF community members and EMF (and subprojects) committers to
review the document and forward their thoughts.
I am also looking for mentors for the proposal.
Below is the extraction of "Background" of the project. Please remember to
review the attached PDF for full proposal draft.
I apoligize for crossposting...
============================================================ =
BACKGROUND
EMF has been around for a long time. But the fact is that it lacked the
necessary IDE Build Manager integration ever since.
We think, the current code generation and validation toolset is below
eclipse UI quality standards and fell behind similar facility provisions
from the other projects.
For instance, given the current infrastructure, if a developer is working
with two ecore models that are dependent each other along with their
respective genmodel, when developer makes a change in the base model that
requires a change in the dependent ecore model, will need quite a lot of
clicks and at least 4 editor switches, 2 actions executions along with
several clicks to locate the action and run them.
Also during the generation process, the UI is blocked and having finished
the change on the base ecore, the developer cannot continue working on the
second ecore before the base model generation finishes. Further more there
is also need to switch to genmodels twice and initiate generation
delibarately.
In addition to this, if developer would like to validate the model in
between the unit of the works, that will require clicks to locate the
validation action, click to run the action and click to dismiss the
feedback.
It is also in our experience that the genmodel editors are kept open just
for triggering code genration. Furthermore, this not only clutters the
editor folder with unneeded editors, but also breaks the 'editor'
description for genmodel, as usualy once genmodels are set up, they very
seldom change, but needed to be open for code generation.
When used on large workspaces with more than a few model, problem becomes a
real burden.
This is where EBM steps in and delegates much of the work to background
build manager and prevents user distrubition with using the instruments
like
auto build on resource save, Marker and Problem View instrumentation to
provide feedback.
============================================================ =
Regards,
--
Hasan Ceylan
hceylan@batoo.org
+90 (532) 713-5384
+90 (216) 332-5647
From Thomas Gray's poem, Ode on a Distant Prospect of Eton College (1742):
"Where ignorance is bliss, 'tis folly to be wise."
--
|
|
|
Powered by
FUDForum. Page generated in 0.02666 seconds
Home