Ok, thanks for all this!
I'm new to Ajax, so I'll have to play around with this so I can better
appreciate the solution proposed below.
Cheers,
Dave
On Fri, 2007-04-20 at 00:26 -0700, Igor Vaynberg wrote:
> i dont really get what scriptaculous, etc has to do with it. and i
> dont get why you
Ok, that's interesting.
So, you guys are suggesting that a reasonable approach to the problem
would be to find a lib that I like (such as scriptaculous), set them up
on a widget server, then access them either as standalone javascript
widgets or in wicket via ComponentAsWidgetContainer?
The only
just to add
an important point is
this is completely transparent to the widget panel. it is just a panel. it
doesnt know it is being inlined via javascript into another page - this is
the job of ComponentAsWidgetContainerPage
one thing to consider is that you would need to rewrite urls so they
afaict there is no servlet.
what he does is have a bookmarkable page which he mounts. all this page does
is read some parameter off url and based on that parameter add the right
panel to itself. it then renders this panel, and wraps the output in
document.write() call.
well this is almost accura
Hi, Barrett,
Thank you for this. Very interesting.
So, allow me to rephrase to make sure I'm understanding you on this.
The requirement is:
- Continue to use Wicket as web framework
- Be able to reuse javascript widgets outside of wicket
- Reuse same javascript code for both usage patterns
Forgot to mention, to use this just create a page class that extends
ComponentAsWidgetContainerPage and then implement the getComponent(id)
method. This method should return the component(usually a panel) that you
wish to make into a widget, with the id set to the id passed in to the
getComponent
David,
We recently had a requirement where we wanted to include a panel from our
new Wicket app on one of our non-wicket legacy applications. To do this I
created a behavior and container page which will spit out any component
between a javascript document.write method. Then on your non-wicket pag
Hello!
We are currently happily using Wicket to develop our web applications.
Wicket rules!
However, now we are required to make "embeddable Ajax components", you
know, like Google Maps that anybody can embed in their own html.
Can anybody suggest an approach that would allow us to keep as mu
