Using VIM as the text editor in KDevelop

[Christian Couder]

On Thu, Mar 22, 2001 at 08:45:36AM -0800, Roland Krause wrote:
> 
> --- Christian Couder <Christian.Couder at fr.alcove.com> wrote:
> > I agree. There is already a kvim app in kdenonbeta. The "big dream"
> > is to 
> > make a KTextEditor library interface and make some kvim, kwrite and 
> > kemacs parts that can be used through this interface.
> 
> I thought so, we should maybe figure out and formulate an interface to
> a KDevelop texteditor component. I am currently reading up on kparts
> and DCOP and it looks like it should be fairly simple once we decided
> what is needed. 

If you want you can do it, but it will be for KDevelop 3.

> > There is also a kwrite-devel mailing list where people are working on
> > this stuff. They improved the kwrite code and made a component called
> > "kant" the new kwrite will use kant through a probably improved
> > texteditor interface.
> 
> I was under the impression that kant is the kwrite successor. Is that
> true? Then why are they implementing project management and stuff like
> that? 

I think you should ask on the kwrite devel list. Currently nobody is
working on this for KDevelop. 

> Also one of kant's major selling points is that it is an MDI
> editor. How would that integrate with kdevelops own MDI interface, aka
> the DocViewManager? 

If we use the kant component with it's own MDI interface, we won't need 
to use the QExtMDI framework.

Bye,
Christian.


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