User Tools

Site Tools


jwlua:finalescriptvsjwlua

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
jwlua:finalescriptvsjwlua [2013/09/18 19:23]
jariw [The MakeMusic blog]
jwlua:finalescriptvsjwlua [2013/09/18 19:24]
jariw [Conclusion]
Line 5: Line 5:
 ==== The MakeMusic blog ==== ==== The MakeMusic blog ====
  
-Today (Sep. 18, 2013), Kelby Stine at MakeMusic made a post on the MakeMusic blog about replacing Wizard-created staff names through FinaleScript. I thought it would be interesting to do a FinaleScript vs. JW Lua comparison on this (testing on the JW Lua beta 0.05 functionality,​ which is soon available).+Today (Sep. 18, 2013), Kelby Stine at MakeMusic made a post on the MakeMusic blog about replacing Wizard-created staff names through FinaleScript. I thought it would be interesting to do a //FinaleScript// vs. //JW Lua// comparison on this (testing on the //JW Lua beta 0.05// functionality,​ which is soon available).
  
 Kelby'​s blog post is here: Kelby'​s blog post is here:
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. :-)
  
jwlua/finalescriptvsjwlua.txt ยท Last modified: 2013/09/18 19:24 by jariw