0 Replies Latest reply on Aug 5, 2014 11:04 AM by houseofpretty

    running into a LOT of issues trying to incorporate Edge Animate content with other technologies

    houseofpretty Level 1

      we're trying to create a self-standing sales document (esentially a powerpoint) taht a sales staff will control via a WordPress backend, which will allow then to simply toggle which sales case studies are included in the preso.


      the main document structure, to give the presenter something to work within in the course of a meeting, is specced out as http://flowtime-js.marcolago.com


      each section (five of them) is a separate EA animation on a separate "page" of this tool. each sales preso is also on a separate "page."


      here's what we're running into:


      1) incorporating more than one EA work into an html document is tedious. each instance of the stage needs to be hand-edited, and cannot be saved into the EA document itself (it would help if we could simply retitle the stage within the document, or at the very least have EA add its random numbers to the stage ID of each document, rather than everything having an ID of "stage" with random numeric classes upon output), which means this needs to be remembered somewhere else, and then done by hand upon each export.


      2) EA JS files must live immediately next to the EA html documents in the file structure, which turns into a big problem quickly, especially in cases (like WordPress) in which the site doesn't actually have files—and turns into a complete wreck inside the server structure if we can't keep all the like-files together for future work. if JS files have references automatically added to them, why not let the developer choose where they need to be by selecting an output location?


      3) there is no way to talk to EA about whether or not to output boilerplate dependency files (JQuery and Edge.min inside edge_includes). very minor quibble.


      I’m going to address all of this separately as actual questions, but right now... I have to say EA has a long way to go before being easily usable in a real publishing environment with many moving pieces.