Duncan Gibson wrote: > I've always been a dyed-in-the-wool vi user and stayed away from these > new-fangled development environments. However, I'm toying with the idea > of trying out kdevelop for a small application because it appears to > bring together coding, documentation via doxygen, and build management > using autoconf, automake and libtool. > > Has anyone used kdevelop with fltk and fluid? Any advice, tips, tricks?
OT... In my opinion, the only useful feature of these IDEs is "code refactoring" (aka: projectwide, context-sensitive renaming), but kdevelop is lacking in this regard. If you use fltk (or projects without QT-moc requirements), there is no real gain. I'd suggest against using the kdevelop project management entirely if you want to target windows or cross-build easily in the future. vim, with sessions, directory buffers, quickfix, omnicomplete and cbrowse does 90% of what kdevelop does and much better. There is no "project management" though, but by working with sessions this is hardly a problem. I tried several IDEs in the years (including xcode, vs, devc++ and code:blocks recently), still, my favourite is RHIDE (a borland builder clone), just because it is barebone. Yet, both vim and emacs are superior in many, many ways now. _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
