LiveCode Create Beta Update — Introducing Create Copilot + Major Features & Fixes!

Announcements
1

Hi everyone,

Today marks a major milestone for LiveCode Create. We’re extremely excited to introduce Create Copilot, our new deeply-integrated AI assistant that lets you vibe code directly inside the platform, then immediately fine-tune everything visually, add widgets, edit the code yourself, do whatever you need to do to get it perfect. This is a first release of Create Copilot, it will have issues and missing features, however we’re delighted to bring it to you today to start working with. Please give us feedback in the forum!

Below is a summary of the headline features, followed by detailed release notes on the major additions.

Top Highlights in This Release

Create Copilot (Early Beta)

  • AI-powered vibecoding inside LiveCode Create.
  • Switch instantly from Copilot to visual editing and script adjustment.

Cloud-Backed Media Assets

  • Assets now stored securely in the cloud and available in standalones.
  • New support for databinding assets into widgets.

Full Multi-Platform Deployment

  • Create Native now deploys to Mac, Windows, Linux, Android, iOS, and Web.
  • Web standalones are now responsive automatically.

New List Widget + Navigation Drawer

  • A fully themeable list widget with templates and databinding.
  • Brand-new navigation drawer widget.

Faster Cloud Project Loading

  • Opening and saving cloud-based projects is now significantly faster.

Expanded Icon Support

  • Many more icons available plus a new icon picker palette.

Major Widget, IDE, and Library Improvements

  • Big refinements across dropdowns, tables, labels, script editor, actions editor, guidelines, visibility controls, and more.

How to Get the Update

If you have Create Native

  • Download the latest release from your LiveCode user account.

If you have Create Web–only access

If you don’t yet have Create

Full Release Notes

Create Copilot (Early Beta)

  • New AI assistant built directly into Create.
  • Enables vibecoding inside the platform.
  • Move seamlessly from generated code to visual editing.
  • Eliminates the “black box” feeling of code you can’t inspect or modify.
  • Early beta with major future potential.

Media Assets

  • Media assets now stored in the cloud and available in standalones.
  • Datastore collections now support an asset field type.
  • Image and image list widgets can bind to collection data for asset display.
  • Added actions to add, delete, and download media assets in collections.
  • Image list now supports web images (HTTP/HTTPS).
  • Numerous layout, alignment, and sizing issues fixed in image list.
  • Image widgets now support asset IDs and async URL resolution.

Deployment

  • Create Native now deploys apps to Mac, Windows, Linux, Android, iOS, and Web.
  • Projects can contain multiple deployment profiles with different settings.
  • Standalones now include a built-in login dialog.
  • Create Native and Create Web can deploy previews directly to the Web Application Service (WAS).
  • Previews automatically overwrite prior versions.
  • Users can publish to WAS, list deployments, launch or delete them.
  • Classic stack import now converts standalone settings into Create deployment configurations.
  • Web standalones are now automatically responsive, no scripting needed.

List Widget

  • New themeable list widget with databinding.
  • Includes a variety of prebuilt list templates.
  • Layout can be customised via the inspector: size, position, content type, default values.

Navigation Drawer

  • Added a new navigation drawer widget.

Cloud Performance

  • Cloud save and load times significantly improved.

Loading Overlays

  • Snackbars and busy indicators now work in Create Native as well as Create Web.

Icons

  • Larger selection of icons now available.
  • New icon picker palette added.

Widgets

  • Progress animations can now be disabled.
  • Progress widgets have a new roundHeight property.
  • Pasting into fields now respects character limits.
  • Many widgets now support text themes.
  • Dropdown menus now respect screen height.
  • traversalOn now works correctly in field-based widgets.
  • Dropdown button borders can now be customised.
  • Chips widgets now compare caselessly when setting selectedChips.
  • Table widget improvements including:
    • columnTypes and columnSortTypes properties.
    • Various behavioural fixes.
  • Label widget updates:
    • Labels can now be empty.
    • Labels now support databinding.

Libraries

The following libraries are now available in the Create IDE:

  • AWS
  • Diff
  • Dropbox
  • Message Authentication
  • Mime
  • QR

Responsive Layout

  • Implemented the overrideVisible property for unified visibility control.

IDE Improvements

  • Improved startup flow: stacks now appear only when controlled by the canvas library.
  • Project “last edited” timestamps now display in readable local time.
  • Added “Export All Project Layouts” menu option.
  • Cmd/Ctrl+S now works in the script editor.
  • Script editor contextual menus now dismiss correctly.
  • “Go to definition” restored in the contextual menu.
  • Guidelines now behave predictably, support grouping, and have refreshed styling.
  • Improved experience when switching layout breakpoints.
  • Variable viewer no longer hangs on long text values.
  • More expressions now usable in the actions editor.
  • Script editor handler list restored with sorting and click-to-navigate functionality.
  • Invisible groups now ignored when drag-dropping from the tools palette.
  • Delete key now works in the message box.

Thanks for Testing!

This is a huge release and we’re incredibly grateful for your feedback, bug reports, and enthusiasm. Create Copilot is just the beginning — and your input helps shape what comes next.

Happy building!

1 Like
2

Hi Heather - can I double check what this means?
It was previously mentioned that the data store would persist only up to an hour for testing purposes, which was a bit of a sticking point for me… does this means that data store is now persistent without time limitations?

3

Hi Stam,

The data store is persistent yes, your assets will remain available indefinitely.

Best Regards,

Heather

4

Edited for clarity.

Hi Team - another question:

What is LC’s decision on cards vs stacks(layouts)?
This question has been asked before but I do not recall seeing a clear answer (sorry if I missed it…)

As previously mentioned, many of us would greatly miss the card metaphor - in terms of using more modern terminology, a card would actually be what a ‘layout’ is, and what is termed ‘layout’ (ie a stack) is what really would be called a window.

I’m sure almost all of us would like to have multiple layouts per window… as it stands now, if I have multiple views I want to implement in a given window, I would have to either create groups and show/hide these, which is more taxing during development; or I would have to create multiple layouts (aka stacks) but then have the issue of positioning and resizing so the end user doesn’t see that these are different windows (stacks).

Cards still do seem to live a half-life in Create - I can create and navigate these with the messagebox but can’t copy/paste objects from one card to another and these are not in any way accessible via the IDE.

In terms of code organisation, having the ability to segregate code into stack, card and objects was a tangible metaphor for MVC style coding, which was seriously helpful. Cards+Card scripts were the “View”, while “Controller” would be the stack. I would normally use substacks or libraries for “Model”.

But much more commonly I would create generalisable commands and functions in the stack script so they can be accessed from all its cards and objects.
I don’t want to have to copy the same code from “layout” to “layout” for generalisable functions and handlers that would normally live in the stack script and could be used by code in cards or objects.

If cards are really going away, then at the very least there has to be some top-level location for code to be shared across all layouts - an ‘app’ and/or ‘session’ object (for web apps) that sits above or outside the layout (stack) hierarchy.

Otherwise, coding is really going to suck - large codebases are going to be really error-prone to maintain when you have to copy/paste large scripts from layout to layout.

I’m sure a lot of thought has been given to this, and I’m very grateful for an update on the direction of travel…

Stam

1 Like
5

Hi Stam,

Cards and stacks will continue to be supported as they always have been. You can edit a stack script right now in Create along with card scripts. You can view and navigate cards in the project browser.

For new users we are encouraging one screen per layout. This will allow us to do caching and progressive downloading of content in future. It will allow you to view multiple screens side by side when editing, and let us do things like pan and zoom to view your entire application all at once. It is a simple and easy concept to explain. The word “card” has been adopted for a different use in Material design, so thats also one less thing to explain too.

In terms of the concerns you raise about potentially missing functionality, there shouldn’t be any gaps:

  • There is a new “master control” system coming shortly. Select objects, create a master control, place this object on any layout. Edit in one place to change on all. These objects will take widgets to the next level, essentially providing templates and reusable functionality with point-and-click. You can add scripts at the level of this template giving you code reuse.
  • There will be a project level script that can contain library code accessible to all other layouts.
  • You can continue to insert scripts into the front/back.
  • Navigation between screens in the same window is just a case of saying “go in window” and it will work as it does today (already supported).

Copy and paste only working from the context menus is a bug rather than by design.

At the end of the day you can continue to do what you’re used to. We expect these new methods to be useful for everyone and provide a great deal of increased flexibility with master controls.

Kind regards,

Kevin

1 Like
6

Thanks Kevin, sounds encouraging, new nomenclature not withstanding. Having this functionality will encourage many I suspect…

7

Will the “master control” be something like a “global group”?
Know what i mean? A group that can be part of more than one stack?

8

Yes, it will be quite like a group designed to be placed anywhere on any stack.

1 Like
9

Thank you, Kevin!

My text is too short…

10

I have just done my first “Create Copilot” test and I am very surprised but I discover that Copilot understands French very well!

I submitted the same question as Heather’s demo but in French… not only does it work but the result is a layout completely in French!

Create-Copilot
Create-Copilot836×1500 113 KB

«Créer une mise en page pour une application mobile, qui recueille des informations d'un agent commercial sous forme, comme résultat d'une réunion avec un client.»

2 Likes
11

Amazing! Thanks for sharing.