Hi,
What are the requirements for this widgets ?
Recently another user asked for the same functionality and we realized that
there are several limitations, the most important one - CORS.
Please create a mini application that shows the requirements and we can try
to finish it together. You can put
The requirements are pretty simple, the widget will contain a form field or two
that will be submitted back to a server via AJAX and present results back to
the user on the site hosting the widget. Think of the ubiquitous Twitter or
Facebook share widgets as existing similar examples to the
Hi, I have a need to create some javascript based widgets that will be deployed
to a variety of websites that are out of my control. I was planning on using
one of the existing javascript UI frameworks with json for callbacks to my
servers (which are running Wicket for normal consumer facing
I have the same question :
Is there a way to force wicket to generate absolute urls
for the page being rendered?
for javascript, onclick events and A urls
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Wicket-Widget-tp1867919p3535951.html
Sent from the Users forum
:50 AM, LePirlouit lepirlo...@hotmail.com wrote:
I have the same question :
Is there a way to force wicket to generate absolute urls
for the page being rendered?
for javascript, onclick events and A urls
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Wicket
Hi,
you are working with html. seems like a resonable approach from our end of
things.
I agree.
Well, I've postprocessed the output through a couple of regexps
because the task was too simple to be done by xslt or dom machinery.
But now I've hit another problem: links are generated relative
Hi all,
I'm looking for a fine and dandy (or just fine) way to create widgets
for igoogle, facebook and others. I would like to reuse our wicket
components and pages because the widgets are not that different from
our site but a shrunk version of it. The main problem I'm facing is
that wicket
wicket doesnt care about the markup type in general, it works on xml.
however, header contributions are special because they are
html-specific so it is assumed that if you use header contributions
you are working with html. seems like a resonable approach from our
end of things.
i would say just
