Re: Cappuccino
Re: Cappuccino
- Subject: Re: Cappuccino
- From: Florijan Stamenkovic <email@hidden>
- Date: Fri, 05 Sep 2008 16:52:46 -0400
Uhm, I've taken a peek at the API. Seems to have some interesting
stuff in there. Very AppKit like. I wonder what Apple would have to
say about that, legally. Still, 117 classes to cover everything from
basic raw type encapsulation to high level GUI management??? Sounds
weak and I have doubts about how extendable the low level API is, and
how easy it would be to integrate custom stuff into it. Which is
crucial for library development... Which is crucial for a language...
Which is, well, just crucial.
Well, we'll see...
As for the replacement of JavaClient? Hm, I'd say it'd be more suited
to a JSON-RPC style solution. Dave has a point in pointing out EOF
libraries on the client. I would not count on Apple implementing
those in Cappuccino...
F
On Sep 05, 2008, at 16:04, Guido Neitzer wrote:
On 05.09.08 13:43, "Chuck Hill" <email@hidden> wrote:
That is fine for document centric apps. My uneducated, uninformed
guess is that using this to replace JavaClient would be a lot of
work. It might be interesting to try.
I know. I guess, you can provide some sort of JSON data source and
use that
in the way you had to when there was no CoreData - populate arrays
and so
on.
Yeah, there should be something for that. Might be coming pretty
soon ...
The framework itself looks really cool.
cug
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40mac.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden