KDEVELOP_1_4: move docViewMan

[Roland Krause]

Falk,

I figured the mail was intended for the list, so I quote in full, for
reference.

I want to move docViewMan into it's own library, but I believe we can
do this in steps. First lets make a folder for it, so I can put
additional files into this folder. 

Then, lets make a library, then wrap it into a kpart, finally then ...
project "mosfet" ;-) 

Anyway, we dont need the library right away, just the fact that I dont
want to create a set of 6 to 10 files additionally into the current
kdevelop directory. 

About the clean up. I am not sure, but there are a lot of docViewMan
slots, that are nothing but redirections of interface signals to the 
Kate::View interface. This is all obsolete since a kate part can be
connected to the corresponding signals directly. 

DocViewMan manages documents and views, that should be it. 

Roland


--- "F at lk Brettschneider" <gigafalk at yahoo.com> wrote:
> Hi,
> 
> Roland Krause wrote:
> > 
> > Falk,
> > is there any chance we could move docViewMan into its own folder
> and
> > make it a library?
> 
> It's hard. I think it's too much related to the core of KDevelop.
> Have a
> look at
> the files which it includes:
> 
> #include "ckdevelop.h"
> #include "kwdoc.h"
> #include "cdocbrowser.h"
> #include "doctreeview.h"
> #include "khtmlview.h"
> #include "ceditwidget.h"
> #include "docviewman.h"
> #include "./dbg/brkptmanager.h"
> #include "./dbg/vartree.h"
> #include "./ctags/ctagsdialog_impl.h"
> #include "ckdevaccel.h"
> 
> A separate library has got the property of being independent from
> stuff
> on a higher level. I don't easily see that possibility because of
> class
> dependencies back to the main program.
> 
> First DocViewMan must be independent from CKDevelop, DocTree*, and
> /dbg/*.
> This isn't possible with the current state of art. DocViewMan must
> become more generic. As I often said in previous emails by using the
> signal/slot-mechanism to get a uni-directional dependency between
> classes.
> 
> Checkout the very first CVS versions to get such a generic
> DocViewMan.
> The dependencies to KDevelop were introduced later when we moved all
> the
> stuff from CKDevelop to DocViewMan. I wasn't really happy with this
> development but after all it was a good decision for KDevelop-2.0.
> 
> Moving stuff of CKDevelop again out of DocViewMan is the only chance
> to
> get a clear interface.
> 
> > 
> > Would be a real nice cleanup ;-)
> > 
> > Roland
> Ciao,
> Falk
> 
> 
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
> 

=====
--
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
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«