> On Jul 5, 2016, at 10:45 AM, Seth Leger <s...@opennms.com> wrote: > > I feel like in these cases, using Vaadin was like a prototyping step > because by using it, we didn't need to strictly separate the model, map > it to JAXB, then make a REST interface out of it while 5 people are > working on a UI on top of it. So maybe that was OK.
Here is what I recall from UI decisions that have been made during the life of the project: Baseline: JSP First attempt: JSF (failed) - Chosen and attempted before JS got it’s legs and seemed to integrate well with Hibernate Second attempt: GWT (Partial impl) - Chosen for all it’s promises: JS client for Java coders and browser compatibility Third attempt: Vaadin (Partial impl) - Chosen for the same reasons as GWT with the added Vaadin components but mainly for the server communication to help with the new Topology app. Forth attempt: AngularJS (Partial impl) - Chosen because GWT, and Vaadin seem too inflexible (hence a Java developer’s tool) So, what’s next? I can’t help but think that we’re not asking the right questions. There’s an elephant in the room and we’re focusing on, “What’s that smell?" :David David Hustace President The OpenNMS Group, Inc. 220 Chatham Business Drive, Suite 100 Pittsboro, NC 27312 +1 919 533 0160 x7734 *Quixotical*
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
