LiveCode Forums

There was no need to do anything other than install a piece of software from the distro's official repo which installed whatever dependencies were missing. Also, there are several distros which don't use either rpm or deb and KaOS is one of them.

Glad I could help

I assume you're referring to the Start Center. The dictionary works and standalones using the browser widget work as expected. The start center is selected to open on startup. Switching to "classic start center" produces the same behavior.

Full official Linux support is extremely limited, but LiveCode runs well in many unsupported distros. Sadly, not as well in a few others. KaOS is definitely an outlier distro. A self standing project using its own packages, it offers only KDE Plasma and has a predominant focus on the QT toolkit. Thi...

For someone who may want to distribute LiveCode applications to Linux users, it may be important to note that while the IDE does not work in Leap 42.1, some standalones do. Exactly why the IDE fails is a mystery. The IDE is itself is a very complicated LiveCode app and while its performance suggests...

Full official Linux support is extremely limited, but LiveCode runs well in many unsupported distros. Sadly, not as well in a few others. Here's a brief synopsis of my experience testing LiveCode in two distros that are based on Arch; Manjaro and Antergos. Again, KDE Plasma 5, 64 bit using LiveCode ...

Full official Linux support is extremely limited, but LiveCode runs well in many unsupported distros. Sadly, not as well in a few others. Here's a brief synopsis of my experience with LiveCode in openSUSE 64bit using LiveCode versions 8.0.2 and 8.1-RC2. All versions of openSUSE are running KDE Plasm...

Which version of LiveCode are you using at the moment?

So, your code block for Linux could be this: if the systemVersion contains "Linux" then --Linux -- this does not address the possibility that a user may have installed some versions -- as "single user" and other versions for "all users" set the folder to tFolder & "/" & tVersionSelected & "/" put th...

Further, using shell() will work for you but there are a couple of things to watch out for. First, shell() is blocking and the launcher will be unresponsive until the instance of LiveCode that it opened is closed. Secondly, you may need to escape the path to LC due to spaces and parentheses. For ins...

Andy, the code you first attempted, "lauch tLaunch" works fine here to open versions 8+ but fails to open LC in versions 6x or 7x, for reasons unknown to me. I get the same result in the message box. A note about how you scan for versions; it's very possible users have installed different versions i...

Andy, I have no problem using 'launch' to open Livecode here in openSUSE and I doubt it will be a problem for anyone running a more or less typical Linux desktop environment. You do have to provide the complete path to the executable. I can't promise you'll never come across a user who has moved Liv...

Having LiveCode Server read and adjust certain settings according to a file could be a useful feature request. There is a forum here for that and you can also do it here: http://quality.livecode.com/ choosing "Feature enhancement" from the option menu. Since the aim is to provide flexibility, maybe ...

On Linux the new dictionary of livecode 8 doesn't work. :( To amplify on what Richard is saying; this kind of statement is far too broad, just not true, counterproductive for you as an affected user, unhelpful for anyone who may be interested in helping you, and possibly bad for LiveCode because it...

Please note that the date/time format for these headers must be in the format shown in the examples in your initial post. They must reference GMT and not any local time zone. If these are lc files specifically because you are serving dynamic content then it could be appropriate to set the Last-Modif...