Studio – Github
The highlighter in particular is going to be hugely helpful. Once we reach enough critical mass on GitHub, we can register .omh files as belonging to the Omnis Studio language. We can use Henk’s work on this highlighter to add syntax coloring to .omh files.
We’ll be using Atlassian’s BitBiucket server for browsing our Omnis repositories and running code reviews once we get fully switched to git. This template will allow for syntax highlighting there as well. The highlighter uses a format introduced with TextMate than many other editors have adopted. I personally prefer Sublime on macOS and Visual Studio Code on Windows, but some of my devs like Atom. All of these editors can recognize TextMate themes allowing them to render Omnis code properly with Henk’s packages.
The real goal is “linting” or running “checkstyle” against Omnis code. Once we can recognize blocks, keywords, variables, classes, etc. you can use tools to ensure your code meets standard for clarity and readability. While these checks never replace a critical human evaluation they are nonetheless helpful for ensuring a minimum code quality especially when multiple developers contribute to a project.
> On Oct 6, 2017, at 12:30, Phil (OmnisList) <firstname.lastname@example.org> wrote:
> It was also pointed out to me, that if you happen to use sublime text editor, then there are some packages available for it, for Studio?
> Not sure what they do, except for there self explanatory name…
> Omnis Studio Highlighter – github.com/Frogli/OmnisStudioHighlighter
> Omnis Studio Indenter – github.com/Frogli/OmnisStudioIndenter
> Phil Potter
> Based in Chester in the UK.
> Manage your list subscriptions at lists.omnis-dev.com
Manage your list subscriptions at lists.omnis-dev.com