Eric,
I'd prefer we not use E. Of course it's a great letter, with Ed and
Eric being just excellent examples of that, but the Ecore model has
trademarked it, so I'll have to sue you if you use it. :-P
Perhaps we can think of a catchy acronym, a very short word, or get
Steve to prefix all his names with SWT. :-P M seems the best
suggestion so far because I imagine E4 would one day seem dated when E5
comes along, as it surely will if E4 is successful!
Maybe no one else cares, which surprises me because the more trivial an
issue, the more opinions there seem to be!
Cheers,
Ed
Eric Moffatt wrote:
While working away on the
compatibility
I've (finally) reached the point where Paul and I are starting to get
the
Menu/Toolbar story together but we've hit a snag. The current model's
elements
such as Menu, MenuItem...clash with the existing SWT classes, making it
very difficult to wotk on the code.
We'd like to change the model so
that
we don't have these clashes and would happily take suggestions on what
to do and/or if anyone thinks that changing these is an issue.
After talking with Boris and Paul
the
best we've got so far is to add a 'prefix' letter to all the model
elements;
'M' for model, 'E' to match EMF's types, 'E4'. <insert your facorite
char here>
Which one is best?
Does anyone have another strategy?
Is this a good idea?
Onwards,
Eric
_______________________________________________
e4-dev mailing list
e4-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/e4-dev
|
