Hi Rui, On 31/01/2014, at 9:23 AM, Rui Pacheco wrote:
> How did you factor out the application logic from the UI rendering? If you mean our application logic, it essentially comes down to abstraction. The application is C++ and sits on our application framework, similar to Qt or wxWidgets. The application framework is also mostly C++ and it mainly uses a bridge pattern to interface with platform specific back ends. On the Mac this back end is Cocoa (Obj-C++), on Windows it's Win32 and on Linux the UI specific parts are empty as the app runs as a CLI render node. The application itself has no knowledge of the underlying API. Well, that's not entirely true as the framework is designed to be "thin" so the application can get to platform specific stuff if need be, but that's the idea anyway. All UI elements are created programatically, so we don't use nibs on the Mac. In fact I do use IB to design the Mac interface when needed but I have a tool which generates an XML file from the nib, and the XML file is parsed by the framework to generate the UI. It's a bit old school but I use IB 3 and a Carbon nib for this, as that is sufficient for my needs. It does mean I have to do some tweaking to account for layout differences at times. Regards, Jo Meder _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
