class KDevelop

Sandy Meier smeier at
Wed Jun 14 20:49:07 UTC 2000

On Wed, 14 Jun 2000 you wrote:
> Falk Brettschneider wrote:
> > 
> > Hi Ralf,
> > 
> > What's better in your new approach? What do you want to do?
> I´m currently implementing CKDevelop from scratch as KDevelop and then
> want to put it to CVS when the UI is complete and the normal slots that
> are called by the UI are in at least as frame functions. Then we´ll go

If you get it to work I think it would be cool :-) At the moment there are
many problems with the current UI,for instance the keyboard accels are
"totally" broken. Nevertheless the MDI stuff works. :-)

But I have an other question: If we want to support more languages such 
fortran, Python,PHP,HTML... we need to implemenent many views  and components as
plugins. (treeview, new class dlg,plugins without a view.....). Should we use
KParts for it or just normal C++ plugins with our own Plugin Baseclass? Are
there disadvantages with KParts? Maybe KParts si only designed for embedding
applications/documents and not for small plugins like a appwizard plugin?


email: smeier at  ICQ: 27681958
the KDevelop project:

More information about the KDevelop-devel mailing list