matthiasm wrote:
>>> For my money, if we are going to break the ABI with the utf8  
>>> stuff, we might as well break it properly...
>>>
>>> Like, I'd really like to see the win32 winsock switched to  
>>> winsock2...
>> +1
>>
>> FWIW, I'd like to drop support for Windows 95/98/Me and add support
>> for Windows CE/Windows Embedded (which only provide Unicode APIs)
>> and Windows Vista (which drops support for some older APIs like
>> winsock...)
> 
> +1 on both.

        Yes, +1 on ditching the non-multiuser windows (95/98/me),
        and I suppose +1 on the ABI rfe/bug stuff, assuming none of
        those slow the utf8 release.

        I'd only caution you kinda want that utf8 merge to go out quickly,
        otherwise we'd again get out of sync with the release stream
        if the ABI tweaks cause a delay.. anticipating Murphy's Law and all 
that.

        A 'treading more carefully' approach might be to make a quick
        1.2.0 release of just the utf8 merge, followed quickly by 1.3.0
        that has the rest of the ABI tweaks.

        But maybe that's treading too carefully/unnecessary, not sure.

> You will not be able to drag me into buying Vista yet, though.

        I have Vista here; had to buy it for testing, and to anticipate
        customers who will eventually jump on it. $399 USD! Grr.
        Well, at least the compiler is now free ;) But I can tell you
        Vista is NOT worth $400.

        I can say that all my 32bit FLTK and non-FLTK apps compiled
        on the old compilers work fine in Vista and Vista-64 unmodified;
        these are FLTK console and windows apps with threads (no opengl)
        and services.

        So for the most part, Vista is acting very much the same as XP/2K
        from beneath the slick desktop. Only the UAC (Universally Annoying Crap)
        is fairly intrusive at the low level, but that mainly affects only
        software installation.

        Although I have Express on Vista, and can compile OK from the command
        line with it, I'll be sticking with the old faithful VisualStudio 7
        for builds, because the newer compiler's 'manifest' stuff is a bit
        complicated.
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk

Reply via email to