Developer Documentation

Log in to your Developer Dashboard, and click on the SDK deployment package link to download and run the installer file. The installer wizard will take care of everything for you.

For ease of use, it is recommended to set up your mebt publishing options as environment variables on your machine:

To add new environment variables in Windows 7, enter the Start menu, right-click Computer, and click through to Properties → Advanced System Settings → Environment Variables...

If you're using Windows 8, you need to look for the Edit system environment variables dialog

When you've got the dialog, click New under the User variable for... panel, and enter the following variable names with their appropriate values:

Figure 27. The Environment Variables dialog with the new variables

When you've done all that, click OK to save your changes.

This might have seemed quite a lot of fuss, but you have in fact saved yourself tons of time: From now on, all you need to enter when you run the mebt tool is the command and the folder that you want to access.

You can try it out for yourself with this very simple mobile form - the very first one you'll be writing in the next tutorial. Save the file in its own folder, navigate to it in the command line, and enter the mebt run . command:

c:\RockyJupiter>mebt run .
mobilengine srv 28.0 (Release) v28.0.38.19272
Executing run (compile and deploy to server):
Service url: https://tutorial.outdoor.mobilengine.com/comex/v1/
User: petar.hoyt@gmail.com
adding 'vehicleInspection.form.xml'
Reset integration settings
No changes for form 'vehicleInspection'
Done.

Save the following batch file as mebtRun.bat in the mebt folder (most probably C:\Program Files(x86)\Mobilengine SDK, but do double-check):

Download and install the NppExec plugin, and then set it up to run mebtRun.bat with a keyboard shortcut:

In Notepad++, select the Plugins → NppExec → Follow $(CURRENT_DIRECTORY) option.

Select Plugins → NppExec → Execute..., type C:\Program Files\mebt\mebtRun.bat $(CURRENT_DIRECTORY) into the Command text box, enter mebtRun as the script name, and click Save.

Figure 28. Notepad++'s Plugins → NppExec → Execute.. dialog with the Command(s): text box and the Script name: drop-down showing your input

Select Plugins → NppExec → Advanced Options: type mebtRun into the Item name text box, choose mebtRun in the Associated script drop-down, and click Add, then OK.

Figure 29. Notepad++'s Plugins → NppExec → Advanced Options dialog, showing your input

Select Settings → Shortcut Mapper.. → Plugin commands, find mebtRun in the list, click the Modify button at the bottom of the dialog, set the shortcut for the script, and click OK.

Figure 30. Notepad++'s Settings → Shortcut Mapper.. → Plugin commands dialog, with the mebtRun script highlighted

Select Plugins → NppExec → Console Output Filters → HighLight, enable two lines, and set up highlight masks to match %FILE%(%LINE%,%CHAR%):* and %FILE%:* (see screenshot below).

Figure 31. Notepad++'s Plugins → NppExec → Console Output Filters → HighLight dialog, showing your input

You're all set: from now on, whenever you press Ctrl+F5 in Notepad++, a console window with mebt.exe running inside it will appear at the bottom of your screen, and the folder that your current file is in will be compiled and published to the cloud.

Figure 32. This is what you'll see when you press Ctrl+F5 (or your custom associated keyboard shortcut) while an artifact solution file is open in Notepad++