A new IDE for a new milleneum :-)

[Christian Couder]

Bernd Gehrmann wrote:
> 
> So what do I have now? First, a modular lego-like framework for an IDE
> that could be used to build a C++ IDE, a Python IDE, or even a web
> development platform (no, I'm not suggesting the latter ;-) In the
> second place, a number of 'part's that make use of the framework and
> form a complete C++ IDE. That is:
> 
> The core application: a kwrite-based editor and a khtml-based
> documentation browser. Any number of views per document can be
> arranged in a grid of non-overlapping windows (in the tradition
> of Emacs and Konqueror). The editor supports incremental search.
> Files can be loaded by a KURLCompletion line edit, without popping
> up annoying dialogs. To edit header file foo.h, just move the cursor
> over a #include "foo.h" and choose 'Goto include file' from the
> context menu. To look at the manpage of printf, move the cursor
> over printf and choose 'Goto manpage' from the context menu.

Hi Bernd,

Isn't what you call "the core application" just some kind of
"docviewmanager" like we have in KDevelop 2 now ?

I mean would it be possible to separate the core application from the
document and view management ?

So that for example we could use the docviewmanager from KDevelop 2 ?

We could perhaps even make a KPart from the KDevelop 2 docviewmanager
and make the core application use such a KPart ?

You know, I think people will keep asking for being able to use other
editors until we get something like this that make it possible to
separate the editor/documentation from the core application.

Bye,
Christian.

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