Livecode Standard Plan

[FourthWorld]

The scripting language is there, the Classic IDE is needed to build Create, many of the bug reports make reference to using Classic.

At the end of the day, you can build the Create IDE in Classic (indeed, that's what they're doing), but not the other way around.

I see Classic as a less attractive power user option for their new market target. But for legacy customers it's the way the workflow has evolved, so as long as it's there it would seem counterproductive to take the additional steps to remove it.

If I sell a product to someone it doesn't matter to me what color shirt they're wearing while they renew their license. My job would be to make sure I keep the value that keeps them renewing. Bonus if it doesn't cost me anything extra to do so.

[jacque]

I know you can edit scripts, so presumably you can write your own. If there was documentation I'd like to try it, but going in cold has put me off so far.

[dunbarx]

Jacque.

I know you can edit scripts, so presumably you can write your own.

OK, so Create does all the control dragging and laying out, and then we can tweak that.

Then it writes a lot of code based on some description of functionality we feed it. And then we can edit that code. OK, that seems in principal like a good deal, assuming that one does not have to spend a lot of time undoing what the very helpful Create assumed was intended.

I guess I will have to reserve judgement until I see a full demo of some sort of project. I saw such a thing a year or two ago. I wonder how it has evolved...

Craig