join efforts with XNEdit, there Unicode, modern Open/Save dialog, Drag&Drop...
Brought to you by:
tringali
Menu
▾
▴
#135 join efforts with XNEdit, there Unicode, modern Open/Save dialog, Drag&Drop of tabs, antialiased text rendering
please join efforts with XNEdit, there Unicode, modern Open/Save dialog, Drag&Drop of tabs, antialiased text rendering
https://github.com/unixwork/xnedit
I'm happy to. However, there are an unknown number of forks out there, and they should contact me directly.
I saw in that fork there is continue developing, so it is really promising
@efa My efforts are towards Nedit-NG which after discussions with @tringali is planned to eventually become NEdit 6.0. (Life has been busy, but we'll get there).
NG has many of the features xnedit has as it is a full port to Qt. The main differentiator is that xnedit has unicode support. I am intentionally not persuing that goal until after it is ready to be called "NEdit 6.0" as the goal of NG is to be a near perfect, drop in replacement for NEdit 5.x just with a modern UI and improvements under the hood.
I would love to work with xnedit, as they are doing great work, and there is probably some collaboration to be had. That being said, I think the big picture goals are a bit divergent as xnedit is continuing with motif and X, while NG is moving on to a more "modern" look and feel as well as native cross platform availability.
I saw current NEdit support VMS, SGI, HP-UX, AIX, Solaris
Did you plan to support these platform too with NEdit 6.0?
At least macOS, Linux, Solaris, net/free/openBSD ?
Last edit: efa 2022-01-28
It may be worth doing both. Getting xnedit into distros right now as a 6.0 seems like a good idea to me while we work on nedit-ng at either 7.0; or rename nedit to nedit-classic and give nedit-ng the full name.
@efa, neditNG supports all platforms which Qt supports. this is at a minimum, Windows, Linux, and macOS. but in practice most unix-like OSes as well, including various BSDs. it's a highly portable library, i think even a Haiku port works, LOL.
@tringali, I am kind of of two minds about your suggestion. of course I love the idea of reinvigorating the base and Nedit community by getting a 6.0 release out. but my only concern is that xnedit and NG are on somewhat divergent paths from a common ancestor. what happens when NG is ready for 7.0 (or whatever) but xnedit wants to continue development? is xnedit forever 6.x? even if they start to develop brand new features? and what if xnedit starts to implement features that NG doesn't plan to have? should NG be required to implement them since it would be a "newer verst of nedit"?
I'm not entirely against the idea, I just think it can get complicated very quickly (and NG is SO close!)
Last edit: Evan Teran 2022-01-28
@tringali, after re-reading your suggestion. i can say that i think yhe idea of:
xnedit -> nedit-classic
NG -> nedit
makes sense to me and avoids most confusions since it makes it clear that classic is a continuation of the motif lineage while NG is a feature for feature port to create a new version
Last edit: Evan Teran 2022-01-28
Taking another look. Done some github admin at work so now I know a bit more.