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

On Saturday 20 July 2002 12:28, Joseph Wenninger wrote:
> 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).

Me too :-((((. It have been useless since the new view architecture, and that 
should be done something about - I just didn't fugure out what up to now:-\

Note, I didn't try your updated code yet. This is only thoughts.

> 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.

I don't think atm, but I was considering a method to find a document object by 
URL in the dcop interface /for mainwindow). Still it would not crach I think, 
just dcop would complain that the related interfaces didn't exist in case 
they were used prior to the document beeing loaded. The dcop user would have 
to make sure that the document would be open.

> 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.

Well, so far I added a method int currentDocumentIfaceNumber() to the dcop 
interface for KateMainWindow. It can be used to construct the interface names 
(if you can figure out the naming) for the active document. See the sample 
script in the initial message in the "Scripting Update" thread.

A dcop method, int KateMainWindowN.findDocument(URL) is one of the next things 
I consider.

As for selecting one out of more views for a document, that is currently not 
usefull. The active view would be usefull, for the (few, so far) interfaces 
that is owned solely by the view. For selecting a specific view for a 
document other than the current one beeing meaningfull, we would have to keep 
track of the latest active view pr document - that is the only thing I can 
think of.

-anders