英文:
Does DOORS baseline and/or track history of Attribute DXL and Layout DXL scripts
问题
- DOORS是否维护此代码的历史记录，与DOORS对象行的历史记录方式类似？
- 当您基线模块时，DOORS是否保存此代码的副本？
- 如果1或2为真，是否有一种方式可以查看与视图中的列相关联的Layout DXL代码片段的历史记录/基线？
- 如果1和2都不成立，有人能否建议一种好的方法来备份或版本控制dxl脚本？即：我是否可以创建自己的dxl文本文件，并将这些文本文件放入SVN（或类似的工具），然后告诉DOORS将它们用作特定列的Layout DXL？
- 如果1和2都不成立，属性DXL是否有比Layout DXL更多的历史记录/备份/基线功能？
我在浏览DXL窗口和编辑列窗口中寻找“历史”按钮，但没有看到任何看似有用的东西。谷歌和搜索IBM DOORS帮助页面返回了许多与“基线dxl历史”等术语相关的结果，但它们都是关于使用DXL来显示其他对象/模块的历史和基线信息的，而不是查找Layout DXL代码片段本身的历史的说明。
英文:
I often edit DOORS Layout DXL, usually by starting with a column created using Analysis->Wizard and then going into the column properties Layout DXL -> Browse... -> Current.
In terms of Layout DXL code that is attached to a column in this way:
- Does DOORS maintain a history of this code, in any way similar to the history of a DOORS object row?
- Does DOORS save a copy of this code when you baseline a module?
- If either 1 or 2 are true, is there a way I could view the history/baselines of the pieces of Layout DXL code attached to columns in a view?
- If 1 and 2 are not true, can anyone suggest a good way to back up or version control dxl scripts? Ie: could I make my own dxl text files and put those text files in SVN (or similar) and then tell DOORS to use them as Layout DXL for certain columns?
- If 1 and 2 are not true, is there more history/backup/baselining functionality for Attribute DXL than Layout DXL?
I've looked for a History button in the Browse DXL window and Edit Column Window, but don't see anything that seems promising.
Google and searches of IBM DOORS help pages return lots of results for terms like "baseline dxl history" etc, but they are all about using DXL to display history and baseline info for other objects/modules, not instructions for finding the history of a Layout DXL code snippet itself.
答案1
得分: 0
视图与模块版本无关，这样的好处是你可以定义一个新视图，并且它在所有基线中都有效。但缺点是代码不存储在基线中，所以对于1和2来说，不是。另一方面，属性DXL（5）属于模块版本，因此代码包含在基线中。
关于4：
我们是这样做的：
我们有一个基础目录，它受版本控制（svn、git、hg，随你喜欢）。这个基础目录有子目录，比如“scripts”、“lib”等。
当我们想要访问DXL代码，比如在菜单或列中时，我们唯一的代码行是指向DXL文件的相对路径，例如#include <layout/TraceColumn.dxl>。
现在，我们只需要创建一个批处理文件来启动DOORS。在这个批处理文件中，我们使用带有参数-addins "%ADDINS%"调用doors.exe，其中ADDINS是一个包含实际基础目录的变量。
这样，DOORS可以找到它需要的代码，我们就可以像任何其他源代码一样对我们的TraceColumn.dxl进行版本控制。
英文:
Views are independent of module versions, which has the advantage that you can define a new view and it works in all baselines, but the disadvantage that the code is not stored in a baseline, so: for 1 and 2: no. Attribute DXL (5) on the other hand belongs to a module version and thus the code is contained in the baseline.
Concerning 4:
We do it like this:
We have a base directory that is under version control (svn, git, hg, as you like it). This base directory has subdirectories like "scripts", "lib" etc.
When we want to access DXL code, e.g. in a menu or in a column, the only line of code we have is a relative path to a DXL file, e.g. #include <layout/TraceColumn.dxl>.
Now, we only need to create a batch file to start DOORS. In this batch file, we call doors.exe with the parameter -addins "%ADDINS%" where ADDINS is a variable that contains the actual base directory.
This way, DOORS can find the code it needs and we have can version our TraceColumn.dxl just like any other source code.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论