Wow. My head is just not geared toward writing a blog any longer. But I will model through it.
This choice is not without its pro's and con's. The pro's win for me for applications with these characteristics:
- At least one display screen greater than 10 inches, i.e. typically used on more than a tablet or phone
- A good bit more data than would easily fit on a single page, and complex relationships throughout
- More than a few operations on that data, with a good bit of keyboard input
Because Cappuccino provides an HTML view, this is not a total loss. I've not done much with this yet, but the "con" seems to become a "pro" by allowing for applying HTML and CSS when those mechanisms are the best fit.
I came back to Cappuccino after frustration with manipulating HTML and CSS to do my bidding. I don't have any great need for the kind of styling afforded by HTML and CSS. (And with the fallback to an HTML view as per above, even less so.) Most of what I need can be provided satisfactorily using the traditional GUI views going back to Smalltalk-80's MVC.
Cappuccino's class documentation is good, because the API and documentation is already 25 years mature. Tutorials and examples are good, growing, and fortunately supplemented by Cocoa material when the Capp material iteself is lacking.