Alright. If noone comes along, I'll explore both options, since this is currently blocking my GSoC work.
Keeping references to NSFont would also make writing UIKit-only, AppKit-free software impossible, so I'm currently leaning toward renaming Opal's NSFont and NSFontDescription to OPFont and OPFontDescription. On Sat, Jun 2, 2012 at 7:29 PM, Gregory Casamento <[email protected]>wrote: > None that I'm currently aware of. > > GC > > On Sat, Jun 2, 2012 at 1:13 PM, Ivan Vučica <[email protected]> wrote: > > Hi, > > > > Opal and AppKit both contain mutually incompatible NSFont > implementations. > > This means that my attempts to make use of Opal in an AppKit app are > failing > > miserably (and only at runtime). > > > > It may be wise if someone more experienced with both AppKit and Opal > would > > patch this. My current idea boils down to adding the few new ivars into > > AppKit, and to move any added methods into a category that'd ship as > part of > > Opal. > > > > This would have a bad side effect of making Opal dependent on AppKit or > > another library that implements NSFont. Since UIKit doesn't contain > NSFont, > > Apple's implementation obviously doesn't depend on NSFont. So, an > > alternative is to rename Opal's NSFont and explore what APIs would be > > broken. > > > > What free software currently uses Opal? > > -- > > Ivan Vučica - [email protected] > > > > > > > > _______________________________________________ > > Discuss-gnustep mailing list > > [email protected] > > https://lists.gnu.org/mailman/listinfo/discuss-gnustep > > > > > > -- > Gregory Casamento > Open Logic Corporation, Principal Consultant > yahoo/skype: greg_casamento, aol: gjcasa > (240)274-9630 (Cell) > http://www.gnustep.org > http://heronsperch.blogspot.com > -- Ivan Vučica - [email protected]
_______________________________________________ Discuss-gnustep mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnustep
