Future of NEdit?

[Scott Tringali]

Thorsten Haude wrote:

> I don't quite understand what you mean by rehosting. You don't have to
> commit to a particular platform, do you? That's the point, isn't it?

Based on my reading, when you make a wxWidgets build you decide whether 
it will target GTK or Motif as the underlying toolkit.  That's what I 
mean by hosting.

> We might as well switch to wxRuby while we are at it. That would make
> things really simple.

Two reasons.  1) Ruby can't compile C code, whereas C++ can.  2) Cool as 
Ruby is, it's not installed everywhere like C++.

> Some of us work in environments where getting GTK, Qt, wxWigets, etc.
> installed is impossible because of corporate policy. Changing to another
> toolkit would have the effect of making a new NEdit unusable. We would
> have to stick with the latest Motif version.

Two things here.  wxWidgets can target Motif.  So, it is only the 
addition of one layer - nothing comes for free.  Just like Motif was on 
Linux, wxWidget could be probably built in static.

The other solution is to fork internally, and let pure Motif sit in 
maintenance mode forever.

Thems the breaks. We can't move forward on Linux and stay compatible on 
AIX at the same time without some tradeoff.