You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@rave.apache.org by Gonzalo Aguilar Delgado <ga...@aguilardelgado.com> on 2013/02/25 08:57:56 UTC
Still messing with wicket rendering. [Partially implemented]
Hello,
I'm just implementing a widget frontend rendering. While still missing
some important features it all seems to work well.
Even changing servers (shinding in another server) rendering is correct.
This is because you did it really well.
It took me some time to figure out the rave client initialization
sequence (rave javascripts) but now works...
I have to say that the html code changes drastically. It's more simple.
Much more.
But it comes with no problems. Major one is layouts implementation.
Wicket is not so "dynamic". But some fragments will do the work well
without much effort. I hope.
This is how it looks for main page:
https://plus.google.com/u/0/photos/117301646173740678910/albums/5635868114523664673/5848794662437168866
https://plus.google.com/u/0/photos/117301646173740678910/albums/5635868114523664673/5848794664675677762
I have to do all the Rave styling and add missing things (admin,
marketplace, multipage, etc). But now that rendering is working it
should not be a problem.
I plan to maintain it when it's finished.
Question is. Should you accept this frontend?
Kindest regards,
Thank you for your support.
Re: Still messing with wicket rendering. [Partially implemented]
Posted by Gonzalo Aguilar Delgado <ga...@aguilardelgado.com>.
I made an error.
Change: I'm just implementing a widget frontend rendering.
by I'm just implementing a wicket frontend rendering.
El lun, 25-02-2013 a las 08:57 +0100, Gonzalo Aguilar Delgado escribió:
> Hello,
>
> I'm just implementing a widget frontend rendering. While still missing
> some important features it all seems to work well.
> Even changing servers (shinding in another server) rendering is correct.
> This is because you did it really well.
>
> It took me some time to figure out the rave client initialization
> sequence (rave javascripts) but now works...
>
> I have to say that the html code changes drastically. It's more simple.
> Much more.
>
> But it comes with no problems. Major one is layouts implementation.
> Wicket is not so "dynamic". But some fragments will do the work well
> without much effort. I hope.
>
> This is how it looks for main page:
>
> https://plus.google.com/u/0/photos/117301646173740678910/albums/5635868114523664673/5848794662437168866
>
> https://plus.google.com/u/0/photos/117301646173740678910/albums/5635868114523664673/5848794664675677762
>
>
> I have to do all the Rave styling and add missing things (admin,
> marketplace, multipage, etc). But now that rendering is working it
> should not be a problem.
>
> I plan to maintain it when it's finished.
>
> Question is. Should you accept this frontend?
>
> Kindest regards,
> Thank you for your support.
Re: Still messing with wicket rendering. [Partially implemented]
Posted by Gonzalo Aguilar Delgado <ga...@aguilardelgado.com>.
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.
>
Re: Still messing with wicket rendering. [Partially implemented]
Posted by Matt Franklin <m....@gmail.com>.
On Mon, Feb 25, 2013 at 2:57 AM, Gonzalo Aguilar Delgado
<ga...@aguilardelgado.com> wrote:
> Hello,
>
> I'm just implementing a widget frontend rendering. While still missing
> some important features it all seems to work well.
> Even changing servers (shinding in another server) rendering is correct.
> This is because you did it really well.
>
> It took me some time to figure out the rave client initialization
> sequence (rave javascripts) but now works...
>
> I have to say that the html code changes drastically. It's more simple.
> Much more.
>
> But it comes with no problems. Major one is layouts implementation.
> Wicket is not so "dynamic". But some fragments will do the work well
> without much effort. I hope.
>
> This is how it looks for main page:
>
> https://plus.google.com/u/0/photos/117301646173740678910/albums/5635868114523664673/5848794662437168866
>
> https://plus.google.com/u/0/photos/117301646173740678910/albums/5635868114523664673/5848794664675677762
>
>
> I have to do all the Rave styling and add missing things (admin,
> marketplace, multipage, etc). But now that rendering is working it
> should not be a problem.
>
> I plan to maintain it when it's finished.
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.