cappuccino

MOVED TO https://github.com/cappuccino/cappuccino

Explore on GitHub Read Hacker News discussions

9Distinct people

13Mentions

0Explicit recommenders

45GitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

MOVED TO https://github.com/cappuccino/cappuccino

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 10:49:33 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year13 dated mentions

Observed mentions: 2008-09-04 18:06:45 UTC to 2011-07-18 19:20:22 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Submissions	Comments
2008	2008-01-01 00:00:00 UTC	2009-01-01 00:00:00 UTC	3	0	3
2009	2009-01-01 00:00:00 UTC	2010-01-01 00:00:00 UTC	0	0	0
2010	2010-01-01 00:00:00 UTC	2011-01-01 00:00:00 UTC	4	0	4
2011	2011-01-01 00:00:00 UTC	2012-01-01 00:00:00 UTC	6	1	5

What Hacker News says

4 sources

paulbaumgart·Oct 13, 2010

It depends on how complex your front-end is. As you put more logic on the client-side, the chance of some of that code being useful on the server-side grows. For example, the Objective-J compiler and loader system ( http://github.com/280north/cappuccino/tree/master/Objective-... ) runs with almost no modification both in the browser-- for on-the-fly compilation during development-- and from the command line-- for pre-compilation prior to deployment. (As an aside it runs on Narwhal, not Node.JS. But the point stands.)

In Why Node.js Is Totally Awesome

paulbaumgart·Aug 24, 2010

http://github.com/280north/cappuccino/blob/master/AppKit/Cor... But if you don't like a particular part of the abstraction layer provided by Objective-J/Cappuccino, you're definitely free to use raw JavaScript. Just like in Objective-C you're free to use structs, function pointers, and C-style arrays.

In Motorola Snaps Up 280 North (YC 08) For $20 Million

tlrobinson·Apr 22, 2010

The title is incorrect, the broken features have nothing to do with HTML5. These features haven't been removed entirely, but as I found when I tried to add them to Cappuccino some of them are very buggy (http://github.com/280north/cappuccino/blob/master/Tools/capp... and http://github.com/280north/cappuccino/commit/9f50f0806528d03...). "apple-touch-icon" and "apple-mobile-web-app-capable" work as expected, as do HTML5 cache manifests. Setting the viewport meta tag to "initial-scale=1.0, user-scalable=no" also works as expected, which is what I needed to get Cappuccino applications to display correctly (this is probably what you want for most JavaScript "applications"). I didn't try any other configurations. This works in both MobileSafari and applications saved to the home screen. I tried "apple-mobile-web-app-status-bar-style" with "blac

Read the rest

k" (default) and "black-translucent", both seemed to work for me, but I stuck with the default. The biggest problem is with the default image, i.e. "apple-touch-startup-image". For some insane reason it expects the PNG to be 748px wide by 1024px tall. This aspect ratio implies the image should be portrait oriented, yet the 20px for the status bar is taken from the narrower dimension, implying that it should be landscape oriented. And in fact the image is scaled from 748x1024 to 768x1004. There is no way around this AFAICT. Original default.png image: http://cl.ly/JCs Displayed in portrait orientation: http://cl.ly/IyM Displayed in landscape orientation: http://cl.ly/Ibx The only way to get something reasonable is to squash your default image in the opposite direction. That is, start with a 748x1024 image, crop it to 768x1004, then scale it back to 748x1024. Unfortunately then you end up with a white bar along one edge in landscape mode. Madness. If I'm mistaken about any of this I'd love to know.

In HTML5 webapps broken on the iPad

tlrobinson·Apr 1, 2010

(don't miss the code: http://github.com/280north/cappuccino/commit/6678bba94f7778b...)

In Solving the JavaScript Memory Management Problem