with SF Symbo apple also takes this route
But, I think we should try to create all the Aristo 3 components that exists in Aristo 2 first.
I think we need to focus so Aristo 3 can be completed.
@didierkorthoudt sorry. it is well centered. it was my fault.
@jasperdeb I’ve found the origin of the split view problem… Must now find a solution. (FYI, in your specific case, when you call
setPosition, subviews are not yet laid out, so the method fails to work correctly. It even sets the height of the second view to -155, which is bad 😉)
@jasperdeb Fixed. I’ve pushed a new build at https://github.com/cappuccino/cappuccino/wiki/CSS-Theming-&-Aristo-3-:-Work-in-progress#2019-09-05 so you can test it on your own application.
Please note the following things regarding « modern Cocoa » split views :
- You should not use
[splitView addSubview:aView];but[splitView addArrangedSubview:aView];instead ; - After adding all your views to the split view, you must call
[splitView adjustSubviews];before doing anything else with the split view ; - You should avoid using
[splitView setIsPaneSplitter:YES];which is deprecated, but use instead[splitView setDividerStyle:CPSplitViewDividerStylePaneSplitter];
Another thing in your reduction : I see that you use CPScrollView as split view subviews… I don’t understand why. You should use simple CPView instead as the tables have their own scroll views…
Please let me know if everything works fine now...
Thank you! Some of the code is maybe not as it should but it is self taught and as it works this way, the code is copied from that moment on :-) I will put this build into the A3 version of the app I have made the tests on. As my wife uses this app for her business, I will ask her to use this version from now on and see or something else comes out. If not I will start to convert something bigger (with more widgets) in the comming weeks to stretch A3 further.
Would it be an idea to add something to the wiki where users (as me) can make a summary from the issues/code conversion needed (as with the splitview) while making the transition to A3?
something yet to be done is the CPDateTimePicker?
great work!
@jasperdeb everyone’s code is embarrassing when looked at after the fact :-) One of the greatest problems I’ve found with Cocoa development is the absence of example code for non-trivial large-scale apps, particularly to inform strategies for modularity and high-level structure. I would love to see the code behind OmniGraffle, Create or Numbers. I know of no teaching resources better than the Big Nerd Ranch books and they don’t offer much if anything concerning structure for large-scale apps. There has lately been good discussion of the use of co-ordinators for managing complex view/controller hierarchies but it still is a matter of experience and perserverance that gets the job done.
Fwiw, Apple’s just-released Music web app uses Ember (a Sproutcore derivative) and OmniGroup’s OmniFocus for the web uses React. If anyone is a candidate for Cappuccino one would think it’s those two.
