[EDIT: You can just launch Intellipad with Samples Enabled, from the Start Menu. For some reason my first port of call was to run Intellipad from the command line]
Ok I’m beginning to dive into Oslo, so I can at least Appear knowledgeable for the PDC Fireworks talk next week, but there was one thing that was holding me back…
To me the most interesting thing in Oslo is the M language and ability to create on the fly Domain Specific Languages, at the moment this functionality is pretty simplistic but there’s a huge number of applications I can think of, not least with my interest in testing side of things (something that Jeremy Miller alluded to).
As such I wanted to get to grips with how the M language works and how to write grammars and models.
I quickly followed this tutorial but found that the Intellipad experience wasn’t as advertised.
As such here’s a quick primer of how to get the three column view up a little like this:
First navigate to the Oslo SDK Bin Directory (on my machine with x64 windows server 2008 it’s located at C:Program Files (x86)Microsoft Oslo SDK 1.0Bin), open the Intellipad folder and you’ll find a sample sources folder, in this folder is a visual studio solution, Open up and build this solution.
Once the solution is built, back in the Intellipad directory you should have another folder (samples), open this folder and copy the directories to the Intellipad components folder
Ok so now we have MGrammar support in Intellipad, you can open Intellipad by clicking on ipad.exe in the Intellipad folder
Lets’ open up a grammar file and try and get the three pain layout as described in the article.
From the Intellipad open menu navigate to the Oslo SDK samples directory and the song directory under MGrammar
C:Program Files (x86)Microsoft Oslo SDK 1.0SamplesMGrammarSong
open the Input.song file
This is the easiest way I’ve found to get the three window layout, open the input file first.
Once the input file is loaded you can press Ctrl+Shift+G to turn the mode to MGrammarMode, this will give you extended menu options:
From this menu click on Tree Preview this will bring up the open dialogue again, this time select the Song.mg file in the same directory as the Input.song file.
if all is well you should end up with the input.song being in a DynamicParserMode window, the Song.mg being in an MGrammarMode window and a GrammarPreviewMode window.
Changes to the input on the left get run through the grammar in the middle and produce the output on the right.
Hopefully this will save some people some time and effort playing round.