Ignition uses jython, which is an implementation of python. Unlike most popular languages, python identifies control structures (if, for, while, …) by indentation. So style is constrained by the rules of the language. This was very much intended by the inventor of the language.
For all practical purposes there is no style guide, because it’s not needed.
[quote=“Kevin.Herron”]There is a style guide[/quote]Interesting. I never noticed that PEP, even though I’ve browsed them before. Based on a quick skim, I’m a baaaaad boy.
Sorry to bump the old thread but the topic is still relevant and good reference info seems hard to come by. I've been looking for best/common practice info on naming and folder structure for perspective views, among other things, in order to communicate/implement some simple standard practices for our dev team.
Here is another "style guide" I came across while looking for similar data. It is not mine but freely available on GitHub. I'm not clear on how to apply the "Linting" info in an Ignition environment (due to lack of familiarity) but all the other info seems relevant.