Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic DOORS (steve huntington)
Decrease font size
Increase font size
Topic Title: Invoke DXL script from main DOORS window
Topic Summary:
Created On: 2-Sep-2003 19:55
Status: Post and Reply
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Quick Reply Quick Reply
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
Answer This question was answered by Tony Goodman, on Friday, September 5, 2003 10:19 PM

Answer:
DOORS is extremely fussy about the addins folders.
The addins directory MUST contain the .hlp and .idx files with the same name as the directory.
Each dxl script must have the single line comment followed by a multiline comment.
Subdirectories must also contain their own .hlp and .idx files.

Contents of the .idx file determine what text is displayed on the menu and the accelerator keys for each script as follows:

<script name excluding .dxl extension> <mnemonic> <accelerator> <menu label>

the mnemonic and accelerator keys can be replaced by underbars if you don't want them.

e.g.
mydxl _ _ Run My DXL Script

displays "Run MY DXL Script" as the menu option to invoke mydxl.dxl.

the command line parameter is case sensitive and the directory must be a full path name from a mapped drive. Server names do not work. e.g.

doors.exe -projectaddins "N:\DXL\addins"


 2-Sep-2003 19:55
User is offline View Users Profile Print this message


Logan Campbell

Posts: 3
Joined: 2-Sep-2003

I am a DOORS newbie, my apologies if this question is terribly simplistic.

I am creating a DXL script that acts on a Project/Folder subtree. It starts at the current Folder (or Project), and processes all formal Modules downtree from that location.

My question is how to set up the DOORS menu system so this script may be invoked by the user. I have found the process for adding to the formal Module menu system, but I need to allow the user to invoke this script without requireing a formal Module to be open.

Any advice will be most appreciated.

Best Regards,
Logan Campbell
Report this to a Moderator Report this to a Moderator
 3-Sep-2003 09:44
User is offline View Users Profile Print this message


Tony Goodman

Posts: 1098
Joined: 12-Sep-2002

Welcome to the world of DXL. I hope you enjoy it as much as I do.

There are several ways to add menus to the explorer window. The simplest is to use the
-projectAddins "directory name" command line switch to point to the directory containing your scripts. This allows you to build a menu structure in the same way as you do in the user addins directory for formal modules.

An advantage of this method is that this directory can be on any mapped drive on a server, allowing you to manage the scripts centrally without updating each client.



-------------------------
Tony Goodman
http://www.smartdxl.com
Report this to a Moderator Report this to a Moderator
 3-Sep-2003 16:36
User is offline View Users Profile Print this message


Logan Campbell

Posts: 3
Joined: 2-Sep-2003

Hello, Tony -

Thank you for your reply, and yes, I do enjoy the DXL environment, as I get my brain wrapped around it.

I tried the projectAddins command line switch, and I'm afraid I am still missing something. I passed in the path to my DXL script location, but see no visible difference in the DOORS window.

My script file conforms to the DXL requirements regarding the initial single-line comment, and so on. However, it is not at this time located in a DOORS-location sub directory, nor do I have the .idx and .hlp files present. Are these necessary for this operation?

I have searched the online DOORS help and the Knowledgebase articles, and have found no details on this command switch.

I'll try setting this up with the .idx and .hlp files, in case that is necessary.

If you can provide a bit more detail, or point me to a place I can get more info on this switch, I will be most grateful.

Thanks again for your help so far.


Logan Campbell
Senior Software Engineer
Galorath Incorporated
100 N. Sepulveda Blvd., Ste 1801
El Segundo, CA 90245
www.galorath.com

SEER: Project Estimation, Planning and Control
Report this to a Moderator Report this to a Moderator
 4-Sep-2003 08:59
User is offline View Users Profile Print this message


Tony Goodman

Posts: 1098
Joined: 12-Sep-2002

Answer Answer
DOORS is extremely fussy about the addins folders.
The addins directory MUST contain the .hlp and .idx files with the same name as the directory.
Each dxl script must have the single line comment followed by a multiline comment.
Subdirectories must also contain their own .hlp and .idx files.

Contents of the .idx file determine what text is displayed on the menu and the accelerator keys for each script as follows:

<script name excluding .dxl extension> <mnemonic> <accelerator> <menu label>

the mnemonic and accelerator keys can be replaced by underbars if you don't want them.

e.g.
mydxl _ _ Run My DXL Script

displays "Run MY DXL Script" as the menu option to invoke mydxl.dxl.

the command line parameter is case sensitive and the directory must be a full path name from a mapped drive. Server names do not work. e.g.

doors.exe -projectaddins "N:\DXL\addins"




-------------------------
Tony Goodman
http://www.smartdxl.com
Report this to a Moderator Report this to a Moderator
 5-Sep-2003 22:10
User is offline View Users Profile Print this message


Logan Campbell

Posts: 3
Joined: 2-Sep-2003

Thanks very much, Tony, that got me going.

Your help is most appreciated.
Report this to a Moderator Report this to a Moderator
 19-Sep-2003 16:22
User is offline View Users Profile Print this message


Alec Witham Crawford

Posts: 24
Joined: 2-Jul-2003

Hello! I was wondering what the other ways to add menus to the explorer window are. I can't find any documentation on it.
Before I read this thread, I thought it was completely impossible.

Thanks!
Alec
Report this to a Moderator Report this to a Moderator
 22-Sep-2003 14:42
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

Goodman made a great response. To which I add

[] I don't have any trouble using Network paths for my module and project Addins.
[] The projectaddins command line switch points to a folder. THAT folder's subfolders can appear as menus.
[] I encourage setting "projectaddins=..." in the DOORS.ini (v5) or in the Registry "\HKEY_LOCAL_MACHINE\SOFTWARE\Telelogic\DOORS\6.0\Config" (v6).
[] I also add that path to the "addins" variable, allowing these project addins to be available to modules. That isn't all that useful, but it allows the project scripts to be more closely scrutinized with the Module's Tools Menu >> DXL Library ... command, where the comment line and comment block from the DXL are displayed (along with the *.hlp blurbs).
[] There is another thread discussing manually building menus, but that's much more difficult and only a little more functional.

- Louie

Report this to a Moderator Report this to a Moderator
 25-Sep-2003 02:50
User is offline View Users Profile Print this message


Alec Witham Crawford

Posts: 24
Joined: 2-Jul-2003

Thanks for the extra info.

I found a way that works well for my situation. I added the menu items to the project folder under dxl. Now I can make some of my scripts available from the explorer window (where they should be), and I don't have to worry about command-line arguments.

Alec
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 1 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 16:36.
There are currently 0 guests browsing this forum, which makes a total of 1 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.