Accessing EA objects from HTML embedded in EA?

[Svend Erik Nygaard]

Is it possible to open a (trusted) html page in EA and let it access EA objects?
I want to create special userfriendly searchresult pages in HTML in EA. And then have scripts in the result page letting the EA user navigate to wanted elements ('links' to EA elements).
Similar with other pages, e.g. a page displaying an element with related elements - in a manner meaningfull to misc. analyts.
The HTML page will be triggered and dispalyed within EA.
The HTML page will be generated from a web server (via SQL access to EA)
?

[Geert Bellekens]

Hi,

Although that might be possible, I really don't understand why you would want to go via an HTML page to search EA elements.
Wouldn't it be much simpler to do that in a regular window?

Geert

[Svend Erik Nygaard]

1) Reuse of code and logic also to be implemented on a web/app server accessing EA. It would be nice to reuse not only search logic and presentation, but also other logic and presentation implemented on a web solution. That would also give the users a common interface between EA and the WEB presentation of the repository. I realize that the logic (e.g. fuzzy search logic etc - could be reused by calling for instance a web service) - but I'd be happy to reuse also the HTML GUI.
2) I like the layout/presentation styles of HTML pages.
3) Reuse of skills. Alternative is Visual studio? - I don't know that development environment (I guess you developed your EA Navigator in Visual Studio?).
PS: I want to open the HTML page in an EA window, possibly the standard pane where EA opens HTML pages.  - triggered by e.g. the user choosing from a context menu on a given element.

[Svend Erik Nygaard]

.. and, of course:
4) being able to use a standard report generator (e.g. MS Report Builder; Jasper report builder) to generate such neatly presented, structured pages with the views relevant to different users - with links to EA elements
- inside EA, opened/displayed on request from EA elements etc.
PS: The report would be defined/designed in the report tool, and runtime generated by the report generating engine from/on the web server – and displayed inside EA from which it was requested