Disqus - Latest Comments for boucher

Re: CappCon Tickets Now Available!

boucher — Fri, 27 May 2011 10:44:03 -0000

We're going to try to videotape the talks, yes.

Re: CappCon 2011

boucher — Sun, 24 Apr 2011 17:18:36 -0000

see http://groups.google.com/gr...

Re: GitHub Issues Update

boucher — Wed, 10 Nov 2010 12:50:17 -0000

Thanks, I've updated the link.

Re: GitHub Issues Update

boucher — Tue, 02 Nov 2010 13:03:59 -0000

You should file an issue in the 280north/issues github repo so that the current maintainers can take a look. Thanks!

Re: App Spotlight: PicsEngine

boucher — Sun, 24 Oct 2010 21:54:33 -0000

Cappuccino is an open source project with a large community of users and developers. The project will continue to thrive, and will never be controlled by any single company.

Re: GitHub Issues Cappuccino App: Desktop and Web

boucher — Thu, 13 May 2010 17:46:23 -0000

Depends on where/how you want to build it in. Send me an email (ross@280north.com) and we'll discuss.

Re: Introducing Jake: A Build Tool for JavaScript

boucher — Wed, 28 Apr 2010 12:19:12 -0000

Although it's completely unrelated to build tools, yes, we actually have ported Rack and the entire concept of middleware. It's called Jack, and you can read more at http://jackjs.org/

Re: http://taitems.tumblr.com/post/482577430

boucher — Mon, 29 Mar 2010 20:12:25 -0000

Looks great. Just to point people back to the source, you can find the Aristo PSDs on github.

Re: Internet Explorer: Global Variables, and Stack Overflows

boucher — Wed, 03 Mar 2010 18:15:09 -0000

Yeah, that's more accurate. It was kind of pseudo code already. I've made the change, thanks.

Re: Internet Explorer: Global Variables, and Stack Overflows

boucher — Mon, 01 Mar 2010 20:41:53 -0000

If you look at the code inside the function, you see we're recursing using the word recurse in both scenarios.

In the first scenario, recurse is a local variable. So, we recurse through a local variable.

In the second scenario, r is the local, and recurse is a global variable. Because there's no local recurse, just r, it goes up the global scope, to the recurse we defined by writing window.recurse = r;

That second scenario is the problem, because the recursion is now happening through the host object, the source of all our problems.

Re: XMLHTTPRequest, JSONP & Cappuccino

boucher — Fri, 04 Dec 2009 18:13:46 -0000

Ok got that one too.

Re: Just One File with Cappuccino 0.8

boucher — Thu, 12 Nov 2009 20:43:19 -0000

Cappuccino doesn't do anything with the server itself. So how reliable
those portions will be is completely dependent on how you code them.
It can be made exactly as reliable as any other web app, since
everything is using the same set of fundamental technologies. More
than likely you'd use an existing Comet library of some kind.

Re: Just One File with Cappuccino 0.8

boucher — Wed, 11 Nov 2009 14:48:03 -0000

See my reply a little lower. The benefits come because we compress lots of images in a single text file, increasing the amount of redundancy between them. It's like zipping up a folder of images versus zipping up one individually. The former is much more efficient.

Re: Just One File with Cappuccino 0.8

boucher — Wed, 11 Nov 2009 14:42:44 -0000

Also worth noting that it would probably still be worth it even if the size did increase by 10%, for the perceived speed benefit, and likely the actual speed benefit of reducing the http requests. It's harder to be exact about such things, but because of the parallel download limit, downloading 100 images individually becomes incredibly slow.

Re: Just One File with Cappuccino 0.8

boucher — Wed, 11 Nov 2009 14:40:13 -0000

Testing the images in one of our projects, it works out like this:

- 377 KB raw for all images
- 520 KB for base64 representations combined
- 303 KB for combined all base64 images, then gzipped

So, it actually saves a significant amount. Plus the savings of the HTTP request overhead.

Re: Just One File with Cappuccino 0.8

boucher — Wed, 11 Nov 2009 10:53:42 -0000

The code is all part of Objective-J and the tools, which don't require the framework itself. You could always use those in your project without using Cappuccino.

Re: Just One File with Cappuccino 0.8

boucher — Wed, 11 Nov 2009 10:52:46 -0000

It's trivial to either include code and images in one file, or beak them into two. More importantly, for most Cappuccino apps, it's easiest to cache and version the entire app, including images. But yeah, there's definitely a tradeoff between granularity of updates and reduction of HTTP requests.

Re: alert debugging — Mockingbird, Cappuccino, and what really matters.

boucher — Thu, 05 Nov 2009 01:54:19 -0000

Ken, you're right. We're very upfront about the fact that not everything makes sense as a desktop-class app. Cappuccino isn't designed to do everything, just this specific type of application. And we think that focus is one of the best parts of Cappuccino.

There's plenty of room on the web for pure documents, dynamic pages, and full blown apps.

Re: Using xCode to develop in Cappuccino

boucher — Thu, 10 Sep 2009 09:41:04 -0000

It's probably not compatible. You might want to try the newer plugin
that's in the github repository.

Re: Cappuccino Turns One

boucher — Tue, 08 Sep 2009 12:53:25 -0000

Still working on it. We'll make some more information available in the next month.

Re: Announcing Atlas

boucher — Wed, 08 Jul 2009 13:22:39 -0000

We're making progress. Not ready to make any new announcements just yet.

Re: Announcing Atlas

boucher — Tue, 30 Jun 2009 15:28:26 -0000

Pablo,

If you want to help, the best way is to contribute bug fixes to
Cappuccino. The github issue tracker is the best place to start.

We're not going to give a specific release date until we're confident
we will meet it. We'd rather ship good software a little late than
buggy software on an artificial deadline.

Re: Import Existing Presentations

boucher — Sat, 20 Jun 2009 13:44:14 -0000

dekete

Re: Cappuccino 0.7 Now Available

boucher — Mon, 15 Jun 2009 13:42:26 -0000

Hi Stefan,

There's a tutorial on debugging and another on Objective-J on the
tutorials section of our website. (http://cappuccino.org/learn/
tutorials).

There is an OJUnit framework which is included in the tools
installation of Cappuccino. It runs on top of rhino, and right now is
mostly suitable for non visual testing.

The easiest way to find the source of an error is to load it in Safari
4 or a webkit nightly and turn on debugging, and the "Break on
Exception" option. This will give you a stack trace to the problem.

Re: Cappuccino 0.7 Now Available

boucher — Sat, 23 May 2009 21:49:06 -0000

Definitely not.