| using EMF2DOMSSE bridge to edit files outside of workspace [message #222728] |
Mon, 20 October 2008 02:11  |
Eclipse User |
|
|
|
Originally posted by: anton.kraev.net
We are using EMF2DOMSSE bridge to edit config files (with form-based
tabs and source XML tab), this works nice and dandy for files inside
workspace (IFile).
Let's say we want the same for files outside of workspace.
Now, EMF2DOMRenderer works fine with these (using InputStream API).
EMF2DOMSSERenderer heavily depends on IFile and explicitly discourages
using InputStream by throwing an exception when InputStream passed in is
not null. Is there particular reason for this design decision? I looked
at hacking it by extending EMF2DOMSSERenderer, but it requires
reimplementing too much.
Any ideas?
|
|
|
| Re: using EMF2DOMSSE bridge to edit files outside of workspace [message #222856 is a reply to message #222728] |
Tue, 21 October 2008 03:28  |
| Eclipse User |
|
|
|
Originally posted by: david_williams.linux.vnet.ibm.com
Anton Kraev wrote:
> [....] Is there particular reason for this design decision?
I'm not sure which version you are using, but the original reason, from
several releases ago, was probably that somewhere, somehow, something
depended on IFile, or more likely IProject (deduced from the IFile), to
correctly interpret or read the file or pass it to an editor.
Lots of things have changed in the platform (and the platform's editors)
since this class was first created, so I am not sure it it's still
required or not ... I'm just explaining the probable reason for the
design decision.
hope it helps
|
|
|
Powered by
FUDForum. Page generated in 0.03182 seconds
] 
Search
Help
Register
Login
Home
