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.
Livecode Standard Plan
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
-
FourthWorld
- VIP Livecode Opensource Backer

- Posts: 10101
- Joined: Sat Apr 08, 2006 7:05 am
- Contact:
Re: Livecode Standard Plan
Richard Gaskin
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn
Re: Livecode Standard Plan
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.
Jacqueline Landman Gay | jacque at hyperactivesw dot com
HyperActive Software | http://www.hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com