kdevelop suggestions

[Massimo Morin]

Hi,
	I suggest not to mix too much graphic library and... motif is a hog
(resources and/or developing time)!!!
The best idea should be to port it to qt/kde.
A better idea could be to keep all the interface with gdb and port only
the data display window:
At the end everything should work as in the emacs mode: it uses emacs as
editor and gdb console, but it pops up the data window for the data
inspection.

I think it is a thought work but the benefits could be a lot: first of
all dump the source editing of DDD because the XmTextWidget sucks. The
use of Kedit (of kfte as someone shows interest) should be much better.
Second it should be less memory hog: when you run an application a
couple of time you grab at least 15Mb!!!
Third the interface with gdb seems more mature than kdbg.
Fourth well DDD is VERY powerful and having it integrated in kde will be
cool!

My 0.02$

Cheers
			Massimo

P.S.
Keep these as suggestions only: someone in the recent past said "Show me
the code!".... well I'm pretty code-less right now!!!!

"John R. Supplee" wrote:
> 
> >> Hi
> >>
> >> > - should integrate gdb support (kdbg is nice, but...)
> >> I suggest an integration/porting with DDD.... the data display is GREAT!
> >> (take alook at http://www.cs.tu-bs.de/softech/ddd/)
> >
> >The trouble with ddd is that is uses the Motif toolkit. :-(
> 
> Why is that a problem?  It compiles with Lesstif as well.
> 
> John Supplee

-- 
Massimo Morin        | Scheduling Systems Inc.
Software Engineer    |
-------------------  | Three University Office Park, suite 100
13, Charnwood Rd     | 95 Sawyer Road
Somerville 02144 MA  | Waltham,
-------------------  | 02453 Massachusetts
+1 (617) 623-4155    | +1 (781) 893-0390
mmorin at schedsys.com  | http://www.schedsys.com
----------------------------------------------------------------------
Never attribute to malice that which can be adequately explained by
stupidity.