[wx-dev] mixing wxMac/wxCocoa

[Stefan Csomor]

Hi
> On Wed, 07 Nov 2007 12:31:01 +0100 Stefan Csomor <csomor at advancedconcepts.ch> wrote:
>
> SC> ok, I'll try to do this at 
> SC> http://www.wxwidgets.org/wiki/index.php/Development:_wxMac64
>
>  We've made a lot of progress (61 versions) since our discussions of wx3 ;-)
>   
yes, we should perhaps add banner ads - or offer search from a wx about 
dialog - to fund development ;-)
> SC> - Core... Frameworks
>
>  If I understand this correctly, it means that if we use C API for any of
> the frameworks, there is no problem in making the code work in both wxMac
> (32 and 64) and wxCocoa, even if the framework is a GUI one? E.g., just to
> take an example, how would we wrap the new Core Animation in such way that
> it could be used in both wxMac and wxCocoa
>   
CoreAnimation unfortunately is dependent on NSViews so this cannot be 
made work, but eg the new CoreText Framework works well for Cocoa and Carbon
> SC> - HIToolbox
> SC> 
> SC> the HIToolbox has been removed from the supported headers for 64 bits, 
> SC> so while I've had a 64 bit version running of wxMac at WWDC 2007, things 
> SC> don't build anymore with the release version of Leopard. Therefore the 
> SC> future of the wxMacControl class hierarchy which right now is my native 
> SC> counterpart will be to become a switchable native implementation. I hope 
> SC> this could be a future path for a 'generic' wxWindow... and pImpl 
> SC> 'wxPeers'.
>
>  AFAIK we can't do this with the current wx API. So maybe this change will
> finally be the necessary impetus to really do something about wxTNG...
>   
wxMacControl and wxWindow and subclasses are still too much 
interdependent (eg native event callbask occuring directly in the 
wxWindow instance), so cleaning this up step by step will be necessary, 
but it will be at least one stone in the mosaic ...
> SC> The fact that a HICocoaView exists as bridge, helps to test things.
>
>  But won't be enough to make them work in the long term?
>   
it will allow to use the latest cocoa views in 32bit mac, to replace 
implementations piece by piece, but it won't be enough for 64bit and 
neither will allow core animation AFAIK, so it only helps as a bridge

Thanks,

Stefan