| Summary: | Consider making a "Xtext project with UML model referencing" project wizard | ||
|---|---|---|---|
| Product: | [Modeling] TMF | Reporter: | Jeppe Cramon <jeppe> |
| Component: | Xtext | Assignee: | Project Inbox <tmf.xtext-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | moritz.eysholdt, sebastian.zarnekow, sven.efftinge |
| Version: | 2.0.0 | ||
| Target Milestone: | --- | ||
| Hardware: | Macintosh | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
|
Description
Jeppe Cramon
There is a big difference between "creating a textual syntax for an UML model" and "allowing cross-references to point to UML-Elements". Christian blog post is talking about the second scenario. These steps acre actually necessary for every "foreign" EMF model that you want Xtext to index. Hi Mortiz The name for the wizard was badly chosen, thanks for pointing that out :) A name like "Xtext project with UML model referencing" is probably a better name. My point is that it shouldn't be necessary to configure and program this much (e.g UmlResourceDescriptionStrategy, UmlRuntimeModule, UmlQualifiedNameProvider, UmlSupport, UmlUiModule, etc.) to get UML referencing working with xtext. UML is pretty commonly used and if you want further adaption of Xtext, then you shouldn't make too hard for UML people to get their models working with xtext. There's simply so much knowledge packed in Christians blog post, that people starting out with xtext shouldn't need to care/know about. Don't make it too hard for them to like xtext. The learning curve is steep enough as it is ;) So if you would provide the default implementations for referencing UML models, it would also be really nice if you could provide a wizard that could setup uriMappings, registerGeneratedEPackages, registerGenModelFiles, pluginDependencies, etc. /Jeppe I'm inclined to close this as won't fix for Xtext core. Any objections? Could it be moved to a sub project or don't you agree that it could be valuable for people coming from a more traditional UML background? We don't think using UML in the context of DSLs is a good idea in general. There might be cases where UML just is what you need, but coming up with a wizard doesn't fit with our thinking of UML :-) How about having such extensions in a separate project at Eclipse Labs? I'd be happy to list it on the Community page. Closing all bugs that were set to RESOLVED before Neon.0 Closing all bugs that were set to RESOLVED before Neon.0 |