This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
jwlua:finalescriptvsjwlua [2013/09/18 19:23] jariw [The MakeMusic blog] |
jwlua:finalescriptvsjwlua [2013/09/18 19:24] jariw [Conclusion] |
||
---|---|---|---|
Line 79: | Line 79: | ||
//JW Lua// is a programming language, and the comparison clearly shows that difference. You'll need to code a bit more, but you have full coding flexibility, can control the brevity of the language - and you get execution speed. | //JW Lua// is a programming language, and the comparison clearly shows that difference. You'll need to code a bit more, but you have full coding flexibility, can control the brevity of the language - and you get execution speed. | ||
- | However, in Finale 2012 string replacement in staff names is generally a bad approach since it put user restrictions on the script. Instead, the //JW Lua// script should make changes primarily based on the ''InstrumentUUID'' property. In the specific example above, the //JW Lua// execution is about **372 times faster** than //FinaleScript//, which would probably be even more difference if a ''InstrumentUUID'' solution would be used. But that's way beyond this comparison. :-) | + | However, in Finale 2012 string replacement in staff names is generally a bad approach since it put user restrictions on the script. Instead, the //JW Lua// script should make changes primarily based on the ''InstrumentUUID'' property. In the specific example above, the //JW Lua// execution is about **372 times faster** than //FinaleScript//, which would probably be an even larger difference if a ''InstrumentUUID'' solution would be used. But that's way beyond this comparison. :-) |