Why would we benefit moving to FreeMarker? I support your decision,
just curious and want to know why. Also, what else could you work on?
BTW, making decisions like a JSF->FreeMarker switch needs to be done
together on this list. I (and others?) didn't even know you were doing
this. This is important to avoid things like messy merge conflicts.
On 9/19/2013 5:03 AM, Viliam Rockai wrote:
I'm working on KEYCLOAK-60 Replace JSF in forms with a template
It's nearly done, I'm just working on some final refinements/testing. I
have used FreeMarker as a templating engine:
I've done only the JSF -> FreeMarker transition in this step, next step
would be to adapt some cool design from Gabriel.
On 09/19/2013 03:29 AM, Bill Burke wrote:
> This may change depending on what we decide for M1, but I'm working
> right now on:
> * Getting Gabriel's new screens incorporated as best as possible into
> existing admin UI
> * I've designed on paper the core screens for admin UI. I'll be
> implementing based on Gabriel's existing styles. I'll need to have a
> feedback iteration loop with Gabrield to move forward. It has to be
> give and take. Meaning, I need to be allowed to improve Gabriel's
> screens and vice-versa. It's seemed more one-way so far...
> I'll have something to show by next Tuesday. I'll be committing early
> and often before then if you want to see what's going on.
keycloak-dev mailing list
JBoss, a division of Red Hat