Document/View? Why not Model/View/Controller (MVC)?
Document/View is a specialization of MVC, in which the Model is the Document, and the View and the Controller are combined into the View. In MVC the Controller takes care of user interaction with the View – how the view is changed. Because most GUI’s contain widgets or controls which already take care of user interaction (e.g. You can click on a combo box to change it’s contents) I don’t see any sense in having a separate controller. If anybody can show me how this might work and be useful then I would be happy to add this architecture to the framework.