[jira] [Created] (GUACAMOLE-59) Separate out the AngularJS Frontend

["Michael Jumper (JIRA)" <ji...@apache.org>]

Michael Jumper created GUACAMOLE-59:
---------------------------------------

             Summary: Separate out the AngularJS Frontend
                 Key: GUACAMOLE-59
                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-59
             Project: Guacamole
          Issue Type: Improvement
          Components: guacamole
            Reporter: Michael Jumper
            Priority: Minor


{panel:bgColor=#FFFFEE}
*The description of this issue was copied from [GUAC-1540|https://glyptodon.org/jira/browse/GUAC-1540], an issue in the JIRA instance used by the Guacamole project prior to its acceptance into the Apache Incubator.*

Comments, attachments, related issues, and history from prior to acceptance *have not been copied* and can be found instead at the original issue.
{panel}

Hi there, 

I just wanted to open up the discussion about how you think about this approach in general. If the angular side of the client side project would be separated out, it would be much easier to use it on another rest api, for example on other platforms.

We would like to provide you with a pull request if you're interested in this and open up new folder inside of guacamole-client. It would contain only the angular frontend and its dependencies.

Then we would create a separate pom and add the maven dependency to the guacamole frontend.

Why?

It would be possible to use the angular frontend outside of the java project and it's really easy to integrate into other ports of the web-frontend.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)