Re: [ANN] Lua For Windows v5.1.3.3 Public Alpha2 released

["Andrew Wilson" <agrwagrw@...>]

People experienced enough to have multiple installs of lua, can setup
lua without the need of this type of installer. File associations make
for high accessibility from explorer. This installer isn't targeted at
experienced Lua users but people who might want to try Lua or those of
us too lazy to setup Lua on multiple machines without an automatic
install.

But the safety point is seems valid, double clicking should call the
Lua editor-of-choice rather than executing the script directly. That
also allows the user to see what is being executed rather than just
popping up and scrolling away. There is the -i parameter on lua.exe
but it seems nicer to see what you are doing before you run something.

Another interesting twist is the inno setup  install script
(install\lua.iss) itself is included in the package, and intention is
to include some instructions that say how to regenerate single install
from the installed files. Hopefully, encouraging people to have
multiple versions.

Andrew

On Mon, May 19, 2008 at 9:10 PM, gary ng <garyng2000@yahoo.com> wrote:
>
> --- Jeff Pohlmeyer <yetanothergeek@gmail.com> wrote:
>> I tend to agree with this, double-clicking on a Lua
>> script
>> should not put an inexperienced user at the mercy of
>> the
>> script's author. If anything, the default action
>> should
>> be to open the file in the Lua editor-of-choice.
>>
>> Possibly you could add a context-menu item for
>> "Execute"
>> but I don't think it should be the default action.
> Ideally, there should be an GUI editor that can also
> 'execute' the current buffer to associate the above
> 'double click means edit' action.
>
> Creating a command line window shortcut(like what VC
> does) with the proper path set is more than enough for
> the installer. This also allows multiple installation
> to live happily together.
>
> Afterall, scripting language is still heavily command
> line oriented.
>
>
>
>