On May 22, 2008, at 1:01 AM, Michal Rudolf wrote: > Garth Corral, czwartek, 22 maja 2008: > >> I don't think its an issue of one or the other. I can't speak to the >> case of the options menu but I think there are at least as many >> instances as not where cleaning up the UI would not add a step to the >> migration to 8.5 because there would be no new widgets offered by 8.5 >> for that particular task. In that case the work would already be >> done >> at the time of migration and there would be nothing further to do >> afterward. Unless you plan on replacing every single widget or >> control in the application, of course, in which case I'm wrong. > I think this *is* a case here. The widgets need to be changed to 8.5 > ones, > which can be done automatically, but only if there were no tuning > done to > those widgets. If I understand things correctly, widgets which use > some > parameters to tweak their look or feel, will require some small but > manual > code changes. > Well, it sounds to me like this is a done deal. Might I suggest at least branching the repository such that maintenance of 3.6.x can occur without disruption on some branch? I'd like to at least get to the point where I can build installable binaries of scid for folks who just want to get up and running with 3.6.x. Then if someone wants to they can merge it down to the trunk at a later time and extend it to package with tcl and tk and whatever else is needed for the whizzy new version. Possibly this could be targeted for some non-3.6 release?
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Scid-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/scid-users
