not 100% sure, but you could try:
input type=checkbox onclick=return false; readonly=readonly /
On Nov 17, 2007 2:28 AM, mclev [EMAIL PROTECTED] wrote:
Nick Heudecker wrote:
For textareas and textfields I always do onfocus='this.blur();'. It
might
work for checkboxes as well.
Well yeah. I never meant for you to put actual code out there. But
like you said a small quickstart with a readme would be great.
-igor
On 11/16/07, Ernesto Reinaldo Barreiro [EMAIL PROTECTED] wrote:
Hi Igor,
The main problem I see here is that there is not a single approach on
building a
And then to be even more clear
when you do the code below that eelco has given you as an example
the back button wil NOT work anymore.
johan
On Nov 17, 2007 2:23 AM, Eelco Hillenius [EMAIL PROTECTED] wrote:
You could also explain some of the details of what should be returned by
our
Hi,
On Nov 16, 2007 6:12 PM, dado [EMAIL PROTECTED] wrote:
Edgar,
I am curious: what version of Jetty are you using? Where did you get the
appropriate bundles? Could you share your Activator code that starts Jetty?
Thanks again,
I use the http service available in Apache Felix.
br,
Now that you have gotten a ton of feedback, I'm interested in if and how you
adjusted your pros and cons. And of course how the presentation went.
Martijn
On Nov 15, 2007 8:35 PM, mraible [EMAIL PROTECTED] wrote:
FWIW, I'd like to replace the pros and cons (my opinions) with some that
are
Ernesto,
Your Equinox-based sample app using wicket would be of great interest!
Many thanks,
David
Ernesto Reinaldo Barreiro wrote:
Hi Igor,
The main problem I see here is that there is not a single approach on
building a wicket based OSGi application. For instance, we have taken a
I have following related problem with wicket-phonebook and FilterToolbar API
Change:
When I hit back button and then try to sort using column names in the
Actions header of the table,
I receive:
WicketMessage: Error attaching this container for rendering:
[MarkupContainer [Component id =
Hi,
I have a problem with page logic works different in Firefox and IE.
The code shows 4 buttons but only 2 are visible at the same time. There is
a Candidate/NotCandidate-Button pair and a Observer/Not-Observer pair.
With Firefox it works perfectly but with IE only the candidate logic is
On Fri, 16 Nov 2007, Andy Barlow [Deftex] wrote:
I guess what I really need to do mock off the getEJBService() of
MainApplication to return a mock object that serves the data to the
test pages.
Problem is, I'm not sure how to achieve that without initialising
WicketTester with a mock
When user presses the back button, wicket need to reconstruct the
previous page instance. And the previous page instance is stored in
second level cache. Wichet is a statefull framework, it maintains page
instances. Most of the time the url only contains page id and page
version. This is used to
On Nov 15, 2007 9:06 PM, Igor Vaynberg [EMAIL PROTECTED] wrote:
for me, pros would be:
trully object oriented: allows great encapsulation/extension/reuse
code centric: easier refactoring, maintenance
trivial component creation: awesome reuse of high level functionality
inter/intra projects
I was trying to modify underlying data provider, which caused the error.
Apologies for mail deluge.
Pavol
I have following related problem with wicket-phonebook and FilterToolbar
API Change:
When I hit back button and then try to sort using column names in the
Actions header of the table,
This would be a great benefit for mee too. I have the same problem and I
currently use a self updateing Timer to trigger an AjaxRequestTarget to open
the modal window.
Stefan
-Ursprüngliche Nachricht-
Von: Matej Knopp [mailto:[EMAIL PROTECTED]
Gesendet: Samstag, 17. November 2007
On Nov 16, 2007 5:26 PM, Johan Compagner [EMAIL PROTECTED] wrote:
and does it really work?
Why wouldn't it work?
For our projects we can store our users in our own database and do our
own authentication, so i don't really have a need for it (yet :)). But
i can certainly see people having to
Personally i prefer overriding protected IModel getListItemModel(final
IModel listViewModel, final int index) which has the same effect but
allows you to create a reusable subclass from listview which always
uses a compoundpropertymodel.
you can simply do return new
So i guess one of the things i misunderstood earlier was that i assumed that
the pageMap maintains the latest page-instance/version (in the active
session) of all the different page-components, but as it turns out its just
the latest accessed page's instance which is kept in the session, and
I understand that the browser back button doesnt really come in the above
context, but you agree to the fact that one has to do a no-store to actually
LET wicket load the page from the SLC otherwise this back button support by
wicket (which is considered to be one of the main features of it)
So basically i meant setting no-store in your response header so that the
browser doesnt load the page from its local-cache, and instead sends the
request to the server and let wicket load the last serialized page.
Farhan.
Eelco Hillenius wrote:
I understand that the browser back button
Well i think it is required, at least as far as the browser back button is
concerned (which is one of the features of wicket i.e. back button
support), unless otherwise as you said where one explicitly wants to make a
call to the old versions, but even with that i wonder how would one go about
Guys,
Yet another question...
Does wicket handles double form submission in anyway ? like if the user
clicks the back button where the previous page was a result of a form
submission, which could result in double form submission..OR otherwise
refreshes that page..
Farhan.
--
View this
hmmm..so correct me if its not the right understanding..i.e. the only time
wicket would be fetching the older page versions is when a user hit the back
button and clicks on a link (or submit a form) from that previous page, and
with that whatever page-version those links/forms were linked to
Hi Timo,
Thanks for the suggestion -- I definitely agree that using the source code
and reading it thoroughly will help us understand the inner workings of
Wicket. However, I would call that a white box approach. :)
My hope was to see if I might find some explanations and answers from the
22 matches
Mail list logo
