The Cappuccino Blog - Latest Comments in Just One File with Cappuccino 0.8

Re: Just One File with Cappuccino 0.8

Tim — Wed, 07 Apr 2010 23:09:39 -0000

How do you handle HTTPS/SSL requests in IE*? I've observed this not working with MHTML.

Re: Just One File with Cappuccino 0.8

Woody — Thu, 18 Feb 2010 10:49:13 -0000

This makes so much sense when its put forward so well...Cant believe I missed this!

Re: Just One File with Cappuccino 0.8

sirus — Thu, 26 Nov 2009 11:27:20 -0000

Look at alternative tool - online generator of data:uri css sprites
http://duris.ru/lang/en/
Supports MHTML for IE < 8 & data:uri for others modern browsers

Re: Just One File with Cappuccino 0.8

tlrobinson — Sun, 15 Nov 2009 17:54:25 -0000

Just like in Cocoa you can implement the drawRect method on a view using the AppKit or CoreGraphics drawing APIs. Check out some of the tutorials: http://cappuccino.org/learn... ("An introduction to Cappuccino Graphics" in particular)

Re: Just One File with Cappuccino 0.8

kevinpan — Sun, 15 Nov 2009 04:13:17 -0000

Thanks, boucher and tlrobinson, for your reply! Could anyone give me some pointers on how to draw a chart (or more specifically, a finance chart such as line or candlestick) using the Cappucino framework? What methods do I call or library do I use? (While I am an Objective-C developer, I have not studied the Cappucino framework or Objective-J language. Any starting tips would be appreciated). Thanks!

Re: Just One File with Cappuccino 0.8

Cédric — Fri, 13 Nov 2009 17:29:24 -0000

Great job.
I was thinking such a feature for a while for the CMS SPIP i'm contributing to.
But having found a way to get it working for ie6&7 is a major step.

Re: Just One File with Cappuccino 0.8

marcuswestin — Fri, 13 Nov 2009 00:39:02 -0000

Nice work guys.

I was browsing around your github repo for the relevant code - would you mind giving a pointer for where to start looking?

Cheers,
Marcus

Re: Just One File with Cappuccino 0.8

tlrobinson — Thu, 12 Nov 2009 20:55:21 -0000

The 2 concurrent connections is a limitation of the web browser, not any particular framework. There are Comet libraries that let you multiplex multiple streams over a single connection.

Check out Orbited, cometd, js.io, and many others. These libraries can be used in a Cappuccino application.

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

kevinpan — Thu, 12 Nov 2009 20:41:16 -0000

Dear Redmar (and other Cappucino fans, as well):

Thanks for your answer! The reason for my worry is my colleage said Google Web Toolkit has problems supporting more than 2 concurrent/simultaneous connections. For GWT, it is possible but requires some major workarounds.

So, I'm wondering how easy to do this with Cappuccino framework? I mean, a stock/forex analysis charting has streams of continuous data feeding to in and updating charts and price display. How reliable would such an application be written using Cappucino?

Thanks!

Kevin Pan

Re: Just One File with Cappuccino 0.8

Mateo — Thu, 12 Nov 2009 09:07:02 -0000

First, I would like to thank you for this amazing framework!

I've got a couple questions.

SproutCore has a really interesting framework called DataStore. It allows to manage structured data and it is often used to implement the model layer, read/write data from/to the server, manage relationship between obects and other cool stuff (like managing for you cache). It is designed with cloud computing in mind.
Do you plan to add a similar framework in Cappuccino?

Do you plan to write a tutorial covering client-server communication?

More generaly, do you plan to make client-server communication easier with Cappuccino?

Re: Just One File with Cappuccino 0.8

Redmar Kerkhoff — Thu, 12 Nov 2009 06:18:39 -0000

>The burning question is: does the Cappucino framework support this many concurrent connections to a server?

This is not really a question for the cappuccino framework, it's more related to the user's browser capability. (so you can lookup general limits of concurrent connections for generic browsers) Another idea could be to multiplex the needed concurrent connections through your server which then acts as a kind of proxy resulting in only one connection for the comet stream. (And added advantages that you can cache the data stream for all your users and that you don't suffer from cross domain connection pains)

Re: Just One File with Cappuccino 0.8

kevinpan — Thu, 12 Nov 2009 04:29:01 -0000

Hi, I'm very impressed by the Cappuccino framework. I'm considering to use it to develop a finance application which includes streaming live ticks of stock prices and forex rates updating dynamic charts (line charts, Japanese candlestick charts, etc.). For this type of application, the client (ie. web browser using JavaScript) has to simultaneously open *MANY* concurrent connections to a server and possible use of http response forever method (ie. Comet) to process the live ticks and update the charts. The burning question is: does the Cappucino framework support this many concurrent connections to a server? If anyone could let me know and possible point me to some code I would appreciate it very much. Thanks! Kevin.

Re: Just One File with Cappuccino 0.8

shaberman — Thu, 12 Nov 2009 00:06:46 -0000

Just coincidentally saw this commit into gwt after reading your post. Might be worth pinging them about their experience with MHTML.

http://code.google.com/p/go...

(Edit: sorry, ManOfTheNorth, didn't mean to reply to your comment, I just hit the wrong button.)

Re: Just One File with Cappuccino 0.8

ManOfTheNorth — Wed, 11 Nov 2009 19:53:26 -0000

The other advantage to base64, that kind of makes up for the size issues, is that they process at a more native level, with half the chip-level instructions per cycle set. This makes for cleaner, faster transitions.

Re: Just One File with Cappuccino 0.8

godavemon — Wed, 11 Nov 2009 16:44:00 -0000

Incredibly awesome! Great work yet again guys!

Re: Just One File with Cappuccino 0.8

robmcm — Wed, 11 Nov 2009 16:35:33 -0000

I was just recently thinking that image (pre)loading was a bit of an elephant in the room with Cappuccino apps.

This looks like a really good solution, not only in preloading or having required images by the time the app launches, but also by speeding it up with Gzip and reduced HTTP overhead on multiple files.

Good work guys ;)

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

WebReflection — Wed, 11 Nov 2009 14:27:14 -0000

I have served via a single file both JavaScript and CSS with packed.it project and MyMin, both dead due missed interest from Web Community. Now that we have images as well, I guess the day we can serve a single file including everything is close. Just a hint, put a minified CSS properly escaped if where necessary into a string and push it into the DOM before the JavaScript code will be evaluated. Add base64 encoded sprites, and a Web Site will automatically become a single request with a single external file which can be served with a quick 304 and a managed via a proper ETag ;-)

Good stuff and nice technique, the scary part is how many "secrets" we can discover about IE, discovering it could have been a better browser if forced properly during these 2.0 era - Documentation Failure?

Regards

Re: Just One File with Cappuccino 0.8

pmuellr — Wed, 11 Nov 2009 12:27:32 -0000

I see someone else is curious about how you're dealing with the base64 33% expansion. I did a quick test on a fairly standard image used in a web app, base64'd it then gzip'd that:

- 3968 bytes for original image
- 5361 bytes for original image converted to base64
- 4108 bytes for original image converted to base64 then gzip'd

Seems like gzip'ing base64'd content puts you back in a reasonable range w/r/t the expansion. But wonder how this scales in general, and with lots of images, and how you'd arrange to pre-gzip the base64'd content.

Re: Just One File with Cappuccino 0.8

Alex Sexton — Wed, 11 Nov 2009 11:52:15 -0000

"This has the added benefit that gzip can work its magic on the entirety of your web app as one, producing better results."

In my experience, I found that gzipping a base64 string showed little to no improvement in size, and often times made my files _bigger_. What were your results, as far as file-size is concerned, when running gzip on a base64 string?

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.