A useful tip when you have separate Model & View schemas

[BeeJay]

This is something that was suggested by a new member of our team, who had not worked with separate Model & View schemas previously, and I've found it so useful I thought I'd share it with the rest of you.

For the last several years, I have been used to having to "swap" back to a "view" schema context IDE form, from a model schema context IDE form, to start our application that resides in the view schema. I have now created a new "A_LaunchViewApp" application, so that it is the 1st application in the model schema and therefore the "default" application unless over-ridden. This application simply has two lines of code in its initialise method:

Code: Select all

app.startApplication( 'OurViewSchemaName', 'OurAppName' ); terminate;

We can then run our application from the IDE without having to swap to a form that has "View" schema context.

Cheers,
BeeJay.

PS: It won't help if you want to run the session in the debugger but I still find it useful enough that I thought it was worth sharing the tip with the rest of you.

[JohnP]

Yes, that is a useful technique. It also works for peer schemas, which is where I tend to use it more.

You can use similar code in JadeScripts. I have some scripts with different lines for apps in different schemas, and uncomment the line I want to use at the time.