KATE: mysterious, secretive kate...

[Roland Krause]

Friends, Christoph (X-fire) in particular,

I dont understand what the kate interface is supposed to be. There are
a few header files that get installed with kate of which two looked
particularily interesting: view.h and document.h. 

But the stuff in there is, as an interface pretty much unusable. Or
more likely, I dont understand what this is supposed to be about. 

For one thing, why would I want to interface with Kate::View instead of
KateView (resp. Kate::Document and KateDocument)? These seem to be some
kind of base classes that arent very particular and only seem to
provide half (or less) of the functionality of their discrete
counterparts. 

Also what I dont understand, if I create an object of type Kate::View
all the methods have empty implementations, it looks like something is
supposed to be derived from these and then virtual overloading is
supposed to happen but the classes arent virtual at all.

Another problem seems, that I wanted to derive from KateView. So my
derived class would gain access to the protected members of KateView
(like myDoc). Now you may think what you want about that from a
stylistic point, but that seems to be another showstopper. I cant get
access to the low level stuff. 

Maybe I have overlooked something here, but I dont quite understand the
reason behind this, why not making kateview.h and katedocument.h
available instead? Please enlighten me. 

Roland

=====
--
Roland Krause
In the garage of life there are mechanics and 
there are drivers. Mechanics wanted!

__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35 
a year!  http://personal.mail.yahoo.com/

-
to unsubscribe from this list send an email to kdevelop-devel-request at kdevelop.org with the following body:
unsubscribe »your-email-address«