You may actually have some luck running those older programs in WINE. Just
a thought. :)
Well, in actual fact, I have found some (64 bit) replacements for these old legacy programs. So I suppose it is fair to say that I have moved on. However, I am now faced with the fact that I do a great deal of switching back and forth between two machines, one of which is an old (32 bit) XP, and one is (64 bit) Win10, and the switch itself is sometimes painful. My main point was simply that change for the sake of change is not necessarily a good thing. Witness, for example, the fact that the new gtk3 gui in Inkscape trunk is virtually unusable, and will probably take years before it is ready for public consumption. (And incidentally this type of work, fixing a gui, is extremely boring, which means it will be hard to find people who are interested in fixing it.) And witness the fact that we have replaced the old Windows btool compile system with CMake, which is very clumsy to use, takes about 10 times longer to compile than btool did, and is virtually impossible to keep in sync if you start messing with the code base, fixing bugs and so on. These problems can all be dealt with, if one has patience, but they make life so complicated that one is, finally, tempted to just give up in frustration.
Alvin
-- View this message in context: http://inkscape.13.x6.nabble.com/Roadmap-for-Inkscape-0-93-on-Windows-GTK3-d... Sent from the Inkscape - Dev mailing list archive at Nabble.com.