Hi, Le 10 mai 2012 à 17:42, Al Chemyth a écrit :
> Hello, > I'm trying to port my application to EtoileUI, having the principal class was > subclassing ETApplication. But once I replaced NSApplicationMain with > ETApplicationMain, this problem raised. Although EtoileUI reuses various basic classes such as NSImage, NSFont etc., you cannot really port an AppKit application to EtoileUI, because EtoileUI has its own overall architecture that is the same than the AppKit. Many AppKit classes or rules are not valid when writing an EtoileUI application. So replacing NSApplication() by ETApplicationMain() won't work. You have to rewrite the UI almost from scratch. You can just reuse some Nibs with ETNibOwner and ETController. In the future, we will probably support reusing an existing AppKit view hierarchy packaged as a layout. For now, this last possibility might work but it is untested (you can try +[ETLayout layoutWithLayoutView:]). > 2012-05-10 15:38:59.014 3SUM[4259] DPSinvalidparam: Invalid gstate index > 2012-05-10 15:38:59.059 3SUM[4259] DPSinvalidparam: Invalid userobject index > 2012-05-10 15:38:59.059 3SUM[4259] DPSstackunderflow: Attempt to pop from > empty stack It's hard to tell what the problem is without a backtrace… If you could post one, that would help. However EtoileUI is currently broken because of CoreObject changes. I hope to fix the problem tomorrow. > The above methods were the only changes I made to the application. Is this > expected? Anyone is familiar with the problem or know where I should take a > peek? If your code is visible somewhere, I could take a look and give you some hints about how to rewrite the UI with EtoileUI. Cheers, Quentin. _______________________________________________ Etoile-discuss mailing list [email protected] https://mail.gna.org/listinfo/etoile-discuss
