"Install Shell Commands" feature

[peter-b]

In LiveCode 8, there are two command-line tools that are useful to have in the system $PATH: lc-run and (especially) lc-compile. It would be really nice to have a "File→Install Shell Commands" (or "LiveCode→Install Shell Commands") menu item that would set this up.

Having the tools in the system path would make it much easier to do things like add editor support for automatic syntax checking without requiring users to do tedious manual configuration and/or adding fragile manual support for finding LiveCode to every editor.

I'd suggest the following logic on Mac OS X and Linux:

1. If /usr/local/bin/tool exists and isn't a symlink, error
2. Make /usr/local/bin/tool a symlink to the appropriate binary for the version of the IDE that's currently in use
3. Fin

Windows seems trickier and might well entail messing about with environment variables.

Also, I'm not sure what the best way to deal with "Just For Me" installations of LiveCode is. They could either not offer the "Install Shell Commands" menu item, or just install in the global path anyway.

[peter-b]

...And what about an "Install LiveCode Server" menu item that downloads the corresponding server package and installs it in the PATH?

[montegoulding]

Would it be also worthwhile symlinking in the modules somewhere standard that lc-compile could look for. Additionally as the engine can load a stack with a startup handler it may be worthwhile to symlink in the engine. BTW are there guidelines as to when you want stuff posted here v posted to bugzilla?

[peter-b]

@montegoulding We're currently trialing GitHub Issues to see how well-suited it is for our issue-tracking needs -- just for the IDE to start with, and without any big fanfair or expectation that people file bugs here instead of in BZ. Please feel free to continue adding issues to BZ for the foreseeable future. 👍

[montegoulding]

Re server bonus points for installing apache config