Hi all, Just my very humble opinions on the future of NEdit. Programming language wise, I would suggest sticking with C. The NEdit codebase is relatively small, and while the code could be a little more modular and have a stronger abstraction layer between documents being edited and their display, this doesn't immediately suggest something like C++ is a necessity. As for the toolkit, it has been obvious for a long time that Motif is an anachronism. It relies on Xt, which has proven to be pointless (as I recall, it was supposed to be a generic layer that many toolkits would be built on) and neither Xt or Motif has hept up with internationalisation features considered essential these days. Porting to a more modern toolkit, with better licensing, greater install base and greater functionality is the single most important thing to me. The debugger frontend, DDD, is the only other Motif application I use, and a major attempt to port it to GTK+ has been undertaken. If I had the time, then I would love to take the approach taken with DDD, and attempt to apply it to NEdit. If the editing component in NEdit could be ported to Xlib (in other words, any Xt Intrinsics dependencies removed), and the remaining interface ported to GTK+, then I believe it would make NEdit a far superior editor to alternatives such as Anjuta, Kdevelop, Kate or GEdit.
Regards, Chris -- NEdit Develop mailing list - [email protected] http://www.nedit.org/mailman/listinfo/develop
