• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Cocoa-dev Digest, Vol 16, Issue 72
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cocoa-dev Digest, Vol 16, Issue 72


  • Subject: Re: Cocoa-dev Digest, Vol 16, Issue 72
  • From: Turtle Creek Software via Cocoa-dev <email@hidden>
  • Date: Mon, 26 Aug 2019 21:22:19 -0400

>> Again, why does cross-platform code need to have references to
platform-specific view/controller types?

There are links between each Cocoa control class and its matching C++
control (which also owns a native MFC control).
Also links between the view and our C++ controller, to load window layouts
and set up the control links.
A couple utility links for showing progress bars, log window, etc.

Running a business is complicated: there are about 150 different window
layouts in our app.
Payroll alone needs 15-- employee hours, tax tables, vacations, holidays,
benefits, tax agencies etc etc.
Most have some quirks- fields enable/disable or change from % to $, totals
update, values get posted elsewhere, etc.

Writing generic code to still use our C++ controller classes and window
layouts was much easier than
building and testing 150 NSViewControllers.  It took a month or 2.  A full
rewrite would have been
a year, plus many new bugs, plus two separate code bases to maintain.

Casey McDermott
www.SmartKnives.com




On Mon, Aug 26, 2019 at 5:06 PM Jens Alfke <email@hidden> wrote:

>
>
> On Aug 26, 2019, at 1:15 PM, Turtle Creek Software <email@hidden>
> wrote:
>
> Our C++ is cross-platform.  More importantly, we have a LOT of accounting
> and business logic in C++.
> To rewrite and test it would be 5 or 10 programmer-years.
>
>
> I can understand the model and some of the controller logic being
> cross-platform, but why do you need the cross-platform code to have
> references to Obj-C classes? It's a cleaner separation to have the
> GUI-related code be in Mac-specific Obj-C++ classes that can refer directly
> to Cocoa.
>
> We never found any way to have Obj-C members in C++ header files, except
> as void *.
>
>
> Again, why does cross-platform code need to have references to
> platform-specific view/controller types?
>
> —Jens
>
_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Cocoa-dev Digest, Vol 16, Issue 72
      • From: Jens Alfke via Cocoa-dev <email@hidden>
References: 
 >Re: Cocoa-dev Digest, Vol 16, Issue 72 (From: Turtle Creek Software via Cocoa-dev <email@hidden>)
 >Re: Cocoa-dev Digest, Vol 16, Issue 72 (From: Jens Alfke via Cocoa-dev <email@hidden>)
 >Re: Cocoa-dev Digest, Vol 16, Issue 72 (From: Turtle Creek Software via Cocoa-dev <email@hidden>)
 >Re: Cocoa-dev Digest, Vol 16, Issue 72 (From: Jens Alfke via Cocoa-dev <email@hidden>)

  • Prev by Date: Recommendations for cross platform library/framework
  • Next by Date: Re: Recommendations for cross platform library/framework
  • Previous by thread: Re: Cocoa-dev Digest, Vol 16, Issue 72
  • Next by thread: Re: Cocoa-dev Digest, Vol 16, Issue 72
  • Index(es):
    • Date
    • Thread