| Separate editors from code? [message #876279] |
Thu, 24 May 2012 05:45  |
Maarten Bezemer Messages: 66 Registered: February 2012 |
Member |
|
|
Hi all,
I thought to start this as a topic (instead of a bug report) as it is easier to discuss on the forum.
I was wondering whether it is possible to separate the editors from the (engine) code?
For the application I am developing, I use the official releases as much as possible, so the users can easily install Epsilon.
But, for development I would like to use the most up-to-date editors (especially since some of my bugs are fixed in the unreleased version).
Currently, the editors cannot not easily replaced, unless one dives into the framework and finds out which parts/plugins provide the editors and (somehow) update only those parts. (As far as I know)
Another reason is that the users of my application does not require the editors, so they do not need to waste resources on this (although it probably would not be too much...).
Regards,
Maarten
|
|
|
|
| Re: Separate editors from code? [message #876462 is a reply to message #876282] |
Thu, 24 May 2012 12:45   |
|
If I may add, not only the editors, but also the wizards and all other UI/user friendly code/plugins. As Maarten my application runs epsilon transformations in the "back" and the users don't really need to know that it is epsilon what I am using. So with a more fine separation we could control more easily what editors, views, menus, wizards, etc., we want to deploy.
Regards,
Horacio Hoyos Rodriguez
EngD Student
University Of York
|
|
|
|
Powered by
FUDForum. Page generated in 0.08762 seconds