Great. Thanks for adding it.
On 12/14/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
Cool, thanks for contributing!
Eelco
On 12/14/06, Anders Holmbech Brandt <[EMAIL PROTECTED]> wrote:
> Hello wicket-users,
>
>I have now added all the sources for wicket assistant to the
>wicket-stuf
though hevvyly drunk, I still manange to say thank you:) Guess this is the last
xxxmas company party of the year...:)
-Original Message-
From: [EMAIL PROTECTED] on behalf of Igor Vaynberg
Sent: Thu 14-12-2006 18:36
To: wicket-user@lists.sourceforge.net
Cc:
Subject:Re
Cool, thanks for contributing!
Eelco
On 12/14/06, Anders Holmbech Brandt <[EMAIL PROTECTED]> wrote:
> Hello wicket-users,
>
>I have now added all the sources for wicket assistant to the
>wicket-stuff project. Feel free to help out getting it better.
>I suggest that we take the develo
With http://issues.apache.org/jira/browse/WICKET-136 you could do:
class PhoneNumber extends FormComponentPanel {
private String one;
private String two;
TextField oneField;
TextField twoField;
public PhoneNumber(String id, IModel m) {
super(id, new CompoundPropertyM
Abackground with Calypso integration is highly recommended butwould consider
candidates who have had experiencing implementingcompeting platforms.
For many years, the successful combination of these three entities has beenthe
key to corporate profitability.
However, we will keep your resume on f
fwiw a common pattern i use is to do the conversion in an model decorator
something like
class StringToPhoneModel implements IModel {
private final IModel stringModel;
public StringToPhoneModel(IModel stringModel) { this.stringModel=stringModel;
}
public Object getObject(Component c) { return ne
I believe I have it working as such:
class PhoneNumber implements Serializable {
private String one;
private String two;
public PhoneNumber(String str) {
// Parse str and set one and two
}
// setters & getters *snipped*
public String toStri
It is actually quiet a bit different.
all visited pages except the most recent are saved to disk instead of being
held in session. the session now only holds the most recently accessed page.
the pages saved on disk are only needed when the user uses the back button,
which is probably not that oft
Other points of consideration is long term maintenance. A component
oriented framework like Wicket encapsulates component functionality into a
black box that can be used in many different contexts and still work as
designed. The same effect is very difficult to achieve with custom tags
(especially
Ryan wrote:
> [...]
> 1. Session support. Many other web frameworks do not use sessions out of
> the box. Wicket uses the session extensively to store the render state
> of most renders. This leads to a large session and if you are not
> careful a VERY large session. I understand Wicket 1.3 will ad
So String work on Person is a toString value of Phone
So somewhere you can do:
new Phone(string) to get phone back i guess?
then something like this:
public PhoneNumber(String id, IModel m) {
super(id, new Model(new Phone(m.getObject(;
On 12/14/06, Jonathan Sharp <[EMAIL PROTECTED]>
On 12/14/06, Johan Compagner <[EMAIL PROTECTED]> wrote:
how do you map the String work to a phone class anyway?
i guess it could be like this:
class Person
{
Phone work;
Phone cell;
}
Then i could understand the example But currently i don't see how
to "convert" the string work to a Phone
how do you map the String work to a phone class anyway?
i guess it could be like this:
class Person
{
Phone work;
Phone cell;
}
Then i could understand the example But currently i don't see how
to "convert" the string work to a Phone object that has 3 strings..
johan
On 12/14/06, Jonathan
It should work AjaxSubmitButton is a IFormSubmittingComponent component so
this code:
IFormSubmittingComponent submit =
(IFormSubmittingComponent)getPage().visitChildren(
IFormSubmittingComponent.class, new IVisitor()
{
public Object compone
I have a Page level Model:
class Person {
String work;
String cell;
}
I have a component such as:
class PhoneNumber extends Panel {
class Phone {
String one;
String two;
String three;
public String toString() {
return one + two + three;
}
}
Yeah, I don't claim that read only and disabled is the same. But i think
that when user wants a read only text fields, it actually should be
disabled (so that it's not updated when form is processed). Even if the
user fakes the form post values.
-Matej
Johan Compagner wrote:
> last time i chec
last time i checked. IE7 also did change that i think
So even a disabled textfield i was still able to select text.
But it is more the look (and feel) that is for me a distinction between
readonly and disabled
johan
On 12/14/06, Matej Knopp <[EMAIL PROTECTED]> wrote:
No, but i think that for
When a user presses "Back" in a browser the page doesn't render again at
least
not in the serverside. By default it is a puur client side thing. (you can
configure
the page in configureResponse to always go back to the server when a user
hits back)
So what gets throwed at what time?
On 12/14/06,
No, but i think that for disabled textfields read only is a nice option,
because you can still select the text.
Anyway, if you want to have read only text field, you should disable it.
Because if it is not disabled, user can still change the text (fake
post) and the model gets updated. With dis
But disabled and readonly are not the same in html..
johan
On 12/14/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
Exactly, that's the way to go, and that's why onDisabled is in there!
Eelco
On 12/14/06, Matej Knopp <[EMAIL PROTECTED]> wrote:
> I'd rather override isEnabled and onDisabled,
try changing the id of your button to something other then "submit"
-igor
On 12/13/06, ChuckDeal <[EMAIL PROTECTED]> wrote:
I have a Page that has a Form with some select boxes in it and, outside
the
Form, I have three buttons (submit[AjaxSubmitButton], reset[AjaxLink],
cancel[AjaxLink]).
I
Hello wicket-users,
I have now added all the sources for wicket assistant to the
wicket-stuff project. Feel free to help out getting it better.
I suggest that we take the development related discussions to the
wicket-stuff developer list.
Its located under "wicket-idea-plugin".
I don't mean to bump this, but I do want to make sure that I am using the
AjaxSubmitButton properly. In each instance that I had previously used the
button, it was OUTSIDE the Form, I had to move it inside the Form in order
to avoid the exception. Was this a known side-effect of the change? If
we should at least try to get some builds out.
johan
On 12/14/06, Francis Amanfo <[EMAIL PROTECTED]> wrote:
Hi Wicket devs,
I'm expecting great presents for the New year but the present I'll
consider the topper would be a usable Wicket 2.0 release, be it beta or RC
:-). Do you think I'm aski
Maybe enough caffeine to keep you guys awake for the most part of the year
and do even more magic with Wicket:-). I don't care if in result someone
somewhere currently developing Wicketry(I won't mention names) would become
so scared because he would loose some ego, which currently has been
magnif
depends on what you are getting us :)
-igor
On 12/14/06, Francis Amanfo <[EMAIL PROTECTED]> wrote:
Hi Wicket devs,
I'm expecting great presents for the New year but the present I'll
consider the topper would be a usable Wicket 2.0 release, be it beta or RC
:-). Do you think I'm asking too mu
Hello wicket-users,
I have now added all the sources for wicket assistant to the
wicket-stuff project. Feel free to help out getting it better.
I suggest that we take the development related discussions to the
wicket-stuff developer list.
Its located under "wicket-idea-plugin".
Hi Wicket devs,
I'm expecting great presents for the New year but the present I'll consider
the topper would be a usable Wicket 2.0 release, be it beta or RC :-). Do
you think I'm asking too much?
Regards,
Francis
--
Beware of bugs in the above code;
I have only proved it correct, not tried it.
A few months ago I wrote to the Wicket user list explaining that I was
investigating view frameworks for a large enterprise project. This is a
follow up to that post explaining why I recommended Wicket. It may be useful
for other people who are going through the same decision process.
First a bit
Exactly, that's the way to go, and that's why onDisabled is in there!
Eelco
On 12/14/06, Matej Knopp <[EMAIL PROTECTED]> wrote:
> I'd rather override isEnabled and onDisabled, e.g.
>
> new TextField() {
> boolean isEnabled() {
> return isTextFieldReadOnly;
> }
>
Many of us struggle with this decision every day, but it never gets any easier
to answer.
"This new switch is designed for seamless compatibility between the new
BladeSystem c-Class and current Cisco environments - a requirement that's
paramount for many of our joint customers. They will also d
see https://issues.apache.org/jira/browse/WICKET-168
-igor
On 12/14/06, Roman Mandeleil <[EMAIL PROTECTED]> wrote:
Ohh yeah it can improve the user expirience
Nino Wael wrote:
>
> Hmmm, should we change it so that trying to use an component that had no
> OutputMarkupId via AJAX would give
I'd rather override isEnabled and onDisabled, e.g.
new TextField() {
boolean isEnabled() {
return isTextFieldReadOnly;
}
void onDisabled(final ComponentTag tag) {
tag.put("readonly", "readonly");
}
}
-Matej
Martijn Dashorst wrote:
>
Hi,
I have a not bookmarkable page (page with a form), when user clicks a link
("submit"), the model data are cleared and confirmation page is displayed.
Now, when the user pressed "Back" in browser, the page renders again, but
because the model changed, it throws.
I want to be able to detect, whe
What doesn't work?
What is exactly the problem
this one works fine in my IE7:
http://www.wicket-library.com/wicket-examples/ajax?wicket:bookmarkablePage=:wicket.examples.ajax.builtin.AutoCompletePage
johan
On 12/14/06, ketan gote <[EMAIL PROTECTED]> wrote:
friends
we are using AutoComple
friends
we are using AutoCompleteTextField ,
which works fine on mozila firefox,
but problem it is not working on IE.
wating for reply
--
Regards
Ketan D.Gote
-
Take Surveys. Earn Cash. Influence the Future of IT
AttributeModifier readonly = new AttributeModifier("readonly", true,
"readonly");
readonly.setEnabled(isTextFIeldReadOnly);
textfield.add(readonly);
Martijn
On 12/14/06, Carfield Yim <[EMAIL PROTECTED]> wrote:
> For Wicket 1.3, look like this is not working, once I add
> [readonly=""] at the mark
if you add it yourself in the markup then yes wicket will not remove it.
the same goes for enabled/disabled.
readonly only works for text components if i am not mistaken so doing at
component or formcomponent
level is a waste if you ask me.
what is wrong with an attribute modifier doing it? (and
I am using AjaxSelfUpdatingTimerBehavior on some ListView and it work
perfectly,
but in some cases when I am in onPostProcessTarget I want to cancel the
current update what is the right
way to do that ?
--
View this message in context:
http://www.nabble.com/AjaxSelfUpdatingTimerBehavior.on
Ohh yeah it can improve the user expirience
Nino Wael wrote:
>
> Hmmm, should we change it so that trying to use an component that had no
> OutputMarkupId via AJAX would give an PleaseSetOutputMarKUPIDTRUE
> exception? I've stumpled over this also and a couple of other users has
> aswell..
>
Hmmm, should we change it so that trying to use an component that had no
OutputMarkupId via AJAX would give an PleaseSetOutputMarKUPIDTRUE exception?
I've stumpled over this also and a couple of other users has aswell..
Regards Nino
_
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTE
41 matches
Mail list logo