Thanks for your input Mehmet! 
  
The Angular 2+ implementation of Patternfly would be my first bet as well, speaking of a pure HTML/JS application; unfortunately, as far as I read,
 it only began active development in the last couple of months (here [1] is the repo). I don’t know if they already have a detailed roadmap, but I don’t expect a beta shortly... 
  
[1] https://github.com/patternfly/patternfly-ng 
  
Claudio Mezzasalma | Eurotech 
  
Da: 
<kapua-dev-bounces@xxxxxxxxxxx> per conto di Mehmet Arziman <mehmet@xxxxxxxxxx> 
Risposta: kapua developer discussions <kapua-dev@xxxxxxxxxxx> 
Data: mercoledì 12 luglio 2017 18:00 
A: kapua developer discussions <kapua-dev@xxxxxxxxxxx> 
Oggetto: Re: [kapua-dev] Status of the PatternFly console? 
 
we are actually using Patternfly and really like it. We also came across the topic Claudio mentioned with only Angular 1.x support of Patternfly. 
 
I would vote for Patternfly, too ..despite the quoted technical challenges. If I remember correctly there are already activities in community to add Angular 2 (future Angular) support to Patternfly. I think that would be the "better train"
 to invest, instead of making a GWT implementation from scratch. 
 
Putting energy towards Angular is valueable, since alot of UI Devs usw it and can contribute. 
 
Patternfly is a good choice! 
 
BR Mehmet 
_________________________________________ 
 
Mit freundlichen Grüßen / Best regards 
 
 
I’m not ruling out Patternfly for GWT (even if this would mean to build such implementation from scratch), but I don’t know how much sense it makes
 such bridge in Vaadin. As far as I can see, Vaadin is great until you stick with their own set of widgets. As soon as you implement different widgets I’m afraid that the effort ramps up quite quickly (even if I’m only speaking from what I read, I didn’t try
 that directly). 
  
Patternfly for GWT could be a really interesting project, but not trivial nonetheless. I’d say that it needs to be thought, scheduled and organized
 carefully. 
  
Claudio Mezzasalma | Eurotech 
  
Why would that rule out PatternFly? There is something like Bootstrap for GWT, we could do something similar if GWT is the way to go. 
 
  
On Wed, Jul 12, 2017 at 3:37 PM, Mezzasalma, Claudio <Claudio.Mezzasalma@xxxxxxxxxxxx> wrote: 
Yes, I remember we already had this discussion, and that’s exactly what I am suggesting: we should find some Java
 based alternative. 
  
Since Patternfly is the UI library we have chosen, we have to figure out what technology we could leverage. GWT would
 probably need a Patternfly implementation itself. In the past few weeks I also had a look at Vaadin, but that would rule out Patternfly since we would need the same GWT implementation anyway. 
  
While I’ll do some research to find some other solutions, any input would be greatly appreciated. 
  
Claudio Mezzasalma | Eurotech 
  
Again, don't think we need NodeJS *at all* for implementing this. 
 
We could also, instead of using Angular, use plain PatternFly and go with JSP (or GWT, …). 
 
 
  
On Wed, Jul 12, 2017 at 12:04 PM, Mezzasalma, Claudio <Claudio.Mezzasalma@xxxxxxxxxxxx> wrote: 
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 
  
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 
 
 
 
 
 
 
 
 
 
 
 
 
_______________________________________________ 
kapua-dev mailing list 
kapua-dev@xxxxxxxxxxx 
To change your delivery options, retrieve your password, or unsubscribe from this list, visit 
https://dev.eclipse.org/mailman/listinfo/kapua-dev 
 
 
 
 
 
--  
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 
 
 
 
 
 
 
 
 
_______________________________________________ 
kapua-dev mailing list 
kapua-dev@xxxxxxxxxxx 
To change your delivery options, retrieve your password, or unsubscribe from this list, visit 
https://dev.eclipse.org/mailman/listinfo/kapua-dev 
 
 
 
 
 
--  
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 
 
 
 
 
 
 
 
 |