Re: [Wonder-disc] SproutCore

[Anjo K. <an...@kr...>]

What he said (except for this shame spiral thing. If I knew what is  
was, I'd resent the mere idea!).

 From what I saw, SC consists of three parts:

- the actual framework (JS)
- the "test" runtime (Ruby)
- the build system (Ruby)

The latter two are the parts I/we was replacing and they both munge  
the JS and CSS quite a bit before returning it to the browser. So  
basically you should be able to run the examples while using pure WO  
and no ruby at all, but the combine-and-compress step in SC's build is  
currently missing (which makes for longer startup times). But this  
should be easy to add.

While it may be neat to have a build system that outputs pure html/JS  
that you can deploy on every plain web server, I'd actually like do be  
able to build the UI at runtime. So the long-term goal is some sort of  
D2SC. For the moment I'd settle for some free time to test what we  
actually have so far (and create the backend JSON binding). Another  
thing on my TODO list is a persistent connection to the users browser  
where you can "push" javascript into and have immediate feedback. But  
as some guys get all the neat projects and others have to do the  
boring stuff, this won't happen for quite a while :)

Cheers, Anjo

Am 30.07.2008 um 07:26 schrieb Mike Schrag:

>> When
>> I read Mike's and your questions I was completely lost, and added an
>> item to my long to-do list to check the wonder sources. My intuition
>> just tells me that it is something completely different from what I  
>> am
>> trying to do
> Anjo sucked me into his shame spiral on this one, but he went crazy
> and decided that rather than just do WO backend frameworks for the SC
> front-end, instead he decided that he'd rather create WO components
> instead of railish templates for SC, and he actually rewrote the
> SproutCore rails compiler to be based on WO components instead.  So in
> the Wonder SproutCore framework, there's no Ruby at all -- just WO/ 
> Java.
>
> I'm sort of curious to see what YOU have going on.  We have some JSON
> stuff in Ajax framework and some XML/REST stuff in ERRest framework,
> but as I understand it, SC has sort of a particular syntax for its
> server backend (specific naming of what we would call GID's, etc), and
> we haven't talked that part yet, which it sounds like maybe you did
> some work on, so that might be some nice overlap there.  This IB
> thing, I have no idea what to expect :)
>
> ms
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's  
> challenge
> Build the coolest Linux based applications with Moblin SDK & win  
> great prizes
> Grand prize is a trip for two to an Open Source event anywhere in  
> the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Wonder-disc mailing list
> Won...@li...
> https://lists.sourceforge.net/lists/listinfo/wonder-disc