asterics / WebACS

HTML5/JS version of the AsTeRICS Configuration Suite
Apache License 2.0
3 stars 2 forks source link

Add querystring option to WebACS URL to autoConnect to ARE #12

Closed deinhofer closed 6 years ago

deinhofer commented 6 years ago

If the WebACS is hosted by the ARE and loaded from that it would be handy, if the user could specify a URL to automatically connect to the ARE when loading the page.

This way, the ARE GUI could provide a feature to open and autoconnect the WebACS by a gui button and shortcut.

e.g. http://localhost:8081/webapps/WebACS/?autoConnect=true

kingcole commented 6 years ago

The WebACS already auto-connects to the ARE it is hosted from - so what's the point in adding a querystring option for that?

deinhofer commented 6 years ago

Just in case if somebody does not want that behaviour. But not a high priority.

sabicalija commented 5 years ago

:tada: This issue has been resolved in version 1.0.0 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket:

sabicalija commented 5 years ago

:tada: This issue has been resolved in version 1.0.0 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket:

sabicalija commented 5 years ago

:tada: This issue has been resolved in version 1.0.0 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket:

sabicalija commented 5 years ago

:tada: This issue has been resolved in version 1.0.0 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket:

sabicalija commented 5 years ago

:tada: This issue has been resolved in version 1.0.0 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket:

sabicalija commented 5 years ago

:tada: This issue has been resolved in version 1.0.0 :tada:

The release is available on GitHub release

sabicalija commented 5 years ago

:tada: This issue has been resolved in version 1.0.0 :tada:

The release is available on GitHub release

sabicalija commented 5 years ago

:tada: This issue has been resolved in version 1.0.0 :tada:

The release is available on GitHub release

sabicalija commented 5 years ago

:tada: This issue has been resolved in version 1.0.0 :tada:

The release is available on GitHub release