kate part (was: Re: fileselector plugin)

[Christoph Cullmann]

Roland Krause wrote:
> 
> Yes!!! Cullmann, you are back from vacation... 6 weeks traveling in
> europe, what a joy to be a student ;-)
It was more 6 weeks fighting with an damn computer firm to get a new pc
(I HATE ALTERNATE !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!)

cu
Christoph

> 
> --- cullmann at moldware.com wrote:
> >
> > You are right ;)
> > To put the katepart into kdelibs, we must split kate into 2 parts:
> >  - the katepart consisting of (I hope I am right)
> >         kate/document/*
> >         kate/view/kateview.*
> >         kate/view/kateviewdialog.*
> >         kate/view/kateundohistory.*
> >         kate/view/kateviewIface.h
> >         kate/factory/*
> >         kate/interfaces/document.h
> >         kate/interfaces/view.h
> >         the most stuff in kate/data
> >
> >   - the kate app consisting of the other stuff ;)
> 
> Yes, I have only minimal knowledge of kate but that sounds very
> logical.
> 
> >
> > The katepart files should be moved into a libkatepart in kdelibs
> > to be avaible for other programs (like kate, kdevelop, konqui, ...).
> 
> Exactly, but will the older TextEditor interface not be better have
> tobe integrated into Kate::View and Kate::Document?
> 
> >
> > But one big problem with that: We must change how kate manage the
> > katedocuments/views.
> > Kate must use the BC compatible view/document interface and not the
> > kateview.h and
> > katedocument.h headers or kate won't work with different kdelibs
> > versions.
> 
> I dont think this would be that difficult to do, I have managed to do
> this for kdevelop and I guess we could do it again for kate. I am
> willing to help with this, if you help me making a Fortran highlighting
> style and a special Fortran background for the editor window :-)
> 
> No seriously, I dont think this is a big deal. The appropriate part of
> the kdelibs could be backported to KDE-2.2.
> 
> Roland
> >
> > cu
> > Christoph
> >
> > --- "F at lk Brettschneider" <gigafalk at yahoo.com> wrote:
> > > Roland Krause wrote:
> > > >
> > > > I think it is not a good idea to make kdebase a requirement for
> > > > kdevelop. The parts of kate that are essential for us (an
> > improved
> > > > kwrite/ktexteditor part) should move into kdelibs where they
> > > belong.
> > > > kate itself can then stay in kdebase.
> > > Why don't we move it NOW!?
> > >
> > > Ciao,
> > > F@
> >
> >
> >
> > --
> > | |   / /               - get an edge in editing -
> > | | / /                      »»»» GET KATE ««««
> > | |/ /      a fast and capable multiple document,
> > |     \     multiple view text editor for KDE
> > | |\  \     cullmann at moldware.com
> > | |  \  \   http://kate.sf.net
> >
> > -
> > to unsubscribe from this list send an email to
> > kdevelop-devel-request at kdevelop.org with the following body:
> > unsubscribe »your-email-address«
> 
> =====
> --
> Roland Krause
> In the garage of life there are mechanics and
> there are drivers. Mechanics wanted!
> 
> __________________________________________________
> Do You Yahoo!?
> Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger
> http://im.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«

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