I think Angelo wants some base class which already implements dirty, focus, memento, save as, issaveasallowed, editor input, etcetera. An editor that is uniform to workbench requirements and that plays along well with the 3.x editor lifecycle.
Cheers, Wim On Fri, Sep 6, 2013 at 4:07 PM, Lars Vogel <[email protected]> wrote: > Hi Angelo, > > I'm not sure if I understand your question correctly. Dirty and focus is > handled via the application model. > > Best regards, Lars > > > 2013/9/6 Angelo zerr <[email protected]> > >> Hi E4 Team, >> >> I know this topic comes from every time, but I would like to know what is >> the sate of E4 Editor. >> My project >> CodeMirror-Eclipse<https://github.com/angelozerr/CodeMirror-Eclipse> provides >> Eclipse 3.x EditorPart, but I would like to provide too Eclipse 4.x Editor. >> >> I would like to avoid developping my own Pojo class like ModelEditor. E4 >> provides the capability to manage your editor with Pojo, it's a great >> feature, but IMHO I think E4 should provide an abstract class for editor >> like EditorPart which manages dirty, focus, after that E4 could provide >> TextEditor class and a lot of project (JDT Java editor, WTP XML editor, >> etc) could migrate to a pure E4 code (but I don't know if it's the goal of >> E4 to remove 3.x EditorPart, View in the future?). >> >> Many thank's for your help. >> >> Regards Angelo >> >> >> >> _______________________________________________ >> e4-dev mailing list >> [email protected] >> https://dev.eclipse.org/mailman/listinfo/e4-dev >> >> > > _______________________________________________ > e4-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/e4-dev > >
_______________________________________________ e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/e4-dev
