Richard Lay

[Richard Lay]

I create a package, and in it a diagram. On the diagram I put 4 classes. The are created in the package. So much for the Sparx stuff.
In eaDocX I create a Word document and insert the diagram. I have a profile for Class that just shows the Name. In the Preview> Diagram options.. I pick Diagram and all contents.
Then Generate the eaDocX and I get the Diagram and the 4 names underneath… beauty.
Then enable the document and generate the html.
When I review in browser, the diagram is in the collaboration page but not the names of the elements.
Hope you can re-create.

[Richard Lay]

I did not answer your question about what happens if the name of a section is changed.
This suggests that the section name and not a unique id is used to identify the section.
perhaps using both may be necessary.
hope this answers your question.

[Richard Lay]

As a quick suggestion ( as I have my day job), have a higher level in the Profile tab ( Profile 1, Profile 2) .
When an element is inserted and the type and stereotype occur in 2 profiles prompt for a profile number or name. Otherwise just profile 1. Store the profile number in Word. This approach would not bother new users unless they need a second profile. Alternately a document could have partitions where a unique profile is applied.

Of course if subreports were supported (By having an insert option that points to a separate word file) this would e simpler.
Hope this answers your question.

[Richard Lay]

The document is 120 pages and is a full report as a consulting deliverable. Being able to make changes and republish quickly is important capability. We will have a dozen or so reviewers, some who will read the whole thing and some who will concentrate on parts. Once complete the document will be constantly referred to in order to resolve specific issues about elements.
I hope this answers your question.

[Richard Lay]

I did not know I was being so silly. But we ARE doing real work, not testing. Using collaboration, reviewers can only comment down to the section level. With hundreds of elements we need comments on each one. If we divide this we have to manage multiple documents.

So the answer to the question is that it cannot handle complex documents.
Do you really search through each time for duplicates? It is time to use some supporting data structures.

[Author]

Posts