On Mon, 24 Mar 2008 16:02:43 +0000, "Eric Y. Kow" <[EMAIL PROTECTED]>
said:
> So, now that 0.10.3 is out, what is the fastest way for us to get
> wxWidgets 2.8 support so that MacOS X Leopard users can run it?
I need to port my wxWidgets 2.8 changes on top of 0.10.3. I started this
last week, and it won't take too long.
There are a few caveats, however, and (at least as I've implemented)
these break compatibility. Note that it seems like the 2.4 compatibility
mode which we have been using with wxWidgets 2.6 seems to be broken (not
unreasonably) in a few places in 2.8 (it's officially unsupported now).
What I have is based on 'raw' wxWidgets 2.8 (I couldn't make 2.4
compatibility work, and it's cleaner to just work to the latest base).
Bottom line is that the update will not compile against wxWidgets 2.4 or
2.6. Don't think the loss of 2.6 compatibility is too much of an issue.
Loss of 2.4 compatibility means that we no longer play nicely with GHCi,
however.
I have some ideas on how to fix this, but it's far from trivial (do
'true' dynamic loading and unloading of wxWidgets DLL/.so/.dylib, which
will be very platform specific, but will ensure that C++ static
constructors and destructors work correctly, and can be called
programmatically).
Main (possibly compatibility breaking) differences from 0.10.3:
* In WX
o Instances of 'framed' (currently in WX.Frame) move to
TopLevelWindow
o Changed behaviour of bestSize attribute (in WX.Window) -
this is very minor, I think, and probably doesn't break
existing code.
* In WXCore
o topLevelWindowSetIconFromFile replaces frameSetIconFromFile
* In wxc
o wxGenericDragImage methods now require a wxPoint
o static wxBrush instances have changed to const type
o static wxColour instances have changed to const type
o static wxCursor instances have changed to const type
o static wxFont instances have changed to const type
o static wxPen instances have changed to const type
o wxTreeItemId_CreateFromValue() should be deprecated
The good news is that it looks as though much of what is needed in wxc
has been implemented (although I'll have to merge my changes as they
are, in some cases, different to what I had done (in unimportant ways).
In general, I'll keep what is already there if it works.
I can try to get this merge done in a week or so, if that's OK. I'll
have time to verify on one platform only (probably Windows), but better
to get the changes in.
I think we need to have a general discussion on whether it's acceptable
to break wxWidgets 2.4 compatibility. I think it is, and that we should
just direct those needing this feature to the 0.10.3 release.
Regards
Jeremy
-------------------------------------------------------------------------
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/
_______________________________________________
wxhaskell-devel mailing list
wxhaskell-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
