2008-03-02

 

it :: Office based on Model View Controler

How would Office look if consequently designed in a MVC (Model View Controler) style? What would it mean to the notion of a Office file format at all? What would it mean to shareing?

Let's have a short look into MS Office. The best example is tables. There are some in Powerpoint, Word, Excel, Access. Each controller (user interface) behaves different, the stored data is different (try to cut'n'paste one to the other and you will see). What is even worse is, that the user can not do the same things. Present nicely in Powerpoint but not calculate well, calculate in Excel, but not ensure data quality, ...

Well, the core software would have to retreat to define the major data model. This than can be extended by microformats and other. But the most important would be to have controllers that extend each other E.g. the upper issues in MS Office.

If now the data should be displayed in a very special form, today there is the selection of the respective spreadsheet software. But I think there are good reasons to let this be done by modules. E.g. the list is actually a genealogy. In todays ecosystems there is no way to interprete the table in such a new way. A new software has to be designed, even that 90% looks exactly the same like office.

Comments:
People should read this.
 

Post a Comment



<< Home

This page is powered by Blogger. Isn't yours?