![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Configuration Files - more questions Topic Summary: Created On: 16-Sep-2004 10:16 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Well I think I can see a use for configuration files now -- I need to have an enumerated attribute type available to all formal modules in a project, but I need the users to be able to add enumerations to the type at will, and for a new view to be built with a filter based on the new enumeration value. So I think the best place to keep the enumeration values (names, values and colours) is in a configuration file for the project. That way, if user B has module Q open for exclusive edit, meaning the script user A is running can't update the type in that module, a closing trigger on the module can run (a version of) the script later, using the new set of values defined in the configuration file to update the type. Or maybe the script to update the type only updates the current module and the configuration file, and triggers do the rest of the work next time a module is opened.
(Of course, this means I'll also have to get my head around triggers... ![]() But the set of enumerations for the type will differ from one project to another, meaning the configuration file needs to be unique to a project. Louie suggests in 'Configuration files -- what are they?' that appending the name of the project to a filename will fix this, but the DXL manual refers to the area confProjUser, which implies to me that this might be a suitable area, unless it is also visible only to one user. Can anyone (Louie? ![]() Any help/wisdom/intelligent guesswork gratefully received... Paul. ------------------------- Paul dot Tiplady at TRW dot com TRW Automotive |
|
![]() |
|
![]() |
|
Trigger documentation is the pits; you'll need to be an Edison to make something work.
Yup, confProjUser seems to be left over from v4. Now it has the same meaning as confUser. To get project unique configurations you'll need to use the confSystem and tailor it for the projectI now prefer to use a project folder therein, rather than appending the project name to all the files. . The line would be something like : confStream cs = confWrite("MyProject/MyConfFile", confSystem). Run that, then go to your data folder, then ther users folder, then the u000000001 folder, and you should see new folder MyProject. But for your purposes I'd be tempted simply to have some sort of "Attribute Template" module available in the root of each project. DXL would open that module to find the latest and greatest attributes and types and enumerations. Use triggers if you want, or just wait until B closes the module. Insisting that everyone use "defopenmode = READ_ONLY" helps a lot in reducing needlessly locked modules. - Louie |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Configuration Files - more questions
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.