![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Share DXL Scripts Topic Summary: Share DXL Scripts via a common Server Created On: 12-Mar-2007 20:06 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Shawn's approach is how we handle this at our company, too. Search the web for instructions in regard to creating a registry file (Windows Registry Editor) - by using your Windows Start button and "Start...Run", then typing "regedit" in the Run window. Look for the Telelogic/DOORS/8.1 (or whatever your version is)/Config folder. It would be under "HKEY_LOCAL_MACHINE\SOFTWARE" and look something like this: [HKEY_LOCAL_MACHINE\SOFTWARE\Telelogic\DOORS\8.1\Config] It would also include the "menu" names (determined by you), such as: "AddIns"="<network_folder>:\\APPS\\Doors User Files" "ProjectAddins"="<network_folder>:\\APPS\\Doors User Files\\ProjectAddins" In any network folder, in order for the scripts to appear on a DOORS menu in an open module, you would need to have .hlp and .idx files with the names that reflect the folder that contains them. For instance, take a look at your present local install of DOORS, and in the C:\Program Files\Telelogic\DOORS_8.1\lib\dxl\addins\user folder, you'll see a user.hlp file and a user.idx file. The network folder you create will have to have similar files for network_folder_name.hlp and network_folder_name.idx. This sounds like a lot of work, but your IT department can help you with this. When you're done, you just send the registry file to your DOORS users (after testing it out on a few, of course) and they will have new menu items, right on the top menu of their DOORS modules, for any scripts that you placed in the network folder. Sweeeeeet. ![]() I hope this helps!! Chris Annal chrisa@sensis.com | |
![]() |
|
I have been developing a bunch of DXL scripts that I would like to give others access to. Is there a way to specify within you ".idx" or ".hlp" files that the actual dxl scripts are stored on a specified server. Any help would be greatly appreciated.
|
|
![]() |
|
![]() |
|
My solution to this was to use the '-a' switch on the DOORS shortcut on the users desktop, and add the following switch setting (including the quotes) to the 'Target' field.
-a "\\\\servername\\DOORS Common Area\\addins"
On the Server create the 'DOORS Common Area\\addins' directory and populate it with your dxl,idx and hlp files as usual.
You will need to make sure any include files are available from below that addins directory too.
Make the same changes to the properties of the DOOSR entry on the Start>Programs button.
|
|
![]() |
|
![]() |
|
What we have is just a DOORS module anyone can read to get user scripts I write. They just copy them into their user directory.
------------------------- David Pechacek AAI Services Textron dpechacek@sc-aaicorp.com David.Pechacek@gmail.com |
|
![]() |
|
![]() |
|
I think you are asking: you'd like a common spot where folks can find scripts, but in that spot you have pointers to where the actual scripts are stored.
No, the idx files cannot have paths to scripts elsewhere, the scripts must be in the same folder as the ids. However, there's nothing to stop you from having this 'script' sibling to the idx: // FindDeletedObjects.dxl - filter for deleted objects in the module /* FindDeletedObjects finds deleted objects bla bla bla */ #include <//MyServer/RealLocationOfScripts/FindDeletedObjects.dxl> - Louie |
|
![]() |
|
![]() |
|
I store all of my scripts in a shared folder on the network. When I do an install on a new client, I install a registry update that specifies the location of the shared folder. In addition, I copy 2 very basic initialization files into the local startup directories of the user. With that done, I can make all of the needed changes to the shared folder without having the users do anything. Works quite well!
Shawn ------------------------- Shawn Stepper shawn.e.stepper@wellsfargo.com |
|
![]() |
|
![]() |
|
Shawn's approach is how we handle this at our company, too. Search the web for instructions in regard to creating a registry file (Windows Registry Editor) - by using your Windows Start button and "Start...Run", then typing "regedit" in the Run window. Look for the Telelogic/DOORS/8.1 (or whatever your version is)/Config folder. It would be under "HKEY_LOCAL_MACHINE\SOFTWARE" and look something like this:
[HKEY_LOCAL_MACHINE\SOFTWARE\Telelogic\DOORS\8.1\Config] It would also include the "menu" names (determined by you), such as: "AddIns"="<network_folder>:\\APPS\\Doors User Files" "ProjectAddins"="<network_folder>:\\APPS\\Doors User Files\\ProjectAddins" In any network folder, in order for the scripts to appear on a DOORS menu in an open module, you would need to have .hlp and .idx files with the names that reflect the folder that contains them. For instance, take a look at your present local install of DOORS, and in the C:\Program Files\Telelogic\DOORS_8.1\lib\dxl\addins\user folder, you'll see a user.hlp file and a user.idx file. The network folder you create will have to have similar files for network_folder_name.hlp and network_folder_name.idx. This sounds like a lot of work, but your IT department can help you with this. When you're done, you just send the registry file to your DOORS users (after testing it out on a few, of course) and they will have new menu items, right on the top menu of their DOORS modules, for any scripts that you placed in the network folder. Sweeeeeet. ![]() I hope this helps!! Chris Annal chrisa@sensis.com |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Share DXL Scripts
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.