[jboss-jira] [JBoss JIRA] Updated: (GPD-67) GPD support for editing non-files (any IEditorInput, not just FileEditorInput)

[Koen Aers (JIRA)]

     [ https://jira.jboss.org/jira/browse/GPD-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Koen Aers updated GPD-67:
-------------------------

    Fix Version/s:     (was: jBPM jPDL Designer 4.0.0.alpha1)


> GPD support for editing non-files (any IEditorInput, not just FileEditorInput)
> ------------------------------------------------------------------------------
>
>                 Key: GPD-67
>                 URL: https://jira.jboss.org/jira/browse/GPD-67
>             Project: JBoss jBPM GPD
>          Issue Type: Feature Request
>          Components: jpdl
>            Reporter: John Ruud
>            Assignee: Koen Aers
>            Priority: Minor
>
> We need to edit process defs that are stored in a DB, as opposed to the processdefinition.xml, gpd.xml files stored in the workspace. There are currently many dependencies to FileEditorInput/File throughout GPD (as is the case for a lot of other Eclipse editors BTW).
> It would be very helpful if it would be feasible to separate out the code that deals with a particular type of IEditorInput from the rest of the editor, possibly into a separete delegate class. For FileEditorInput the delegate would deal with reading, writing, and syncronizing the view (resource listeners), plus whatever else I may have forgotten. We could then replace the default "file" delegate with our own that knows how to deal our DB (by subclassing of the editor would be fine). 
> Probably not the #1 GPD issue for many other users, but hopefully something you would keep in mind...

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira