Please tell me, if I broke something concerning dcop interface functionality

Hi

To speed up application startup I removed a lot of view creation in the case 
the view configuration shouldn't be restored. (which crashes for me anyways). 
It basically behaves like the new filelistloader plugin and creates only a 
view for the really displayed one. Closing all documents and shutting down 
the application is still a littlebit slow, since it seems to create a view 
for a document, if none exists, just to delete it the second after the 
creation.

Please tell me, if that new startup behaviour  is very bad concerning the the 
kate app dcop interfaces. I'll have to find a work around than.

What about a dcop interface for the documentmanager/katemainwindow. Which 
returns all documents and allows returning the active or any  view of a 
document. If it doesn't exist it should create one. I think that would be the 
easiest way to implement.

Kind regards
Joseph Wenninger

PS: Even view creation, without pluggin/unplugging XMLGUI components makes 
startup a lot slower