Thoughts on Kevin's announcement

Ian Wood revlist at azurevision.co.uk
Thu May 13 06:13:07 EDT 2010


Presumably Jerry is asleep at the moment but from what I've read and  
watched...

Rodeo is written in Rev and creates *online* HTML webapps, hosted on  
On-Rev. Xcode is not involved in the end-user's workflow at all*. The  
'originally written in' clause is irrelevant because all that ends up  
being accessed by someone using a Rodeo-created webapp is HTML/CSS/JS.

Basically, using Rev's strengths in text/file manipulation to generate  
all the relevant web files from a Rev-like syntax. What I'm not sure  
of is whether the Rodeo service is set up to generate the web files on- 
the-fly or to compile them when you finish editing an app. Presumably  
the second option, or the server load would get a bit heavy.

Ian

* Jerry has spoken about a future possibility of advising authors on  
PhoneGap-style wrapping of webapps for submission to Apple, but again  
all the code is processed within Webkit and therefore bypasses the  
restrictive parts of the SDK agreement.


On 13 May 2010, at 10:55, David Bovill wrote:

> I'm sort of assuming that Rodeo is an app written in Cocoa Touch/ 
> Objective
> C/Xcode which reads and writes structured data to the web server. You
> therefore have an authoring app and a web service. The web service  
> is able
> to customize an Xcode project, and therefore create an app from this  
> data
> for you, which you then aim to submit to the App store.
>
> Questions:
>
>   - Is this right?
>   - Is this not simply using web services to do the same thing as  
> any other
>   framework that automatically generates Objective C for Xcode - and  
> therfore
>   "could" fall foul of the "originally written" clause on the new  
> license?




More information about the use-livecode mailing list