Products

Home Forums eaDocX queries generate eaDocX files automated

Home Forums eaDocX queries generate eaDocX files automated

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #9229
    Philipp Woditsch
    Participant

    Hi,

    i am thinking about the possibility to generate eaDocX files automatically, e.g. by starting a script in EA or the usage of sth. like a eaDocX API.

    The idea is to automatically generate updated eaDocX files from one EA project without any manual process steps.

    Is there a possibility to open files and start generation without using the eaDocX GUI?

    Regards,
    Philipp

    #9230
    Administrator
    Participant

    I’ve never tried calling into an addin from inside an ea script. Is this possible?
    If so, what would the eaDocX API call look like? That is, what parameters would you expect to pass?
    We have the beginnings of this function in the Auto-template capability, so internally we might have most of the moving parts.

    #9231
    Philipp Woditsch
    Participant

    The idea would be to open an already configured docx file (including defined eaDocX sections and profiles) and trigger the generating process.

    #9232
    Philipp Woditsch
    Participant

    We have a solution which enables to call EA AddIn functions based on a script (using a separate thread and windows named pipes…). Calling functions of an own developed AddIn works properly with this. I assume this would also work with eaDocX, but therefore we need to know the eaDocX functions (e.g. the eaDocX function which is called when using “Generate Document” or “Open Word document”).

    #9233
    eadocX Support
    Participant

    You really as desperate….
    sadly, it’s not that simple….eaDocX is designed to work with a UI, so I would need to cleanly separate the UI from the engine.
    To get you started,
    (in vb.net)

    Dim g As New WordGenerator(neweaDocXMain)
    g.profile = myProfile ‘Profile is an instance of DgDocumentProfile. I get if from the UI, which it turn got it from the current document.
    g.activeDocument = aDoc ‘ This needs to be an instance of Microsoft.Office.Interop.Word.Document

    ‘(4) Generate the document
    g.RunDocument()

    You might be able to create a new WordGenerator with a null parameter, as that’s just a ref to the current UI, and I seem to check if there really is one.

    I can’t help feeling that, without some radical re-factoring from me, this is doomed…

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.

Compare licence prices

Choose the licence that’s right for you and your team

Prices

Download a free trial

Download eaTeamWorks today for several free for life features, plus no obligation, 30-day trials of all the products: eaDocX, ea Revision Manager, eaSheets, Model Expert and PortfolioManager. Discover for yourself why we sell the world’s best-selling Enterprise Architect extension.

Download