This is the first in a series of articles where the community can showcase what they are doing with Cappuccino.
In this blog post I will briefly explain what we are doing here at Nuage Networks, why we chose Cappuccino, why we love it, and what we’ve done with it.
Here's a quick update on what's new with Cappuccino for the last two weeks.
Cappuccinoare now on http://gitter.im/cappuccino/cappuccino. Don't hesitate to come and ask whatever you want!
Cucappis now available in a sub-repository of
Cappuccino(https://github.com/cappuccino/cucapp). Thanks Daniel Parnell!
Here's a quick update on what's new with Cappuccino this past month.
xCodeCapphas been upgraded to version 3.1.
capp_lint) of the current project from
In this post I will explain how you can use the
jake command to build the Cappuccino documentation straight from the source. I will cover building both the HTML version of the source, as well as a DocSet version suitable for use in Dash or XCode.
After nearly a year's worth of work we are truly excited to introduce Cappuccino 0.9.7, a major update to the Cappuccino framework featuring a massive number of new features.
Since Cappuccino is such a wide framework, ranging from a low foundations such as our Objective-J compiler, all the way up to the full featured, fully themable UI kit AppKit, it's incredibly hard to summarise all the changes. But here's our best stab at it:
A common need for Cappuccino apps is the ability to upload files. Until now, the only native Cappuccino upload solution was DeepDropUpload by David Cann. While DeepDropUpload works, it hasn't been updated in two years, and it doesn't integrate directly with Interface Builder.
The new Objective-J 2.0 compiler has three components: tokenizer, parser and code generator. The merging of this pull request brought major improvements to the tokenizer and code generator.
The time has come to move Cappuccino to Node.js. Why move to Node? There are three main reasons: