I'm getting closer to introducing the concept of an Editor; specifically, a visual component within a page area that supports the editing of an object or file (some input.) This is somewhat like a view, but different: multiple editors of the same type can be opened within the editor area on the page (for editing different inputs) (think eclipse when you're opening java files that are tabbed accross the editor area - instead of java files, customer records, for example), while there can only be at most one view of a given type displaying on a page. Editors can be explicitly saved, modified (can be dirty), and are typically backed by a form/form model for editing a domain object.
The first step towards this goal is introducing two interfaces: Dirtyable and Saveable, which the Editor interface will inherit when it is introduced. The next step is to add the ability for the application page to open editors for a particular editor input (say a domain object) and display that within the editor pane area. The framework will track the active editor and if changes have been made, issue a "save reminder' for example when the editor window is closed.
Thoughts? For you Eclipse RCP gurus our design is similiar on purpose: one to facilitate people going between both platforms (ease of learning curve) and secondly because it's just good design. Our niche is we will be a lighter weight implementation built on Spring for configuration, and hopefullly one that's more pluggable with regard to the underlying windowing system.