Menu
We got so many questions during this live demo we could not get to them all. So we’ve brought them here to get you the answers you are looking for.
In this live Zoom session Kevin demonstrated the Create Cloud interface. He showed that it is the same as the Native interface on the desktop. He demo’d how to use Actions, mix in code, use responsive layout and create a data collection.
In general anything that worked in LiveCode 9/10 (Classic) will continue to work in LiveCode Create Native. However in the case of Plugins, if they depend heavily on specific aspects of the Classic IDE they may need to be updated to work with the new IDE.
Yes there are. And the difference is going to continue to grow as we continue to build Create. We’re working on additions to handle widgets and the new database functions, and other new features we’ve introduced.
push / pop syntax for adding and removing elements from the front/back of sequence arraysstandard adjective for date/time formats (ISO 8601)The PDF Viewer is available in LiveCode Create Native. Its not yet there in the Cloud but it will come.
Yes, substacks are supported.
There is AI already in Create, we have a copilot within the script editor to help you write scripts. AI will help in constructing app layouts and action flows in the future.
Reporting features, such as summaries, tables and other reporting features are coming as part of the point-and-click actions set. So you should be able to construct reports easily.
We will be providing user management features for your apps, with different permission levels.
Currently audio recording on all platforms will record from the system/platform default input. There is a record property which allows selecting mono, stereo and 5.1 etc depending on what the input supports.
Everything you can do in LiveCode Cloud you can also do in LiveCode Native.
It’s in production. We are working on a standalone builder in Native that will let you download your app and upload to your own servers.
We are initially looking at including mySQL support (followed by Postgres) within our data binding system. The system itself will ultimately be extendable. You can also access your own databases in the traditional way using Restful APIs (which will work now).
This is not immediately planned however it is on our radar. (Our own database backend is based on No SQL already.)
It is included in Create Native. It is not supported on the web.
If this platform has a Restful API you should be able to connect to it.
Maybe in the future!
Not yet but it’s something we’ve been looking at. We do have a point-and-click theme editor that has taken some inspiration from things like CSS.
There is a Browser Widget and you can access JavaScript from it. This is yet to come to the Youtube widget but can be added in the future.
The date picker widgets will work and display on mobile in the same way as for Web or Desktop. They are not strictly native, as in accessing the mobile native OS features. We will be adding a Native mode/option to various of the widgets over time.
Yes, we will be providing user management tools.
Yes. It has been used extensively within LiveCode Create. It’s also a separate widget you can use.
We’re adding a pan and zoom function so you can work more easily on large stacks.
It will be an option for Responsive Layout. It should flip automatically between them if you set this as a preference for the layout.
Arbitrary access to other URLs which are not designed to be used from other other sites is not supported, nor will it be. If the user controls the URLs being fetched, then they need to add appropriate CORS headers. There are three possible cases:
You can switch themes in the desktop IDE. You can’t currently change a theme in a compiled app but its something we could look at for the future.
You will be able to. There may not yet be an easy mechanism for adding them in Cloud DP 1, it is coming soon.
If you are experiencing this, please email support@livecode.com with your exact setup, what OS you are on, what browser and version you are using, and what your internet speed is, and we’ll investigate.
Yes, we’ve been designing this in from the start to all aspects of data management in Create.
You can edit an action’s script by pressing the unlock icon in the corner. Doing this will turn it into a LiveCode Script Action Block which can then only be edited by script and not using the Actions setup point and click editor. So to be sure it’s the behavior you want. The other way to add custom code to an Action Workflow is to add a script step to it.
Yes, in code – it’s just hidden in the Property Inspector in DP 1. Coming soon.
This is not possible at the moment – you will need to wait for some more flexible list options that are coming.
Actions apply scripts to the object they are applied to so the hierarchy for them is the same as it is now.
The existing player control supports currentTime and that hasn’t changed. We’re looking at bringing updated functionality into the new video widgets.
The Create web engine supports calling JS from LiveCode, and LiveCode calling into JS, so it depends on what the JS is doing. If its JS libraries doing processing, then you might not need to convert them at all.
If plugins are directly tied to the Classic IDE then they may need to be updated to work in Create.
Yes. If it works currently in LiveCode 9/10, it will work in Create Native. If it is Web compatible, i.e. the functionality is not prohibited by running in a browser, it will also work in Create Cloud.
You can currently only edit one layout (stack) at a time in the Cloud IDE. Navigate between them using the Application Browser. You can choose to embed multiple layouts on a webpage when you deploy your app.
Yes, it should do, provided you haven’t used any features from Create that LiveCode 9 cannot understand, in which case it may not open or things may be missing or not work correctly.
If they don’t yet have all of those features, we will be adding them provided they are browser compatible.
We are taking nothing away. Everything that worked in LiveCode Classic will still work in LiveCode Create Native, and the vast majority of features will work in Cloud, with some restrictions being imposed by browser restrictions. Just open your stacks in Create and carry on working.
At present it is not affected. You build for mobile from Create Native in Classic mode, exactly as you do now. In the future, we are looking at how many of the pain points we can remove from this process – a first step is almost completed in removing the requirement for a specific version of Xcode in the upcoming Create Native standalone builder.
Yes, in LiveCode Create Native. Mobile and Web don’t have these concepts.
We are working on providing written and video documentation as fast as we can for all aspects of the new Create tools and widgets.
We’ll look into this.
No, you absolutely are not. We are working on documentation, we know how vital this is and we’ll be providing more as fast as we can.
There will be “fair use” limits. These will be published from time to time on the website, and may vary over time. Our intention is that these fair use limits are sufficient for most use cases for paid apps. For free apps, the fair use limits will be tighter.
Yes. You can use Create Native today to ship your apps for iOS and Android. Features to build for desktop and mobile from the Cloud, if you have the appropriate Universal license, are being worked on.
There is no difference. With the possible exception that the Native IDE can run offline and any AI features would not work during the time there is no connection.
We are not planning to move to purely browser based, we think there will always be a need for desktop development, at least for the foreseeable future.
Create Cloud runs best in Chrome at present. Better support for other popular browsers is coming.
It’s the same language.