Farewell Livecode...?

[wsamples]

After much trial and error and brain and heart ache, I finally got LiveCode 10 installed on CachyOS which runs KDE. The GUI is a no go, you will hit -E error that some rando is keeping the application from updating. So what you need to do instead is download the installer to the machine, make sure there are no spaces in the path and DO NOT TOUCH THE INSTALLER FILENAME! leave it alone, keep your grubby mitts off.

Then launch a terminal and do sudo -s to switch into Root's account, then cd to the folder where the installer is located and then do chmod +x ./LiveCodeProfessional-10_0_0-Linux.x64 and then finally, do ./LiveCodeProfessional-10_0_0-Linux.x64 -ui -desktopshortcut -startmenu.

Don't bother with the -AllUsers or -Location parameters, it doesn't pay attention, it'll then extract everything to /root/.runrev/components/livecode-10.0.0.x86_64 and also put some icons and a desktop file into /root/.local/share/applications and /root/.local/share/icons/hicolor/48x48/apps respectively. Then you need to do mv ~/.runrev/components/livecode-10.0.0.x86_64 /opt/ which will move the installation folder to /opt where it belongs. Then do mv ~/.local/share/applications/runrev-livecode_10_0_0-x86_64.desktop /usr/share/applications/ and then mv ~/.local/share/icons/hicolor/48x48/apps/runrev-livecode_10_0_0-x86_64.png /usr/share/icons/hicolor/48x48/apps/.

Next issue a nano /usr/share/applications/runrev-livecode_10_0_0-x86_64.desktop and update the line that starts with Exec= to say: Exec="/opt/livecode-10.0.0.x86_64/LiveCode.x86_64" %U then hit Ctrl+O, then Enter and then Ctrl+X to exit Nano. Finally exit from Root's session and issue sudo gtk-update-icon-cache to refresh the icons and then you can find LiveCode 10.0 listed in the Development category of the KDE menu. So in order:

Code: Select all

sudo -s
cd ~/Downloads
chmod +x ./LiveCodeProfessional-10_0_0-Linux.x64
./LiveCodeProfessional-10_0_0-Linux.x64 -ui -desktopshortcut -startmenu
mv ~/.runrev/components/livecode-10.0.0.x86_64 /opt/
mv ~/.local/share/applications/runrev-livecode_10_0_0-x86_64.desktop /usr/share/applications/
mv ~/.local/share/icons/hicolor/48x48/apps/runrev-livecode_10_0_0-x86_64.png /usr/share/icons/hicolor/48x48/apps/
sed -i -e 's/\/root\/.runrev\/components/\/opt/' /usr/share/applications/runrev-livecode_10_0_0-x86_64.desktop
exit
sudo gtk-update-icon-cache

Do that and the app will be usable and will have its icon displayed in the KDE menu. This will likely work for other Arch-based distributions.

For future reference, there's no need to sudo into root unless you want to install in opt which is what the "for all users" option does. The istaller will successfuly install into ~/.runrev if you run it in a terminal with the -ui flag without elevating privileges. Fixing the executable bit of the installer is necessary for all linuxes and this has long been complained about I had posted that solution somewhere here some time ago after I ran into it, too, while trying to update, although I see it wasn't in this thread.

[SirWobbyTheFirst]

After much trial and error and brain and heart ache, I finally got LiveCode 10 installed on CachyOS which runs KDE. The GUI is a no go, you will hit -E error that some rando is keeping the application from updating. So what you need to do instead is download the installer to the machine, make sure there are no spaces in the path and DO NOT TOUCH THE INSTALLER FILENAME! leave it alone, keep your grubby mitts off.

Then launch a terminal and do sudo -s to switch into Root's account, then cd to the folder where the installer is located and then do chmod +x ./LiveCodeProfessional-10_0_0-Linux.x64 and then finally, do ./LiveCodeProfessional-10_0_0-Linux.x64 -ui -desktopshortcut -startmenu.

Don't bother with the -AllUsers or -Location parameters, it doesn't pay attention, it'll then extract everything to /root/.runrev/components/livecode-10.0.0.x86_64 and also put some icons and a desktop file into /root/.local/share/applications and /root/.local/share/icons/hicolor/48x48/apps respectively. Then you need to do mv ~/.runrev/components/livecode-10.0.0.x86_64 /opt/ which will move the installation folder to /opt where it belongs. Then do mv ~/.local/share/applications/runrev-livecode_10_0_0-x86_64.desktop /usr/share/applications/ and then mv ~/.local/share/icons/hicolor/48x48/apps/runrev-livecode_10_0_0-x86_64.png /usr/share/icons/hicolor/48x48/apps/.

Next issue a nano /usr/share/applications/runrev-livecode_10_0_0-x86_64.desktop and update the line that starts with Exec= to say: Exec="/opt/livecode-10.0.0.x86_64/LiveCode.x86_64" %U then hit Ctrl+O, then Enter and then Ctrl+X to exit Nano. Finally exit from Root's session and issue sudo gtk-update-icon-cache to refresh the icons and then you can find LiveCode 10.0 listed in the Development category of the KDE menu. So in order:

Code: Select all

sudo -s
cd ~/Downloads
chmod +x ./LiveCodeProfessional-10_0_0-Linux.x64
./LiveCodeProfessional-10_0_0-Linux.x64 -ui -desktopshortcut -startmenu
mv ~/.runrev/components/livecode-10.0.0.x86_64 /opt/
mv ~/.local/share/applications/runrev-livecode_10_0_0-x86_64.desktop /usr/share/applications/
mv ~/.local/share/icons/hicolor/48x48/apps/runrev-livecode_10_0_0-x86_64.png /usr/share/icons/hicolor/48x48/apps/
sed -i -e 's/\/root\/.runrev\/components/\/opt/' /usr/share/applications/runrev-livecode_10_0_0-x86_64.desktop
exit
sudo gtk-update-icon-cache

Do that and the app will be usable and will have its icon displayed in the KDE menu. This will likely work for other Arch-based distributions.

For future reference, there's no need to sudo into root unless you want to install in opt which is what the "for all users" option does. The istaller will successfuly install into ~/.runrev if you run it in a terminal with the -ui flag without elevating privileges. Fixing the executable bit of the installer is necessary for all linuxes and this has long been complained about I had posted that solution somewhere here some time ago after I ran into it, too, while trying to update, although I see it wasn't in this thread.

I could never get the installer to run otherwise, it always just immediately returned in the Terminal or dumped with a Segmentation Fault error. Either there really doesn't need to be an installer for Linux, just an archive and we can take care of the rest.

[udi]

I've had the same experience. On EndeavourOS MATE, the LiveCode installer says ‘This is most likely being caused by having a version of LiveCode already running in the install location.’ The ‘Continue’ button is unusable. I saw the same issue on Mageia Linux MATE.

My workaround was...

Install Debian on a separate environment
Install LiveCode
Copy the directory '/opt/livecodecommunity-9.6.3.x86_64' to USB drive
Copy it to the same directory on EOS/Mageia
Use the Menu Tools to make LiveCode appear in the menu
Set the .livecode stack properties to open with LiveCode

Everything works fine now.


Thanks all and sorry to my poor English.
UDI https://udimac.web.fc2.com/livecode/withLivecode.html

[richmond62]

Remember, way back when, when LC was tested on a Linux distro, it was tested on a Debian derivative (Ubuntu): that is why, on my Linux machines, I stick to Debian derivs.

[stam]

Yeah, that is a disproportionate amount of work just to install software.
Generally I have no real reason to use Linux, but it's a good option for resurrecting old machines that are unable to receive security updates. Having said that, I'm not sure I see a value in using an OS that makes it so difficult to install what I presume would be an important tool.

I must have been lucky because I just happened to use a Debian-based distro that worked most reliably with my ancient 2012 MacBook Pro. I installed Mint XFCE and then added KDE Plasma desktop and it works a treat. Snappy and highly configurable OS, and LC runs installs with no issues and runs perfectly well.

I will always default to using my newer M2 Pro laptop, but it was bothering me that I couldn't even connect to WiFi with my old 2012 MBP so Linux was a solution but that was more of a vanity project, as I can't say I use that regularly.

I had less luck trying to install Linux on my 2016 i7 TouchBar MBP though - 2/3 of the distros failed to even recognise keyboard or trackpad and neither wifi, sound nor TouchBar (which includes the ESC key) worked with any distro (I did try about 10 distros). I resorted to using OpenCore Patcher to install MacOS Sequoia instead. Works OK but not supersonically fast... but that is another way to resurrect old Macs and will always run LC/LCC.

Having said do we know if LC will continue developing for Linux specifically?
LC10 does run on Linux but is available only as student or learning editions. If you have what used to the the 'standard' licence then you're stuck, as LCC has replaced LC10 in that. And it's hard to see developing for Linux as a profitable venture, so at best it will be browser-based LCC which at present kinda works... but will that produce Linux binaries? Not sure...

[richmond62]

Having said do we know if LC will continue developing for Linux specifically?

NO, as LC is going to stop developing LiveCode completely very shortly.

As LiveCode Create is browser-based (?) it should be accessible on far more platforms than LiveCode ever was . . .

Haiku OS?

[stam]

Having said do we know if LC will continue developing for Linux specifically?

NO, as LC is going to stop developing LiveCode completely very shortly.

As LiveCode Create is browser-based (?) it should be accessible on far more platforms than LiveCode ever was . . .

Haiku OS?

Browser based yes. But will it create Linux binaries? Or just web apps?

[dunbarx]

NO, as LC is going to stop developing LiveCode completely very shortly.

I am confused. Do I not understand that in 2027 Create will take center stage, but that the "standard" LC UI will still be active and available, if no longer updated?

Craig

[richmond62]

I am confused. Do I not understand that in 2027 Create will take center stage, but that the "standard" LC UI will still be active and available, if no longer updated?

Why?

Indeed: as I understand from LiveCode's rather sparse announcements: Create is meant to take over completely from sometime in 2027.

Whether what thou termest "standard" LC will still be available from then on I do not know.

But I understand by "developed" by what you seem to understand by "updated."

However, I would not rely on these announcements as, many, many times before LiveCode have made announcements which, later on, they have not followed through.

https://future.livecode.com/

Ultimately, LiveCode Create will replace LiveCode, running both as a Web IDE and on the desktop.

[stam]

My recollection was they stated that LC10 has now entered a maintenance phase and would be maintained with updates through 2027, when it will be sunsetted in favour of LCC.

I’m pretty sure no one would be surprised if that happened at a much later date or not at all, given their track history.
But one can’t rely on that.

As such choices are really
a) stick with 9.6.3 as long as that works for
b) Use student/learner edition for LC10, up to its sunset
c) Go LCC and use LC “Classic” aka LC10 up to its sunset and the switch to LCC hoping that will fill the gap
d) hedge your bets and dip your toes in other platforms

While I do use LC classic I have dipped my toes in other waters anticipating that (d) will probably not do it for me, but I’m keeping an open mind.

There’s lots of good IDEs out there, fewer that do x-plat moderately well and only a handful that are free or ultra-low-cost.
Sadly these are mostly c-style strongly typed languages that can cause endless frustration who. You’re used to the conveniences in LiveCode.

[dunbarx]

Stam.

That is what I thought. I will stick with LC forever since it does all I could want. When Create is really running I will try it in earnest, but will not care if i revert back to "classic".

Why?

I run three different factory production machines using LC through a gadget that communicates to the outside world via the USB bus. It uses a software framework that is limited to v.8; it will not run v.9 in or later. This does not matter to me at all, because as I am fond of saying, the last feature I really care about is the multi-char itemDelimiter.

Craig