<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">I also like Charles' idea of
stand-alone plug-ins.<br>
<br>
It's very probable that there will be more users,<br>
if the plugins are stand-alone and don't need any<br>
group editing, special selecting, etc. - although these<br>
features maybe very interesting for the professional users.<br>
<br>
It would also be much easier to integrate them in Finale with
macros,<br>
if they were directly accessible through Finale keyboard shortcuts<br>
(i.e. with TG Tools / Menu shortcuts) or via the Finale plug-in
menu.<br>
<br>
Some suggestions of how to implement this in a very simple way:<br>
<br>
- the developer makes a 1:1 filecopy of the "jwlua.fxt" file
(copy&paste) and <br>
renames the new file to the new stand-alone filename, e.g.
"jafixtimesignatures.fxt"<br>
<br>
- the JW Lua script must have the same filename but with the file
extension .lua<br>
(i.e. "jafixtimesignatures.lua") and must be placed in the same
directory as the .fxt file,<br>
so that there are two files for the stand-alone plugin in the
FInale plugin directory.<br>
<br>
- when initializing the fxt plugin on Finale start, JW Lua will
scan for a .lua file <br>
with the same filename.<br>
If the .lua file is found, it will be registered as a
stand-alone plugin in Finale<br>
and appear in the Finale plug-in menu with a plugin name as
defined in the .lua file.<br>
If the .lua file is not found and the filename is jwlua.fxt, it
will be the standard<br>
"developer" jw lua plug-in as we know it. <br>
If the .lua file is not found and the filename is not jwlua.fxt,
it will not be recognized <br>
as a valid plug-in in Finale (is this possible ?), but simply
ignored.<br>
<br>
- If it is a standalone plugin, the user interface will simply be
the interface of the .lua file -<br>
or if that doesn't have an interface, the plug-in will perform
directly without user interface.<br>
If it's not a standalone plugin, it will work as we know it now.<br>
<br>
Benefits are:<br>
- not much work of implementing<br>
- only one plugin .fxt file required for the stand-alone and
developer version, <br>
so only one software project to maintain<br>
- nearly no effort in creating the stand-alone version for the
developer<br>
- very simple to install for the user (simply put download both
files from <br>
the software developer and put them into the Finale plug-in
directory)<br>
<br>
Jari, what do you think about it ?<br>
<br>
Jan<br>
<br>
<br>
<br>
Am 18.08.2014 13:56, schrieb Jari Williamsson:<br>
</div>
<blockquote cite="mid:53F1E9E6.3070202@mailbox.swipnet.se"
type="cite">Charles,
<br>
<br>
Currently, the end user can add a script to appear in the Finale
plug-in menu if running the script through the JW Lua window is an
issue. In the future, the end user will get a "Repository" feature
that will make it a one-step process to download an install a
script (similar to how Sib works). There's currently no plans to
provide scripts as stand-alone plug-ins.
<br>
<br>
<br>
Best regards,
<br>
<br>
Jari Williamsson
<br>
<br>
<br>
On 2014-08-17 23:02, Charles O. Lawrence wrote:
<br>
<blockquote type="cite">Jari,
<br>
<br>
You may have discussed this before and I just missed it. Is
there any
<br>
plan in the future for a script compiler or something similar
that will
<br>
allow JWLua scripts to by run on a system without the JWLua
plug-in
<br>
installed? Some people might like a script but, not being of
the
<br>
developer mindset, do not want the “hassle” of going through the
plug-in
<br>
to run it.
<br>
<br>
Charles
<br>
<br>
<br>
<br>
_______________________________________________
<br>
JWLua mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:JWLua@jwmusic.nu">JWLua@jwmusic.nu</a>
<br>
<a class="moz-txt-link-freetext" href="http://jwmusic.nu/mailman/listinfo/jwlua_jwmusic.nu">http://jwmusic.nu/mailman/listinfo/jwlua_jwmusic.nu</a>
<br>
<br>
</blockquote>
<br>
<br>
<br>
_______________________________________________
<br>
JWLua mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:JWLua@jwmusic.nu">JWLua@jwmusic.nu</a>
<br>
<a class="moz-txt-link-freetext" href="http://jwmusic.nu/mailman/listinfo/jwlua_jwmusic.nu">http://jwmusic.nu/mailman/listinfo/jwlua_jwmusic.nu</a>
<br>
<br>
</blockquote>
<br>
</body>
</html>