Comments on: Announcing Cappuccino

By: Cappuccino Blog » Blog Archive » Cappuccino Turns One

Cappuccino Blog » Blog Archive » Cappuccino Turns One — Tue, 08 Sep 2009 14:44:06 +0000

[...] officialy turned one last Friday. I suppose that technically Cappuccino is quite a bit older, but a year ago was when we finally released it into the open source community. It’s unbelievable to me that [...]

By: Mohit Aggarwal

Mohit Aggarwal — Sat, 13 Sep 2008 21:59:40 +0000

Hi,

Congrats for this brilliant release. I really liked your mission statement and wish you good luck for future improvements. I am very excited about Cappuccino and know, if picked up; it will change the way web applications are programmed.

By: mohit_aggarwal

mohit_aggarwal — Sat, 13 Sep 2008 16:59:40 +0000

Hi,

By: chris

chris — Thu, 11 Sep 2008 16:31:03 +0000

having some tutorial or just some simple examples for server interaction would be great...

e.g. reading and editing a SQL table
-> generate the XML file on the server and write a PHP handler for the updates, what about the list in cappuccino

probably it's just me but I think that giving such an example would be helpful for quite a few people...

By: Misha Peric

Misha Peric — Thu, 11 Sep 2008 16:04:32 +0000

Nice work indeed!

One question, how is the source code protected? I mean, all the source code is downloaded to the clients machine … For example, I could write a spider and download all the files that comprise your Slides application! Not that I will do that But this is a problem I think …

By: openspecies

openspecies — Tue, 09 Sep 2008 20:32:56 +0000

nice javascript "ontop" runtime,

one comment about your dictionary implementation:

http://openspecies.blogspot.com/2008/08/collect...

use Json to serialize and unserialize your plist

By: boucher

boucher — Tue, 09 Sep 2008 15:42:29 +0000

you don't need a CPURL, the request is just fine. You also don't need the [connection start]. This is a bug int he documentation — the connection is automatically started.

Of course, XMLHTTPRequests must follow the same origin policy — are you making a request to your same domain? Have you examined what the error passed to didFailWithError: is? May help debug the problem. Try hitting us up in our irc channel irc.freenode.net#cappuccino

By: Martijn

Martijn — Tue, 09 Sep 2008 14:47:48 +0000

This is really cool, I can see this getting pretty huge. Especially now Chrome and Firefox 3.1 are promising massive Javascript performance gains.. your timing couldn't be better!

By: sxs

sxs — Tue, 09 Sep 2008 13:27:11 +0000

Hi there,

nice things!

I'm just playing arround. And now I wanna make some “server calls”. I tried this:

var aRequest = [CPURLRequest requestWithURL:"http://foo.bar.com/?ajax=givemesomejson"];
var connection = [CPURLConnection connectionWithRequest: aRequest delegate: self];
[connection start];

I implemented the delegates and the didFailWithError one is triggered.

Now I see that i have to pass a CPURL object to [CPURLRequest requestWithURL:].

But I can't find any documentation about to make a propper CPURL-object, nor I find something in the source (as far as iI understand it

By: boucher

boucher — Mon, 08 Sep 2008 19:07:27 +0000

Donnie,

This is something that everyone developing JavaScript for the web faces. There's really no panacea, but most people have resorted to minification and obfuscation to offer a little defense. While I'm not sure its strictly necessary, I would love to see some of these existing tools adapted to work with Objective-J.