Hi Matt, That's the idea. And more... This kind of process that splits frontend in two approached will highlight some points that can aviod implementing more frontends.
I mean, sometimes I can do something in a way it fits exactly with the current frontend but may not fit as well for the others. Having two different approaches will tell us what's the best way to do it. Best regards, > Very cool. In my opinion, we should move toward a much more flexible > front-end model where developers such as yourself should be able to > use something like wicket if they choose, but someone else should be > able to to use a pure HTML/JS front-end with REST services. > > > > > Question is. Should you accept this frontend? > > > > Kindest regards, > > Thank you for your support. >
