What Users want from the next version of LiveCode
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
Re: What Users want from the next version of LiveCode
Better automatic add inclusions to make generating executables go without any problems. This truly should be an automatic process!
Re: What Users want from the next version of LiveCode
I am using livecode to create interfaces for video-installations in a museum context. The single most important thing for me would be to be able (again) to place controls on top of a player object without compromising playback speed and framerate. My second biggest wish would be to be able to place controls on top of the map widget. And of course it would be nice if there would be a larger developer community that could contribute to LC. Thank you! Oliver
-
- Livecode Opensource Backer
- Posts: 9387
- Joined: Fri Feb 19, 2010 10:17 am
- Location: Bulgaria
Re: What Users want from the next version of LiveCode
Hang on a moment until I stop laughing.a larger developer community
A large proportion do.that could contribute to LC
I think you may be apportioning blame in the wrong place.
Re: What Users want from the next version of LiveCode
@richmond62 Sorry, I don't understand your comment. Irony is not my strength. My point was to say that I would hope more people would discover livecode and would actively contribute to its development, either in the forums, building extensions, improving the documentation an so on. What's wrong with that? Best. Oliver
-
- Livecode Opensource Backer
- Posts: 9387
- Joined: Fri Feb 19, 2010 10:17 am
- Location: Bulgaria
Re: What Users want from the next version of LiveCode
Nothing whatsoever.What's wrong with that?
But your initial post suggested that there was not already a sizeable number of end-users
who contributed to LC.
Re: What Users want from the next version of LiveCode
In no particular order..
library sharing promoted as a first class feature in the form of script ony stacks, either hosted directly on github or a lc github lite style site. Import a library into an open stack or download a library into your current projects folder with a one liner using the messagebox eg. "livecode import github. com /bhall2001/fastjson". optionally view libraries in use at the top of the mainstack script
short form syntax for those that want to use it, english language is becoming increasingly abbreviated in it's usage, language evolves, so could the syntax eg. a= 1
slices
custom types which are essentially slices under the hood
multi line string variables
more built in methods for manipulating tables and the datagrid to make them easier to use out of the box
library sharing promoted as a first class feature in the form of script ony stacks, either hosted directly on github or a lc github lite style site. Import a library into an open stack or download a library into your current projects folder with a one liner using the messagebox eg. "livecode import github. com /bhall2001/fastjson". optionally view libraries in use at the top of the mainstack script
short form syntax for those that want to use it, english language is becoming increasingly abbreviated in it's usage, language evolves, so could the syntax eg. a= 1
slices
custom types which are essentially slices under the hood
multi line string variables
more built in methods for manipulating tables and the datagrid to make them easier to use out of the box
Re: What Users want from the next version of LiveCode
Trevor Devore made one.simon.schvartzman wrote: ↑Wed Aug 26, 2020 11:19 amMosquitto library: such that LC developed Apps will be able to join the IoT universe...
Finger crossed!
https://github.com/trevordevore/lc-mosquitto
Andy Piddock
https://livecode1001.blogspot.com Built with LiveCode
https://github.com/AndyPiddock/TinyIDE Mini IDE alternative
https://github.com/AndyPiddock/Seth Editor color theming
http://livecodeshare.runrev.com/stack/897/ LiveCode-Multi-Search
https://livecode1001.blogspot.com Built with LiveCode
https://github.com/AndyPiddock/TinyIDE Mini IDE alternative
https://github.com/AndyPiddock/Seth Editor color theming
http://livecodeshare.runrev.com/stack/897/ LiveCode-Multi-Search
Re: What Users want from the next version of LiveCode
I would like to see an EASY way to add Andriod sdk's.
Not having this ability turns away would be Android developers
Not having this ability turns away would be Android developers
Andy Piddock
https://livecode1001.blogspot.com Built with LiveCode
https://github.com/AndyPiddock/TinyIDE Mini IDE alternative
https://github.com/AndyPiddock/Seth Editor color theming
http://livecodeshare.runrev.com/stack/897/ LiveCode-Multi-Search
https://livecode1001.blogspot.com Built with LiveCode
https://github.com/AndyPiddock/TinyIDE Mini IDE alternative
https://github.com/AndyPiddock/Seth Editor color theming
http://livecodeshare.runrev.com/stack/897/ LiveCode-Multi-Search
-
- VIP Livecode Opensource Backer
- Posts: 7237
- Joined: Sat Apr 08, 2006 8:31 pm
- Location: Minneapolis MN
- Contact:
Re: What Users want from the next version of LiveCode
Not what you asked for exactly, but you can see all libraries in the "stacks in use" pane in the message box.view libraries in use at the top of the mainstack script
I'm curious why we'd need multi-line variable names. If you meant variable values, you can already do that.
Jacqueline Landman Gay | jacque at hyperactivesw dot com
HyperActive Software | http://www.hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
-
- VIP Livecode Opensource Backer
- Posts: 9837
- Joined: Sat Apr 08, 2006 7:05 am
- Location: Los Angeles
- Contact:
Re: What Users want from the next version of LiveCode
FWIW array element names can include CR. It's not recommended, so I support the docs listing them as prohibited, since things like "the keys" become useless with multi-line names. But AFAIK from testing this out, consistent with the method the engine uses to distinguish names, I believe only NULLs are strictly prohibited.
That said, life is MUCH easier with single-line element names. If multiple parts are needed consider a different separator; semcolons seem a natural fit for that problem.
That said, life is MUCH easier with single-line element names. If multiple parts are needed consider a different separator; semcolons seem a natural fit for that problem.
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
-
- Posts: 641
- Joined: Tue Jul 29, 2014 12:52 am
- Location: Brazil
Re: What Users want from the next version of LiveCode
HI Andy, thanks for your hint. Trevor's library isn't available for mobile...AndyP wrote: ↑Wed Dec 16, 2020 12:48 pmTrevor Devore made one.simon.schvartzman wrote: ↑Wed Aug 26, 2020 11:19 amMosquitto library: such that LC developed Apps will be able to join the IoT universe...
Finger crossed!
https://github.com/trevordevore/lc-mosquitto
Simon
________________________________________
To ";" or not to ";" that is the question
________________________________________
To ";" or not to ";" that is the question
-
- VIP Livecode Opensource Backer
- Posts: 9837
- Joined: Sat Apr 08, 2006 7:05 am
- Location: Los Angeles
- Contact:
Re: What Users want from the next version of LiveCode
What dependencies does Trevor's library have that prevent it from working on mobile platforms?
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
-
- Posts: 641
- Joined: Tue Jul 29, 2014 12:52 am
- Location: Brazil
Re: What Users want from the next version of LiveCode
Hi Richard, plese see below Trevor's answerFourthWorld wrote: ↑Thu Dec 17, 2020 5:48 pmWhat dependencies does Trevor's library have that prevent it from working on mobile platforms?
You are correct that the mosquitto project at https://github.com/trevordevore/lc-mosquitto does not have mobile libraries. In order for a LiveCode extension to work on a platform you have to compile a library that goes in the ./code folder. Currently there are compiled libraries for macOS and Windows 32/64-bit:
https://github.com/trevordevore/lc-mosq ... aster/code
Compiling a library can sometimes be the most time consuming part of developing an extension though. Compiling a C library that will work with a LiveCode extension on iOS or Android isn't something I am familiar with so I can't provide much guidance there. You could try asking on the forums or the mailing list to see if anyone wants to chip in. After all, the beauty of Github and open source is that multiple people can contribute to a project.
Another alternative is to reach out to LiveCode and ask about hiring them to get lc-mosquitto working on mobile. Just be aware that the project was one created for a conference talk. I have not used it in any commercial setting other than running some basic tests.
--
Trevor
Simon
________________________________________
To ";" or not to ";" that is the question
________________________________________
To ";" or not to ";" that is the question
-
- VIP Livecode Opensource Backer
- Posts: 9837
- Joined: Sat Apr 08, 2006 7:05 am
- Location: Los Angeles
- Contact:
Re: What Users want from the next version of LiveCode
Thank you, Simon.
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: What Users want from the next version of LiveCode
-Multi-threading, in other languages eg.Python. One can say do this in this thread and that in that thread.
-HTML5 not the way it is now, but something like an output which is a mix of LC-server and HTML. Again this makes it difficult to deploy, because most servers do not run LC-server. It has to be installed extra. Current HTML5 is deployable, but unworkable.
-HTML5 not the way it is now, but something like an output which is a mix of LC-server and HTML. Again this makes it difficult to deploy, because most servers do not run LC-server. It has to be installed extra. Current HTML5 is deployable, but unworkable.