Hi!
>> 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.
THEN this is not just a UI polishing, but a complete new
version. At that point one should call it scid 4.x...
(Just to make it also clear to the users.)
> 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.
Then it could also be wrapped in some functions that decide
on version basis. Anyway, have fun...
But I'd really do this in a new major and not within the
micro versioning of 3.6.25 or something.
--
Kind regards, / War is Peace.
| Freedom is Slavery.
Alexander Wagner | Ignorance is Strength.
|
| Theory : G. Orwell, "1984"
/ In practice: USA, since 2001
-------------------------------------------------------------------------
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
