![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Inserting DXL Layout Columns using DXL Topic Summary: Created On: 21-Feb-2007 22:43 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hi,
I need to insert some DXL layout columns using DXL - I know how to insert columns using DXL, but when it comes to creating a DXL layout column, the most common method I've seen to date for inserting the actual DXL layout source code is to represent the source code as one large string of text with zillions of "\" escape and "\n" new line characters everywhere. Is there a way to read in the source DXL code for the layout column from a file rather than defining the source code as a string? ------------------------- Paul Miller Specification Practices Specialist, EuroCyber, Melbourne, Australia. Mobile: +61 (0)418 135 103 Web Site: http://www.eurocyber.biz E-mail: miller@eurocyber.biz">pmiller@eurocyber.biz |
|
![]() |
|
![]() |
|
I don't think there's any way of directly reading the DXL from a file.
However, you could read the file into a string and use the following functions to do the escaping and conversion of newlines: |
|
![]() |
|
![]() |
|
Hey Paul, Edited: 28-Feb-2007 at 14:55 by Kevin James |
|
![]() |
|
![]() |
|
Hi Kevin,
Thankyou for your response. I liked your use of Constants to help configure a DXL layout function and your sample code showed me how to read in DXL code from an external file - it's a lot easier than I thought - many thanks for that. The use of #includes to point to a single instance of the DXL code is something that I've used before but becomes a pain when a Project or Module needs to be archived and restored onto another database. We have customers and sub-contractors who also use DOORS and quite often we need to exchange copies of projects and modules. DOORS doesn't handle broken #include paths very elegantly so I've tended to steer clear of this. I would be nice if DXL supported pre-processor commands so that #includes can be used on a conditional basis. ------------------------- Paul Miller Specification Practices Specialist, EuroCyber, Melbourne, Australia. Mobile: +61 (0)418 135 103 Web Site: http://www.eurocyber.biz E-mail: miller@eurocyber.biz">pmiller@eurocyber.biz |
|
![]() |
|
![]() |
|
Hi Paul,
You've definitely got a more complicated scenario than we do. I've never even considered that because we've always had a single database and a single team accessing DOORS. I guess the only way around that issue if you still wanted to use #includes would be standardize the DXL scripts that the different contractors use (probably not worth the effort), or to have some kind of script that takes a module to be archived, makes a copy of it, and in the new module loops through any DXL columns and replaces any include statements with actual code from the file. That seems like a lot of work too though. Anyway, I can think of any quick solution to your problem about includes, but I'm glad you can at least use the code about pulling DXL from a file. Regards, Kevin |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Inserting DXL Layout Columns using DXL
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.