Sparx Systems Forum
Enterprise Architect => Suggestions and Requests => Topic started by: wolfgang.uhr on June 14, 2006, 12:14:05 am
-
Hello
I’ve just done a very first simple EA-Project and I want to add some points, I’ve missed. Let me begin with some points of the html-Report.
- You have to insert an output-data-path. There a “Web-Site” will be generated.
- It is very much better to store the css and js-files into a separate directory too. Normally, in the main directory there should be a file (<projectname>.html and not index.html)
- I’ve added attachments to some use-cases. These have been organized in a sub path of my EA-Project-Path and normally this path structure should be added into this web-site too. It is very difficult to place it into the root directory. Your customer has 20 files in the root or more and is looking for “index.html” – always.
- You can define your own styles and this is a very interesting idea, because the web-site itself is something “non transparent” and difficult (It is somewhat better to reduce it to a two-frame-solution instead of a three-frame-solution. I want do this, but the freedom is restricted hardly because
- You cannot import or export a HTML-style. All changes are restricted onto one project.
- Complex code generations are produced in one step.
- A label can only be generated by “#name#” and produces “<a href="../../../ Attachment.jpg">D:\pathOfAttachment\ Attachment.jpg</a>”. This is something difficult, if you send the complete web-site-folder to someone else. This person will not have a path “D:\pathOfAttachment”.
- The generation of pictures is encapsulated too. So a picture “EA11.png” is created. Why don’t you use “usecaseName.png” here? Furthermore I do not see any possibility to handle the constructions of the img-entry and the map-entries.
Up to now, these are the points, which make it difficult to use the html-report (my opinion).
Best regards
Wolfgang