jerry.daniels at me.com
Thu Jul 22 08:20:47 CDT 2010
For all intents and purposes, you are on the money.
Couple answers to your question marks below...
Rodeo now in beta:
On Jul 22, 2010, at 5:28 AM, FlexibleLearning <admin at FlexibleLearning.com> wrote:
> THANK YOU for taking the time to write such a comprehensive answer and for
> being gentle with me. I hope others will have found your further
> explanations helpful also. As a struggling 50-something rev developer who
> wants to stay in the game, you are describing me completely.
You're welcome. Your questions forced me to the heart of the issue.
> What you have done sounds nothing short of quantum (if not the decimation of
> Rev itself). My needs are purely practical; I leave 'lifestyle' to those
> that can afford it. The process therefore as I have to understand things
> 1. Write Rev stack. Limit functionalities to (limitations list?).
No groups (unless datagrid) yet.
No graphics, yet.
Transfer just notes that these are not transferred. No errors.
> 2. Use the Rodeo transfer utility on a Mac to compile the stack as
> 'Rodeo-Talk' to your account on the Rodeo server.
> 3. Use a Mac to edit the work now in 'Rodeo-Talk' using the Rodeo Editor,
> hosted on Rodeo's server.
Or user can also log into their Rodeo dev space and edit their definitions using any webkit compliant browser, tho the desktop Rodeo editor might be better for many at this time.
> 4. Save and Test the webApp (how?). Re-visit the Rodeo Editor to
Sarah and I have used a client side load tester to help with un-covering bugs. We are still working on our debugger. It will be like tRev's decoder.
> 5. Copy the webApp to your site.
Will be easier than that...click deploy button and choose/create a target(s).
> 6. Tell people the url so they can view it in a webkit-compatible browser
> such as Chrome or Safari.
Or create a Mac client app which is a customized browser for the Mac users you might have.
> Requirements: (for developer)
> 1. A Mac with a webkit-compatible browser
Mac with Leopard or Snow Leopard has this by default. We do have users who develop on non-Mac in a webkit browser like Chrome or Safari, but Mac desktop is easier to work in at this time.,
> 2. An account with the Rodeo server at $189/year
$149 until we release in August, then $249. Right now there is much work for us to do in order for us to create client/customer-pleasing apps. Check out our time-line in the post linked above in my signature.
> At some stage it would be helpful to see some video examplars that show the
> functionalities available. I have a set of 20 interactive careers lessons
> written in rev that the client wants delivered in a browser. Rodeo sounds
> the way to do this, with the additional benefit that the lessons could also
> be viewed on an iPad (and utimately on an iPhone also).
> PLEASE tell me I got it now!
Oh, yeah. You got it.
> You're not being thick. Rodeo is not for everyone on earth and not for
> everyone on the list. Obviously. However, it is very important to a HUGE
> number of us. You could easily be one of those people for whom it satisfies
> no need. The AHA is in the eye (or heart) of the beholder. Not everyone here
> or there are going to have it.
> Addressing some specifics you mentioned:
> - Webkit is an engine for many web browsers, especially the mobile ones. I
> think FireFox and IE will use webkit eventually. Maybe sooner than we think.
> In any case, it's simple to develop and app and tell your customers to get a
> webkit browser (Chrome or Safari on any platform are excellent).
> - Many apps use webkit to render their screens...not just web browsers.
> That's what iTunes was and is. There are many more out there doing the same
> thing. Their value in the marketplace is much more than a web page in a
> - The above are technical and business reasons for choosing webkit as our
> prime target for Rodeo's deliverables.
> - There are many, many people who will simply not download a web plugin.
> Ever. Steve Jobs (rightly or wrongly) has placed nails in the coffins of
> more plugins than just Flash.
> - Sarah, MJ and i think the desktop wars are fading as an issue as more
> developers on all platforms simply use webkit in a browser or a shell app to
> do their bidding. This allows them to compete with cheaper labor markets.
> There is, however a steep learning curve for many to do this. Rodeo
> definitions are an antidote to this problem.
> - We chose an Xcode Desktop Mac app as our shell app to house our editor and
> as a shell app to house other folks' web pages who develop in Rodeo because
> of its superior webviews.
> - The next step for Rodeo is to make a shell app for iOS devices (in Xcode)
> that does the same as our Mac desktop shell app. iPad is a magic word for
> getting work, good prices paid for work, and availability of work. LIke it
> or not, iPad sales are astounding. HUGE. And the app model, the web app
> model have captured the imagination of people who pay people like us
> There are some deep issues that the emergence of Rodeo touches. They
> certainly not purely technical or economic, or even totally logical. Many
> developers have had a visceral reaction to Rodeo because it gets to issues
> of lifestyle.
> For many of us, delivering web apps to webkit browsers will get us back in
> the game. Let us create product quickly that our customers can afford...that
> can't be outsourced to a cheaper labor pool. That once again captures the
> imagination of our clients and customers.
> For all of the above reasons, Rodeo (rightly or wrongly) represents HOPE.
> Who cares if the Rodeo editor runs on a Mac? We're talking about HOPE,
> lifestyle, family, passion all returning to where they belong in the breasts
> of struggling developers in their 50's and in debt.
> The world many of us live in has changed profoundly in a very short period
> of time. Economic collapse, outsourced jobs, and apps. Not executables,
> apps. And app stores. And hybrid-designed mobile devices with 4 dollar apps.
> Maybe that helps. Maybe not. Good starter dough, perhaps.
> Jerry Daniels
More information about the use-livecode