I think a new look-and-feel to the webconsole would be awesome. Before talking about the look-and-feel, I want to encourage the focus of the webconsole to be just that - a console into the running ActiveMQ instance. That means the functionality is limited to interactions with the internal broker:
<ul> <li> Display state of the broker (e.g. broker-stats, settings, queues and topics, messages stored in destinations) <li> Perform administration on the broker (e.g. create a queue, send a message, disconnect a client) <ul> Keeping the scope limited in this way will make sure the console is a great tool for anyone first learning ActiveMQ to get information on the broker operation and perform operations which can help with learning how the broker works. It is also great for those wanting a simple-yet-effective means to administer ActiveMQ. Is "web console" the best term here for this focus? Sounds good to me, but I can also see calling this a "dashboard" or "control panel". AngularJS and Bootstrap are awesome - I've started learning both recently. It looks like meeting To meet the terms of the MIT license for AngularJS, it is sufficient to put a copy of the license into the NOTICE file (http://www.apache.org/legal/resolved.html). To make the console responsive, are you thinking REST calls from Javascript? -- View this message in context: http://activemq.2283324.n4.nabble.com/The-ActiveMQ-community-deserves-better-Lets-vote-on-new-UI-for-AMQ-tp4680583p4680651.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
