Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic DOORS (steve huntington)
Decrease font size
Increase font size
Topic Title: Some DLX Attribute to display like Object Heading/Object Text column
Topic Summary: Nice formating in a DXL attribute
Created On: 24-Jul-2006 19:39
Status: Post and Reply
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Quick Reply Quick Reply
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
 24-Jul-2006 19:39
User is offline View Users Profile Print this message


Octavian Stanescu

Posts: 39
Joined: 28-Feb-2005

How do I display rich text in a new attribute - DXL Attribute?

I need to create a column that displays the last baseline, and use that like a released copy of the document.

Here is a DXL attribute that displays the last baseline of the current module. I would like to be shown like the Object Heading/Object Text column.
Report this to a Moderator Report this to a Moderator
 25-Jul-2006 07:29
User is offline View Users Profile Print this message


Reik Schroeder

Posts: 361
Joined: 28-Jul-2003

Hi Octavian,

could you try the attached code
I've changed your version to use the set function to copy the attributes value ... may be this works.

Greetings
Reik Schroeder

-------------------------
Evosoft GmbH
for Siemens Industry Sector


Berlin, Germany
Report this to a Moderator Report this to a Moderator
 25-Jul-2006 13:21
User is offline View Users Profile Print this message


Octavian Stanescu

Posts: 39
Joined: 28-Feb-2005

Thanks for reply, the code is much cleaner but still needs more.
I think that the Object Heading  does not contain formating info, because I get the following:

DXL ATTR          Object Heading/Object Text

Section 1            1.1  Section 1
Section A            1.1.3  Section A
RTF  b Text         RTF b Text

So, I think that I would have to add manually the formatting and numbering for the headings.
If I do:
Buffer b = "{\\b1 { " number (old) "  " old.Object Heading "}}" 
 
I get somthing that resembles the look of the Object Heading, but I thought I can make it look like the original. 

PS: With this method we are trying to have some test documents that we can execute looking at the DXL attribute, since that is the last baseline (reviewed/approved document) and still edit the document while testing (changes will be still saved but not part of the baseline).
Report this to a Moderator Report this to a Moderator
 25-Jul-2006 13:30
User is offline View Users Profile Print this message


Paul Tiplady

Posts: 176
Joined: 28-Oct-2003

Can you accept a two-window approach? If so, then you can maybe open the current version for edit in one window and the baseline as read only in a second window. You then 'execute the test documents' (not sure what that means) on the baseline window, and the user plays with the current-version window. This seems like a simpler approach than trying to mimic the formatting you get for free in a 'main' column. For instance, how will you deal with the formatting changes users are allowed to make for heading font etc?

The bottom line is, there can only be one 'main' column in a window, and it's only the main column that can automatically present object heading and object text with the appropriate formatting. Ok, I might not have the details exactly right (someone will correct me, I'm sure), but the general essence of the 'main' column is about right.

Paul.

-------------------------


Paul dot Tiplady at TRW dot com
TRW Automotive
Report this to a Moderator Report this to a Moderator
 25-Jul-2006 14:14
User is offline View Users Profile Print this message


Octavian Stanescu

Posts: 39
Joined: 28-Feb-2005

I can open a baseline but that is Read Only, so I can not modify the other attributes.
Ok, let me be more specific,, there are 4 other important attributes:
 1. Test Status - pass, fail, N/A
 2. Test Date (filled by trigger installed post save on Test Status)
 3. Test Engineer (filled by trigger installed post save on Test Status)
 4. Test Comment - not that importand

The "Test Execution View" will not have the main colimn displayed, it will have this DXL attribute displayed as the main column, because you want to view the baseline and be able to record (modify) the "Test XXX" attributes.
The "Test Editing View" will be the normal view, for the lead engineers to desing the test document and to baseline the test document when is approved.

In the future I want to make more dxl attributes with their own views, so I can combine the values of the Test Status, Test Eng, etc. with the main Object Text, so I can run the same exporting tool (usually we need Word doc format).

Also, If anyone is interested in the Trigger code that I use for Test Status, let me know.
Report this to a Moderator Report this to a Moderator
 25-Jul-2006 14:31
User is offline View Users Profile Print this message


Paul Tiplady

Posts: 176
Joined: 28-Oct-2003

OK, let me keep stirring...

Can you not have a Test Execution module, which gets copied from (and linked back to) the baselined Test module when you hit the 'I want to do a test' button. If you make the object heading and text in the Execution module uneditable once you've copied it, you have effectively the same thing as you have now, without the pain of working out how to format a surrogate object heading and text.

For exporting, you can follow the links from the 'master' module to the appropriate (latest?) results module, and you should be able to expand the concept to the otehr views you're after. And it doesn't need to look any different to the user (except for the module name).

-------------------------


Paul dot Tiplady at TRW dot com
TRW Automotive
Report this to a Moderator Report this to a Moderator
 25-Jul-2006 14:54
User is offline View Users Profile Print this message


Octavian Stanescu

Posts: 39
Joined: 28-Feb-2005

This is kind of what we have now:
 1 - manually copy the baselined module (get the same identifiers numbers for free -> kind of linking)
 2 - make Object Heading and Object Text - READ ONLY -
 3 - execute tests
 4 - export results to Word -
 5 - done - delete/reset the copy (erase all results)

Next time repeat with the next baseline.

But, I thought the DXL attribute would be more elegant solution, and maybe keep the results in the same module.



Report this to a Moderator Report this to a Moderator
 25-Jul-2006 15:08
User is offline View Users Profile Print this message


Paul Tiplady

Posts: 176
Joined: 28-Oct-2003

I have developed an allergy to 'elegant solutions' over a period of time ;-) I now go with what works!

The down side of keeping the resuls in the same module is that you only ever have the latest results. But since your 'what we have now' system deletes the results after printing, that's probably not an issue. Personally, I like to keep the old records -- you never know when they might be useful -- and putting them in a separate module allows you to keep as many as want (given disk space...). Naming the results file for a combination of the name of the baselined test module and the date and time will give you something you can trace quite easily without too much fear of duplicating module names (watch out for the change from summer time to winter time ... :-D )

I like your original solution. And if it ain't broke, don't fix it!

-------------------------


Paul dot Tiplady at TRW dot com
TRW Automotive
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 0 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 16:36.
There are currently 0 guests browsing this forum, which makes a total of 0 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.