Converting RGB to HEX with lua

[jsmorley]

I would, and have, create a Toolkit.lua file, that has as many clever little functions in it that you might ever use. It could have functions to convert text "case" in different ways, format numbers with commas, convert colors between rgb/hex/hsb, convert numbers to text, autoscale numbers, pretty much anything you want. Then you just stick that file in any @Resource folders for skins you might need any of them, and call them as needed, anywhere and as many times as you like in the skin(s), using just one "host" Script measure in the skin.

This file can have hundreds of little functions if you want. None of them are used or expend any resources unless they are "called" in the skin.

Sorry, but I'm just not going to "reinvent the wheel" in every skin I need some function like that, and figure out how to use them multiple times in the same skin without bulking up the code.

This is the beauty of Inline Lua. It's one of the best things we ever did.

[balala]

I would, and have, create a Toolkit.lua file, that has as many clever little functions in it that you might ever use. It could have functions to convert text "case" in different ways, format numbers with commas, convert colors between rgb/hex/hsb, convert numbers to text, autoscale numbers, pretty much anything you want. Then you just stick that file in any @Resource folders for skins you might need any of them, and call them as needed, anywhere and as many times as you like in the skin(s), using just one "host" Script measure in the skin.

This file can have hundreds of little functions if you want. None of them are used or expend any resources unless they are "called" in the skin.

Sorry, but I'm just not going to "reinvent the wheel" in every skin I need some function like that, and figure out how to use them multiple times in the same skin without bulking up the code.

Yes, Inline lua probably has great advantage in front of a "classic" code, which doesn't use a lua code.
But where Toolkit.lua is accessible?

[StArL0rd84]

I would, and have, create a Toolkit.lua file, that has as many clever little functions in it that you might ever use. It could have functions to convert text "case" in different ways, format numbers with commas, convert colors between rgb/hex/hsb, convert numbers to text, autoscale numbers, pretty much anything you want. Then you just stick that file in any @Resource folders for skins you might need any of them, and call them as needed, anywhere and as many times as you like in the skin(s), using just one "host" Script measure in the skin.

This file can have hundreds of little functions if you want. None of them are used or expend any resources unless they are "called" in the skin.

Sorry, but I'm just not going to "reinvent the wheel" in every skin I need some function like that, and figure out how to use them multiple times in the same skin without bulking up the code.

Sounds very interesting.

[jsmorley]

Yes, Inline lua probably has great advantage in front of a "classic" code, which doesn't use a lua code.
But where Toolkit.lua is accessible?

I've never posted mine anywhere. Let me clean it up and add a few other things to it and I will do so in another thread.

[balala]

I've never posted mine anywhere. Let me clean it up and add a few other things to it and I will do so in another thread.

Ok, I wait it.

[eclectic-tech]

I've never posted mine anywhere. Let me clean it up and add a few other things to it and I will do so in another thread.

Excited to see that release!