Hi WIm, Thank's a lot for your clarification.
For the tooling, I had already tried the Wizard which generates the E4 Application. But I think SamplePart should be improved with dirty, close, save etc because the first time when you generate the E4 application you have the impression that E4 doesn't provide a lot of feature (I think dirty, close, save feature are the commons feature for an editor). Regards Angelo 2013/9/8 Wim Jongman <[email protected]> > We have that. If you install the e4 tooling you can create an e4 >> application with a view. An editor just implements the @dirtyable >> annotation. >> >> >> ??? Never heard of this annotation all an editor has to do is to mark a >> method with @Persit >> > > Typo. I mixed-up MDirtyable with @Persist. Members of the same family. > > >> >> If your editor just depends on EditorPart then there is a different story >> because EditorPart can be quite easily rewritten to pure Eclipse 4. >> However, since pure Eclipse 4 does not work with the *Advisor classes any >> more, saving and restoring state is up to you until the time the e4 project >> provides something generic. >> >> >> It does that already just annotate a method with @PersitState >> > > Yes. Scratch everything after "However,". Obviously, state can be saved > and restored. > > > _______________________________________________ > 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
