You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@polygene.apache.org by "Niclas Hedhman (JIRA)" <ji...@apache.org> on 2017/02/18 02:29:44 UTC

[jira] [Commented] (POLYGENE-46) Remote Envisage

    [ https://issues.apache.org/jira/browse/POLYGENE-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15872915#comment-15872915 ] 

Niclas Hedhman commented on POLYGENE-46:
----------------------------------------

Considering the deadlock bug in Envisage (which is inside the underlying graph library) at the moment, I think an HTML 5 version would be the best way forward.

D3 is probably the obvious choice to use, acquiring the model via JSON/HTTP.

Currently there is a Visitor pattern in Polygene Runtime, which is primarily there to support Envisage. Perhaps we should drop that pattern, and simply make the Model serializable to JSON instead. Once that is done, Envisage 2 can be started.

> Remote Envisage
> ---------------
>
>                 Key: POLYGENE-46
>                 URL: https://issues.apache.org/jira/browse/POLYGENE-46
>             Project: Polygene
>          Issue Type: New Feature
>            Reporter: Niclas Hedhman
>
> Envisage is a great tool, EXCEPT that it requires the code to run locally. It would great if Envisage could either be made to use a remote model, OR that Envisage is re-written to an HTML5 application, possibly leveraging JMX library (and make any changes to JMX lib needed)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)