The reason I ask is that
I may want to have *many*
settings for an emulator. Dozens. Ideally,
these settings appear on additional tabs on the dialog with lots of
user-friendly default values, prompts, and data validation. The
emulator may
not require all values to be passed into it, but it may complain if you
pass in
a parameter name without a value. I don’t want to force the user to
enter
something just because a launch template has a replaceable parameter
for it.
For example, if the user does not want to enter a phone number but the
template
includes “/phone=%number%”, you send the emulator /phone=””
and it may throw up and error and not launch.
So it comes down to this.
Do we expect the user to manually
edit the template? It could be made read-only and presented below the
tab panel.
Changes in the tabbed page fields could be reflected real-time in the
launch
command below. That’s just an idea.
Another option is to keep
the template simple, then add
additional parameters programmatically and hidden from the user. But
that could
hide errors.
As a vendor, I would want
to be careful to do things “the
MTJ way”.
Cheers,
Jon
---
Senior Software
Developer, Eclipse Tools
Research In Motion
905-629-4746 x15333 / Mobile:
519 500-23167
jdearden@xxxxxxx
---------------------------------------------------------------------