![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Auto-opening Modules, Views, and History ? Topic Summary: Created On: 7-Mar-2008 15:51 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
I am working on a DXL Script/Dialog Box where users will be able to select a number of modules to be automatically opened the next time they open DOORS.
So, for example, a user might choose: - Open Module SRS, in Read-Only mode, with View ABC - Open Module SDD, in Shareable Edit mode, with View VIEW10 - Open Module STD, in Shareable Edit mode, with View SuperView The DXL script will then save this info to a text file to be read in next time the launch DOORS. My questions: 1.) Is there any way to get a list of available views for a certain module, without the module being open? 2.) Is there a way to pre-load the history file when the module is loaded. As far as I can tell, the history information is stored in a separate file from the module. And, it takes several minutes to access history information, at least the first time it is accessed. I'd like to pre-load the history file along with the module, so that people don't notice this additional delay when accessing the history information. Overall, I am trying to make it easy for users to essentially have user-preferences that will pre-load the modules they typically work on, along with the views they prefer, and pre-load the history file. Doing this manually step by step is very slow. With this DXL script/dialog box, people will be able to automatically load everything, and they can go get coffee in the morning, while it takes that 5-10 mintues to load up everything. |
|
![]() |
|
![]() |
|
The user can create the view they like and then define that view to be the 'Default for current user' view, and it will be loaded each time that user opens that module. Thus, your script doesn't need to deal with that.
I've not had much of a delay when dealing with History, but perhaps you have. It doesn't seem reasonable to me to cause perhaps a 30 second delay each time a user opens a module in order to prevent a possible 30 second delay when the user infrequently deals with the history of that module. But if you think that's worth it then you can simply have a post-module open trigger that scans through the entire History of the module. DOORS does not have a database login trigger. Thus its difficult to get code to run when the user logs in, without modifying each client and inserting DXL into the right folder. IT folks don't like that. It wouldn't be hard to put an on-demand little script in the users 'User' folder making it appear in the 'User' menu. If you wrote another script that let them define their favorite modules, it could store the names in a config file for that user, and the on-demand script could open them visibly. This doesn't seem worth it to me. - Louie |
|
![]() |
|
![]() |
|
Just for reference, here are some times I took with my trusty stop watch...
Module -- Time to Open -- Time to Switch View -- Time to Access History ----------------------------------------------------------------------------------- #1 -- 1:20 -- 1:54 -- 0:04 #2 -- 0:32 -- 0:03 -- 0:11 #3 -- 1:06 -- 0:02 -- 7:25 #4 -- 7:06 -- 0:02 -- 0:07 If you have to do that each morning when you log in, that's 12 steps that take close to 20 minutes. Of course, I should probably investigate why certain things take so long. |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Auto-opening Modules, Views, and History ?
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.