<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 23 Jul 2015, at 06:47, Stan Lewis <<a href="mailto:stlewis@redhat.com" class="">stlewis@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">Is this all form work? Might want to consider using hawtio's form plugins perhaps, all you need to come up with then is a json schema, live examples at -> <a href="http://forms.hawt.io" class="">http://forms.hawt.io</a><br class=""></div></blockquote><div><br class=""></div>Stan, thanks for the tips. Much of this is forms work, and I really like the declarative nature of hawt.io forms (reminds me of Angular Formly (<a href="http://angular-formly.com/" class="">http://angular-formly.com/</a>) . One of the difficulties we face with form libraries in general, is their PatternFly compliance. We work closely with our UXD counterparts and they usually provide the html/css (using PatternFly). We take those designs (the view) after lengthy discussions between the teams and integrate them with our front-end/backend. So as developers we are not the only ones working with the html/view.</div><div><br class=""></div><div>I see two hurdles with Hawt.io forms:</div><div><br class=""></div><div>1) Hawt.io form PatternFly compliance</div><div>2) Get our UXD folks to use Hawt.io forms for their designs</div><div><br class=""></div><div>I definitely like the idea.</div><div><br class=""></div><div>— Mike</div><div><br class=""></div><div>P.S. I know there is a current effort in PatternFly to create angular wrappers around their components. Perhaps this is great area of overlap to participate in?</div><div><br class=""></div><div><br class=""><blockquote type="cite" class=""><div class=""><br class="">----- Original Message -----<br class=""><blockquote type="cite" class="">hey,<br class=""><br class="">for upcoming tasks like<br class=""><br class="">"define and manage jdbc driver"<br class="">"define and manage data source"<br class="">and others<br class=""><br class="">I wonder if we could speed up the UI development a bit by<br class="">creating some skeletons for html , and also ts-code<br class="">by running some scripts over the resource type<br class="">definitions we have.<br class=""><br class="">This is not meant to be the 100% UI, but rather a start where<br class="">the UI folks can improve on, but which could give us a (working)<br class="">head start.<br class=""><br class="">Does that make any sense?<br class=""><br class=""> Heiko<br class="">_______________________________________________<br class="">hawkular-dev mailing list<br class=""><a href="mailto:hawkular-dev@lists.jboss.org" class="">hawkular-dev@lists.jboss.org</a><br class="">https://lists.jboss.org/mailman/listinfo/hawkular-dev<br class=""><br class=""></blockquote>_______________________________________________<br class="">hawkular-dev mailing list<br class=""><a href="mailto:hawkular-dev@lists.jboss.org" class="">hawkular-dev@lists.jboss.org</a><br class="">https://lists.jboss.org/mailman/listinfo/hawkular-dev<br class=""></div></blockquote></div><br class=""></body></html>