I still have to double check, but theoretically speaking we should get in Angular-Patternfly 4.0 the Table component we were missing.
However we should still discuss about the approach we want to take on an higher level. Angular-Patternfly 4.0 means we should use AngularJS 1.5+,
since using Angular 4+ is not recommended even if (theoretically) the conversion of Patternfly directives to AngularJS components would allow us to do so. AngularJS (now at version 1.6.5) is still supported, but it’s no news that “in the future” it will be
dropped in favor of Angular (now at 4.2.6), that is a completely different framework.
Last but not the least, as of now the Patternfly Console is way too indipendent from the rest of the Kapua ecosystem, being a NodeJS based HTML/JS
application. I think we should try to “bring it back” as near as the ecosystem as possible.
Claudio Mezzasalma | Eurotech
Da:
<kapua-dev-bounces@xxxxxxxxxxx> per conto di Jens Reimann <jreimann@xxxxxxxxxx>
Risposta: kapua developer discussions <kapua-dev@xxxxxxxxxxx>
Data: mercoledì 12 luglio 2017 11:26
A: kapua developer discussions <kapua-dev@xxxxxxxxxxx>
Oggetto: [kapua-dev] Status of the PatternFly console?
I just wanted to check if there is any update on the PatternFly port.
From what I've seen PatternFly 4 has been released as of May 2017 [1] and so there should be no more blocker for making use of that in Kapua, right?
Cheers
Jens
[1] https://blog.patternfly.org/patternfly-roadmap-update/
--
Jens Reimann
Senior Software Engineer / EMEA ENG Middleware
Werner-von-Siemens-Ring 14
85630 Grasbrunn
Germany
phone: +49 89 2050 71286
_____________________________________________________________________________
Red Hat GmbH, www.de.redhat.com,
Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham, Michael O'Neill