Studio – Github
We use checkstyle for our ruby projects and jsHint and esHint for our Ember projects. Part of passing our builds is meeting a minimum threshold for code quality according to these tools.
While getting our main Omnis projects into git is the first step, I fully intend to adopt the code style checks for our Omnis projects as well. When I do, I will be sure it’s open-sourced so we can all enjoy.
Unless someone beats me to the project, of course!
> On Oct 9, 2017, at 06:13, H.P. Noppe <email@example.com> wrote:
> Thanks Alex and Phil,
> The highlighter is far from complete, but it is a nice first version (as I may say myself). Feel free to contribute. Last weekend I have added the omh extension to the package. You can download it from GitHub. It will take some time that the update will appear in the Sublime Text package manager.
> The indenter, well it is born from the frustration of losing the indention when I copy-pasted from Omnis to Sublime or what ever other application. Now with the Json export it will become less relevant. Although copy and pasting code is still easier then exporting it first to JSON. 😉
> Alex is last paragraph below stirred a long cherished wish of mine: Sonarqube (www.sonarqube.org/ <www.sonarqube.org/>) support for Omnis. Our Java developers use it a lot and I think it would also be great to have this for Omnis. I did not have the time to look in to how this works in Sonarqube or any other alternative, but I definitely see some potential.
> Grtz Henk
>> On 6 Oct 2017, at 19:18, Alex Clay <firstname.lastname@example.org <mailto:email@example.com>> wrote:
>> 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 <mailto:email@example.com>> 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 <github.com/Frogli/OmnisStudioHighlighter>
>>> Omnis Studio Indenter – github.com/Frogli/OmnisStudioIndenter <github.com/Frogli/OmnisStudioIndenter>
>>> Phil Potter
>>> Based in Chester in the UK.
>>> Manage your list subscriptions at lists.omnis-dev.com <lists.omnis-dev.com/>
>> Manage your list subscriptions at lists.omnis-dev.com <lists.omnis-dev.com/>
> Manage your list subscriptions at lists.omnis-dev.com
Manage your list subscriptions at lists.omnis-dev.com