![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: DXL-script view for all Doors users (?) Topic Summary: Created On: 28-Sep-2006 12:56 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hello all, how or where can I place a dxl-script for all Doors-users? Is there a special path :n\n , or funcion for this? The script is placed at the moment in c :\Program Files\Telelogic\DOORS_8.0\lib\dxl\addins\ user I only can see the script in the doors-user-menu. Does anyone have any further idea? Thanks in advance, Christian Edited: 28-Sep-2006 at 13:02 by Christian Montero |
|
![]() |
|
![]() |
|
In the help file look for command line switches
|
|
![]() |
|
![]() |
|
You may find this useful, see Create Menus from a Network Directory on my website.
------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
|
![]() |
|
Didnt read Tony's solution yet, but what we do is place somethingin the windows registry to point to a shared network drive containing the scripts. If you dont get the solution form Tony's article, reply here and I will post our solution.
Rgds
Andrew.
------------------------- Andrew Tagg Thales Air Systems, Melbourne Australia. andrew.tagg@thalesatm.com |
|
![]() |
|
![]() |
|
Edited: 29-Sep-2006 at 13:51 by Christian Montero |
|
![]() |
|
![]() |
|
In order to be eligible for 'addins' insertion in a menu, the desired DXL files and desired folders housing those files must be in proper format. See section titled 'The DXL Library and Addins menus' in the DXL manual.
[1] DXL files should have a single line comment followed by a multi-line comment. These need to be 'near the top' so I just put them at the top; example: // CountRequirements.dxl - Count requirements in the current module /* CountRequirements.dxl runs from a currently open module and counts the number of undeleted objects that contain some valid Text and have attribute value of 'Required' equal to True. */ The first comment appears in the DXL Addins library hierarchy. The 2nd comment block appears when you select a DXL file from that library. [2] The folders housing your addins must have two files. Both files must have the same name as the housing folder; the first file is type *.idx and the second is of type *.hlp. Both can be empty. The IDX file can be used to modify how the menu selection works for a particular dxl file therein. If the idx has no reference to a well-formed *.dxl file (see [1] above), then the name of the dxl file is inserted into the menu. You need at least two levels of such folders; the first is generic and doesn't appear in the menus, the subordinates DO appear in the menus. [3] You 'addins' variable should include a path to the top folder from [2] above. It can point to lots of different places; each is semi-colon separated (don't use spaces around the semi-colons). Environment variable 'Addins' creates menus in formal modules. 'ProjectAddins' creates menus in the DB explorer. 'AttributeAddins' creates a menu available when inserting Attr DXL into an attribute 'LayoutAddins' when inserting a Layout DXL into a column. My 'addins' also includes a reference to the 'ProjectAddins' location, thus making project scripts available from inside a module. Attached find a registry update script I use to set addins locally for me. Save it to some *.reg file. Double click on it from Windows Explorer. Confirm updating your registry. Perhaps you want to change "HKEY_Local_Machine" to "HKEY_Current_User' therein to modify registry just for you and not for everyone on you computer. (Notice I invented the 'linkmodaddins' parameter.) - Louie Edited: 29-Sep-2006 at 19:53 by Louie Landale |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
DXL-script view for all Doors users (?)
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.