> On 15 Oct 2019, at 18:27, Turtle Creek Software via Cocoa-dev > <cocoa-dev@lists.apple.com> wrote: > > MVC is an excellent design paradigm. The M and V layers were no problem at > all to set up. The C started out easy, but ended up being a big problem. > Quite a bit of the business logic is not just data, but fancy stuff that > happens with the GUI. Fields that switch between % and $, table cells that > change other table cells, etc. There is a lot of code in our C++ > RecordViewer classes to make that happen, and it didn't integrate easily > with NSWindowControllers or NSViewControllers. It often was faster to just > redo the logic in Cocoa. That took a lot of time. Much more rewriting than > expected.
If the RecordViewer is a controller of some kind, could you not add it to a view controller, and let the view controller (an ObjC++ subclass of NSViewController) call the RecordViewer to make these changes? It sounds like you actually made quite a bit of progress if you’ve already rewritten the View (V) layers, and the Model (M) layer is separate. Jeremy _______________________________________________ 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
