kate part (was: Re: fileselector plugin)
rokrau at yahoo.com
Thu Aug 23 17:47:40 UTC 2001
We really need to coordinate this with jowenn and cullmann.
There is something about the whole thing that makes me think that
someone has to go and collect, stabilize and document the entire new
interface. That includes:
- the older texteditor interface (old kwrite stuff)
- my newer kate/kdevelop interface (Kate::View and Kate::Document)
- MHK's interface that he did for gideon.
Consolidation and getting an overview and documentation is what I would
do before anything else, this doesn't work without the current kate
--- "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
> > kate itself can then stay in kdebase.
> Why don't we move it NOW!?
> F at lk
> Do You Yahoo!?
> Get your free @yahoo.com address at http://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«
In the garage of life there are mechanics and
there are drivers. Mechanics wanted!
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
to unsubscribe from this list send an email to kdevelop-devel-request at kdevelop.org with the following body:
More information about the KDevelop-devel