hawtio-forms does actually import patternfly's css already, though I'm sure tweaks
could be necessary here and there. Actually all of the hawtio projects already at least
work with patternfly and bring in the CSS definitions, though I'm sure we've a few
widgets in hawtio that don't have patternfly rules as they're custom controls
etc.
----- Original Message -----
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 (
http://angular-formly.com/ ) . 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.
I see two hurdles with Hawt.io forms:
1) Hawt.io form PatternFly compliance
2) Get our UXD folks to use Hawt.io forms for their designs
I definitely like the idea.
— Mike
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?
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev