Messages

1

Automation Interface, Add-Ins and Tools / Re: Format of internal documentation when exportin

« on: September 03, 2007, 12:04:00 am »

This is great, *but* it means that you have to process both the XMI and go direct via the automation interface to get the RTF docs and then tie them back together again, which would be a lot of extra effort and a much more complex solution.

It is certainly a workaround if it is *impossible* to translate rtf docs from the XMI, but why would you put them in the XMI if it were completely impossible to get them out again?

Is there a way of translating the strings containing the RTF docs in the XMI?

Thanks for your help

2

Automation Interface, Add-Ins and Tools / Re: Format of internal documentation when exportin

« on: August 31, 2007, 07:45:50 am »

I need to get hold of the contents of the embedded rtf files in the XMI as well.

Could Sparx please let us both know what the format of the str.dat is?

(I would also like to be able to get hold the embedded RTF files to convert them to XML and XSL-FO for further processing)

T.

3

Automation Interface, Add-Ins and Tools / Re: Format of internal documentation when exportin

« on: August 31, 2007, 07:45:14 am »

I need to get hold of the contents of the embedded rtf files in the XMI as well.

Could Sparx please let us both know what the format of the str.dat is?

(I would also like to be able to get hold the embedded RTF files to convert them to XML and XSL-FO for further processing)

T.

4

Automation Interface, Add-Ins and Tools / Re: Format of internal documentation when exportin

« on: August 31, 2007, 07:43:02 am »

This is my problem as well

Could Sparx please let us both know what the format of the str.dat is?

(I would also like to be able to get hold the embedded RTF files to convert them to XML and XSL-FO for further processing)

T.

5

Automation Interface, Add-Ins and Tools / Re: Format of internal documentation when exportin

« on: August 31, 2007, 07:42:34 am »

This is my problem as well

Could Sparx please let us both know what the format of the str.dat is?

(I would also like to be able to get hold the embedded RTF files to convert them to XML and XSL-FO for further processing)

T.

6

Automation Interface, Add-Ins and Tools / Re: XHTML for comments

« on: July 18, 2007, 05:01:30 am »

To clarify we are using the Document Artifact component and then importing rtf files, generated from Microsoft Word to load analysis narrative documentation into EA projects.

This is exported in the XMI as a Tagged Value called modeldocument as a base64-encoded binary string.

We would like to have something intelligible like XHTML rather than RTF in the XMI file so that we can process it with the rest of the file and would also like a less cumbersome process to get documents into Sparx in the first place.

Has anyone implemented an add-in to incorporate an XML-based editor in EA, which saves its content within the EAP file (our business architects want everything in one file - hence the desire to embed the narrative documentation) and would be exported in an XMI export (e.g. as a tagged value)?

Thanks for your help, regards,

Tim