/
How configurable should individual templates be?
How configurable should individual templates be?
The answer is - a little. But not too much:
iNTERFACEWARE as company needs to be moderate in the number of templates we put out since our customers will rightly expect that we test the templates we offer.
It makes sense not to cram too many different use cases into a single template, for example
Have a plain unencrypted LLP socket, and an encrypted one - don’t try to make one that does both
Have a FTP template which is separate from a File template
etc. etc.
Less options per template means:
The Lua will be easier to understand, test and modify for custom requirements.
, multiple selections available,
Related content
Where/how do we store the custom fields?
Where/how do we store the custom fields?
More like this
Structuring Component Translators
Structuring Component Translators
More like this
How we handle QA and support with a lot more Lua libraries?
How we handle QA and support with a lot more Lua libraries?
More like this
How are we planning to handle networking in Iguana X?
How are we planning to handle networking in Iguana X?
More like this
How does Lua's simplicity make it more secure?
How does Lua's simplicity make it more secure?
More like this
Configuration Management
Configuration Management
More like this