I think we should definitely set a common ground and “someone” decide to make
${FRAMEWORK} the OpenNMS UI framework. So everybody working in code can do
refactorings in the same directions. With the current status we diverge the
development and this makes it ridiculous complicated for all of us. Cause we
start developing against each other.Just to summarize, We haven’t replaced GWT and JSP pages and what else old things are left in the UI. We should really start talking about, what is the UI software architecture and strategy. Instead of unifying things we have just added things. - JSP stuff with legacy styles - GWT is still left - Vaadin was added and got misused with OSGi, single Vaadin apps, everything has its own theming - this is quite a large part in the UI - Angular JS was added in the provisioning probably also with own theming - The Topology UI is its own place, I think Markus von Rüden knows most about it right know IMHO at least core contributor should pull in the same direction. The current stuff we have makes it quite ridiculous expensive to get features in. I personally don’t care about the UI technology I’m just interested to move with all developers in the same direction and make the development less painful and less time consuming as it is right know. Probably DevJam should be a place to get an idea how to proceed with that stuff. I think Seth, Jesse, Alejandro, Markus, Christian and Ben spent a lot of time in UI development and should be the ones who define the architecture for OpenNMS - cause they have to work with it most of the time. Just my two cents. > On 05.07.2016, at 13:45, Seth Leger <s...@opennms.com> wrote: > > I agree. I think that a Javascript-based UI is the future for most CRUD > pages such as viewing lists of data and editing simple configs. > > My goal with the Angular list pages is to add useful filtering to the > lists with weak filtering (notifications, outages) which will address > bugs that have been reported for a very long time with OpenNMS's web UI: > > http://issues.opennms.org/browse/HZN-427 > > After that works well, we can move to replacing the event, alarm, and > node lists with Angular as well. Angular simplifies the UI code > significantly. I did a quick calculation yesterday... the core Angular > list code is about 700 lines plus about 500 lines per implementation > (notification, outage, etc) and hasn't been refactored to consolidate a > lot of things. Still, this 1200 lines of code is replacing 4000+ lines > of JSP + Java. :) > > -- Seth > > > On 7/5/16 7:27 AM, Ronny Trommer wrote: >> IMHO: If we add more Angular JS stuff and more Vaadin stuff - we start >> to get a common UI strategy. >> >>> Begin forwarded message: >>> >>> *From: *Seth Leger <s...@opennms.org <mailto:s...@opennms.org>> >>> *Subject: **[opennms-cvs] [OpenNMS/opennms] 360737: Added Angular >>> outage list that is mostly working.* >>> *Date: *5. Juli 2016 um 12:10:38 MESZ >>> *To: *opennms-...@lists.sourceforge.net >>> <mailto:opennms-...@lists.sourceforge.net> >>> *Reply-To: *Seth Leger <s...@opennms.org <mailto:s...@opennms.org>> >>> >>> Branch: refs/heads/jira/NMS-2656/notifications >>> Home: https://github.com/OpenNMS/opennms >>> Commit: 3607378064d6a3ad1f30987af0e6bd55ac2ef699 >>> >>> https://github.com/OpenNMS/opennms/commit/3607378064d6a3ad1f30987af0e6bd55ac2ef699 >>> Author: Seth Leger <s...@opennms.org <mailto:s...@opennms.org>> >>> Date: 2016-07-05 (Tue, 05 Jul 2016) >>> >>> Changed paths: >>> M opennms-model/src/main/java/org/opennms/netmgt/model/OnmsOutage.java >>> M >>> opennms-model/src/test/java/org/opennms/netmgt/model/OnmsOutageTest.java >>> M opennms-webapp-rest/src/test/resources/v1/outages.json >>> A opennms-webapp/src/main/webapp/js/angular-onmsList-outage.js >>> R opennms-webapp/src/main/webapp/outage/current.jsp >>> A opennms-webapp/src/main/webapp/outage/indexNew.jsp >>> A opennms-webapp/src/main/webapp/outage/main.html >>> >>> Log Message: >>> ----------- >>> Added Angular outage list that is mostly working. >>> >>> > > ------------------------------------------------------------------------------ > Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San > Francisco, CA to explore cutting-edge tech and listen to tech luminaries > present their vision of the future. This family event has something for > everyone, including kids. Get more information and register today. > http://sdm.link/attshape_______________________________________________ > Please read the OpenNMS Mailing List FAQ: > http://www.opennms.org/index.php/Mailing_List_FAQ > > opennms-devel mailing list > > To *unsubscribe* or change your subscription options, see the bottom of this > page: > https://lists.sourceforge.net/lists/listinfo/opennms-devel
signature.asc
Description: Message signed with OpenPGP using GPGMail
------------------------------------------------------------------------------ Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape
_______________________________________________ Please read the OpenNMS Mailing List FAQ: http://www.opennms.org/index.php/Mailing_List_FAQ opennms-devel mailing list To *unsubscribe* or change your subscription options, see the bottom of this page: https://lists.sourceforge.net/lists/listinfo/opennms-devel
