Re: Issue with AjaxLinks in ListView
Anyone??? Thanks Kuga -- View this message in context: http://www.nabble.com/Issue-with-AjaxLinks-in-ListView-tp24765587p24775312.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Bug in AbstractOptions of Palette?
Done. *WICKET-2407 https://issues.apache.org/jira/browse/WICKET-2407* Eyal Golan egola...@gmail.com Visit: http://jvdrums.sourceforge.net/ LinkedIn: http://www.linkedin.com/in/egolan74 P Save a tree. Please don't print this e-mail unless it's really necessary On Thu, Jul 30, 2009 at 7:19 PM, Igor Vaynberg igor.vaynb...@gmail.comwrote: open a jira issue -igor On Thu, Jul 30, 2009 at 1:39 AM, Eyal Golanegola...@gmail.com wrote: Hello, We encountered a small problem in our Palette. Some of the values that were supposed to be in the choices (available and/or selected) had the '' and '' . Because of that the options weren't rendererd correctly. Looking at AbstractAction#onComponentTagBody I saw that it takes the value as it is and put it in the html: String value = getConverter(displayClass).convertToString(displayValue, getLocale()); where displayValue is Object displayValue = renderer.getDisplayValue(choice); In my code I overridden the getDisplayValue and getDisplayId of the renderer: IChoiceRenderer choiceRenderer = new ChoiceRenderer(getFieldName, getFieldName) { private static final long serialVersionUID = 1L; @Override public Object getDisplayValue(Object object) { final String result = (String) super.getDisplayValue(object); return Strings.escapeMarkup(result, true, true).toString(); } @Override public String getIdValue(Object object, int index) { final String result = (String) super.getIdValue(object, index); return Strings.escapeMarkup(result, true, true).toString(); } }; As you can see I took the result and changed it with the Strings utility. Do you think it's a bug in Wicket and I should open a Jira issue? Or is the Palette works as wanted and my change is normal? BTW, we use Wicket 1.3.6 Thanks Eyal Golan egola...@gmail.com Visit: http://jvdrums.sourceforge.net/ LinkedIn: http://www.linkedin.com/in/egolan74 P Save a tree. Please don't print this e-mail unless it's really necessary - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Issue with AjaxLinks in ListView
It's hard to say what's going wrong without seeing code for entire page. -Matej On Sun, Aug 2, 2009 at 8:29 AM, Kugakvisagam...@infoblox.com wrote: Anyone??? Thanks Kuga -- View this message in context: http://www.nabble.com/Issue-with-AjaxLinks-in-ListView-tp24765587p24775312.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Problem with Required component message
Hi! I have a page with some required fields among which there is one specific field I want to return a specific required validation error message, if value not given. I have tried to put componentId.Required=Unique error message into Application.properties but it does not work. Instead Wicket always returns the standard Required error. Debugging deeper into the problem shows that Wicket constructs a dot-notation component path of the requied component: page.panel.form.nested_panel.listview.index.componentId.Required and tries to look for a property with such name. If not found, it next tries to look for Required alone and if it is found, it returns that (if Required was not found, it would continue dropping one prefix at a time until it would reach the assumed componentId.Required). This code is in: ComponentStringResourceLoader.loadStringResource(final Component component, final String key) Is there a flaw in the logic or am I doing something wrong here? ** Martin - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: launching a modal page from a Panel
Define your modal window as a class variable. class MyWebPage extends WebPage{ private ModalWindow myWindow; } in the constructor myWindow = new ModalWindow( myWindow ); myWindow.setPageMapName(myWindow-1); myWindow.setCookieName(myWindow-1); myWindow.setPageCreator(new ModalWindow.PageCreator() { public org.apache.wicket.Page createPage() { return new MyWindow(); } }); myWindow.setWindowClosedCallback(new ModalWindow.WindowClosedCallback() { public void onClose(AjaxRequestTarget target) { } }); myWindow.setCloseButtonCallback(new ModalWindow.CloseButtonCallback() { public boolean onCloseButtonClicked(AjaxRequestTarget target) { return true; } }); add( myWindow ); Now, all you have to do is to call myWindow.show() in your ajaxlink. -- View this message in context: http://www.nabble.com/launching-a-modal-page-from-a-Panel-tp24760576p24776275.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: launching a modal page from a Panel
Of course. If it is a panel then you'll do the same thing. class MyPanel extends Panel{ class variable } -- View this message in context: http://www.nabble.com/launching-a-modal-page-from-a-Panel-tp24760576p24776281.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Problem with Required component message
Martin Makundi schrieb: Debugging deeper into the problem shows that Wicket constructs a dot-notation component path of the requied component: page.panel.form.nested_panel.listview.index.componentId.Required and tries to look for a property with such name. don´t know about the exact state of it (did not yet use 1.4), but could this be connected to: https://issues.apache.org/jira/browse/WICKET-2350 ? cu uwe - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
RE: Problem with Required component message
Martin, I did this by creating a properties file MyPanel.properties and then setting creditCardForm.ccNumber.Required=Please enter your credit card number. Did you try setting form.componentId.Required? Or even panel.form.componentId.Required Russ Date: Sun, 2 Aug 2009 12:19:40 +0300 Subject: Problem with Required component message From: martin.maku...@koodaripalvelut.com To: users@wicket.apache.org Hi! I have a page with some required fields among which there is one specific field I want to return a specific required validation error message, if value not given. I have tried to put componentId.Required=Unique error message into Application.properties but it does not work. Instead Wicket always returns the standard Required error. Debugging deeper into the problem shows that Wicket constructs a dot-notation component path of the requied component: page.panel.form.nested_panel.listview.index.componentId.Required and tries to look for a property with such name. If not found, it next tries to look for Required alone and if it is found, it returns that (if Required was not found, it would continue dropping one prefix at a time until it would reach the assumed componentId.Required). This code is in: ComponentStringResourceLoader.loadStringResource(final Component component, final String key) Is there a flaw in the logic or am I doing something wrong here? ** Martin - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org _ Get back to school stuff for them and cashback for you. http://www.bing.com/cashback?form=MSHYCBpubl=WLHMTAGcrea=TEXT_MSHYCB_BackToSchool_Cashback_BTSCashback_1x1
Re: Issue with AjaxLinks in ListView
On Sat, Aug 01, 2009 at 09:19:05AM -0700, Kuga wrote: I have not tried replacing to RepeatingView. Will it make a difference? I have no idea. Why don't you try it? jk - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Problem with Required component message
I did this by creating a properties file MyPanel.properties and then setting creditCardForm.ccNumber.Required=Please enter your credit card number. Did you try setting form.componentId.Required? Or even panel.form.componentId.Required The problem is that my field is on a ListView. I cannot PREDICT the INDEX!!! It will be: form.listview.*random_index*.componentId.Required In my opinnion there is a bug in the stringResource-finder. It should FIRST scan down the path before trying the Key=Required alone. Now it tries the full path first, then Key=Required and if that is not found, then it tries the next path depth. https://issues.apache.org/jira/browse/WICKET-2350 That's something different. I had a look at the HEAD Wicket svn, this part of the code still remains: // First, try the fully qualified resource name relative to the // component on the path from page down. ... proper code here but FULLY QUALIFIED RESOURCE Then right after that: // If not found, than check if a property with the 'key' provided by // the user can be found. if ((string == null) old) { string = loadStringResource(clazz, key, locale, style); } It looks for the key...Required. I.e., it will override with the default one. In my opinnion the above block if not found... should be right after the LOOP for (int i = searchStack.size() - 1; (i = 0) (string == null); i--) and NOT WITHIN the loop as it is now. ** Martin Russ Date: Sun, 2 Aug 2009 12:19:40 +0300 Subject: Problem with Required component message From: martin.maku...@koodaripalvelut.com To: users@wicket.apache.org Hi! I have a page with some required fields among which there is one specific field I want to return a specific required validation error message, if value not given. I have tried to put componentId.Required=Unique error message into Application.properties but it does not work. Instead Wicket always returns the standard Required error. Debugging deeper into the problem shows that Wicket constructs a dot-notation component path of the requied component: page.panel.form.nested_panel.listview.index.componentId.Required and tries to look for a property with such name. If not found, it next tries to look for Required alone and if it is found, it returns that (if Required was not found, it would continue dropping one prefix at a time until it would reach the assumed componentId.Required). This code is in: ComponentStringResourceLoader.loadStringResource(final Component component, final String key) Is there a flaw in the logic or am I doing something wrong here? ** Martin - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org _ Get back to school stuff for them and cashback for you. http://www.bing.com/cashback?form=MSHYCBpubl=WLHMTAGcrea=TEXT_MSHYCB_BackToSchool_Cashback_BTSCashback_1x1 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Stateless login form?
Martin, I am not sure what you mean. On the site you are referring, the login page is always visible under /login. Regards, Erik. Martin Makundi wrote: If I understood correctly, you might find this interesting: http://day-to-day-stuff.blogspot.com/2008/10/wicket-extreme-consistent-urls.html Does appear to make stateless-looking urls AFTER you CLICK/REDIRECT (looking at the example page referred on the site). Not BEFORE you CLICK... - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Stateless login form?
Login page is visible, but the form action=/?wicket:interface=:0:1 which is stateful. If my session dies I will definitely get an error. Try clicking this link with a new browser that does not have a session on the site: http://www.tipspot.com/?wicket:interface=:0:1 This is what you would get if your browser loaded the page from cache (or if you let it wait until the session invalidates). Does not look professional and it is totaly unnecessary, in my opinnion. It should be possible to handle forms on virgin (=no state bound yet) invocations too. ** Martin 2009/8/2 Erik van Oosten e.vanoos...@grons.nl: Martin, I am not sure what you mean. On the site you are referring, the login page is always visible under /login. Regards, Erik. Martin Makundi wrote: If I understood correctly, you might find this interesting: http://day-to-day-stuff.blogspot.com/2008/10/wicket-extreme-consistent-urls.html Does appear to make stateless-looking urls AFTER you CLICK/REDIRECT (looking at the example page referred on the site). Not BEFORE you CLICK... - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: reloading DropDownChoice choices
Well, I found some detachable model documentation and figured it out. LDM::detach() will cause a getObject() call to load(). Putting detach early in my Form::submit() was sufficient for this example. Another wrinkle was that I also had a Button with the same issue and putting detach() in Button::onSubmit() was not work. Changing the Button to a Link and using onClick() did, though. -troy On Thu, Jul 30, 2009 at 7:29 PM, Troy Cauble troycau...@gmail.com wrote: Here's a minimal example of my problem. Again, the LDM::getObject() call AFTER the onSubmit() call that changes the data does not result in a LDM::load(). There's a load() before the onSubmit(), but that's too early. Anyone? What am I missing? Thanks, -troy [jetty] DDC choices LDM: getObject [jetty] DDC choices LDM: load(reading choices) [jetty] DDC choices LDM: onAttach [jetty] Form onSubmit [jetty] DDC choices LDM: getObject [jetty] DDC choices LDM: onDetach [jetty] ?xml version=1.0 encoding=UTF-8? html head/head body Pressing the button adds an entry to the drop down list, but you can't see it without reloading the page. br/ What am I missing? div style=position:relative; left:10px; br/ form wicket:id=form style=position:relative; left:10px; select wicket:id=ddc/ input type=submit value=add an entry/ /form /div /body /html package dummy; import java.util.*; import org.apache.wicket.PageParameters; import org.apache.wicket.markup.html.WebPage; import org.apache.wicket.markup.html.form.*; import org.apache.wicket.model.*; public class Dummy extends WebPage { private static final long serialVersionUID = 1L; private ArrayListStringchoices = new ArrayListString(); private Integeritem = new Integer(1); public Dummy(final PageParameters parameters) { super(parameters); choices.add(item.toString()); IModel choicesModel = new LoadableDetachableModel() { private static final long serialVersionUID = 1L; @Override protected void onAttach() { System.out.println(DDC choices LDM: onAttach); super.onAttach(); } @Override protected void onDetach() { System.out.println(DDC choices LDM: onDetach\n); super.onDetach(); } @Override public Object getObject() { System.out.println(DDC choices LDM: getObject); return super.getObject(); } @Override protected Object load() { System.out.println(DDC choices LDM: load(reading choices)); // Note the clone() -- // to simulate a hibernate pull return choices.clone(); } }; final DropDownChoice ddc = new DropDownChoice(ddc, new Model(), choicesModel); Form form = new Form(form) { private static final long serialVersionUID = 1L; @Override protected void onSubmit() { System.err.printf(Form onSubmit\n); ddc.setModelObject(null); choices.add((++item).toString()); } }; add(form); form.add(ddc); } }
Wicket for non Web/AJAX developers?
Are there any resources for Wicket that a non web or ajax developer should be aware of? Much of the class design documentation assume knowledge of these things, especially when you get down to stuff like AjaxFormComponentUpdatingBehavior. WTF? I know that this was a design choice and you can't teach everybody everything. I'm just asking if this info exists somewhere. And OTOH, Wicket is trying to hide the web model. For example, given that I can make a Link look like a button, when should I use a Link vs a Button? I have no idea. Thanks, -troy
Issue WICKET-2409
have you read thishttp://www.codesmell.org/blog/2009/08/pitfall-on-implementing-generic-methods/? Eyal Golan egola...@gmail.com Visit: http://jvdrums.sourceforge.net/ LinkedIn: http://www.linkedin.com/in/egolan74 P Save a tree. Please don't print this e-mail unless it's really necessary
Re: Wicket for non Web/AJAX developers?
For example, given that I can make a Link look like a button, when should I use a Link vs a Button? I have no idea. Duh... there is/was a bug on BUTTON at least on firefox (might have affected only non-ajax buttons). You cannot distinguish which button was pressed. So it is safer to use LINk when you need to style the link freely. What I am trying to say is: just try it out and bang your head to the tree. Wicket is so customizable that it is very hard to make generic examples - each project might need to tweak things differently to its needs. ** Martin Thanks, -troy - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket for non Web/AJAX developers?
On Sun, Aug 2, 2009 at 10:40 AM, Troy Caubletroycau...@gmail.com wrote: Much of the class design documentation assume knowledge of these things, especially when you get down to stuff like AjaxFormComponentUpdatingBehavior. WTF? what part of that name or javadoc is hard for you to understand? I know that this was a design choice and you can't teach everybody everything. I'm just asking if this info exists somewhere. not really sure. And OTOH, Wicket is trying to hide the web model. totally and completely wrong. wicket abstracts away the nastiest part of writng webapps - the stateless nature of http, not the fact that you are writing a web app. For example, given that I can make a Link look like a button, when should I use a Link vs a Button? I have no idea. it solely depends on your UI requirements (what markup you want to use). we make it easy to work with either an anchor tag or a button/input type=submit tag. -igor Thanks, -troy - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket for non Web/AJAX developers?
ps, you might want to look into wingS or echo frameworks. i think their level of abstraction is higher and might be what you are looking for. of course, the higher the level of abstraction the less control you have over the final product, keep that in mind and find a good balance for your needs. -igor On Sun, Aug 2, 2009 at 1:46 PM, Igor Vaynbergigor.vaynb...@gmail.com wrote: On Sun, Aug 2, 2009 at 10:40 AM, Troy Caubletroycau...@gmail.com wrote: Much of the class design documentation assume knowledge of these things, especially when you get down to stuff like AjaxFormComponentUpdatingBehavior. WTF? what part of that name or javadoc is hard for you to understand? I know that this was a design choice and you can't teach everybody everything. I'm just asking if this info exists somewhere. not really sure. And OTOH, Wicket is trying to hide the web model. totally and completely wrong. wicket abstracts away the nastiest part of writng webapps - the stateless nature of http, not the fact that you are writing a web app. For example, given that I can make a Link look like a button, when should I use a Link vs a Button? I have no idea. it solely depends on your UI requirements (what markup you want to use). we make it easy to work with either an anchor tag or a button/input type=submit tag. -igor Thanks, -troy - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Stateless login form?
Jeremy Thomerson already gave you the hint: override isStateless and return true... thus you'll not get a session relative url. Alex. MartinM wrote: Login page is visible, but the form action=/?wicket:interface=:0:1 which is stateful. If my session dies I will definitely get an error. Try clicking this link with a new browser that does not have a session on the site: http://www.tipspot.com/?wicket:interface=:0:1 This is what you would get if your browser loaded the page from cache (or if you let it wait until the session invalidates). Does not look professional and it is totaly unnecessary, in my opinnion. It should be possible to handle forms on virgin (=no state bound yet) invocations too. ** Martin 2009/8/2 Erik van Oosten e.vanoos...@grons.nl: Martin, I am not sure what you mean. On the site you are referring, the login page is always visible under /login. Regards, Erik. Martin Makundi wrote: If I understood correctly, you might find this interesting: http://day-to-day-stuff.blogspot.com/2008/10/wicket-extreme-consistent-urls.html Does appear to make stateless-looking urls AFTER you CLICK/REDIRECT (looking at the example page referred on the site). Not BEFORE you CLICK... - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- View this message in context: http://www.nabble.com/Stateless-login-form--tp24757066p24782234.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket for non Web/AJAX developers?
The similar confusion had a friend of mine who didn't have any experience at all with wicket and indeed, at the first glance, a 33 letters long class seems a bit strange :)... But, you must know that according to wicket coding convensions: - each class implementing IBehavior interface has a 'Behavior' suffix - each ajax related component or behavior has an 'Ajax' prefix Remove those two, and it will become easier to understand... Do you have other suggestions for naming convensions? Alex Objelean LazyBoy wrote: Much of the class design documentation assume knowledge of these things, especially when you get down to stuff like AjaxFormComponentUpdatingBehavior. WTF? -- View this message in context: http://www.nabble.com/Wicket-for-non-Web-AJAX-developers--tp24780111p24782326.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket for non Web/AJAX developers?
On Sun, Aug 2, 2009 at 4:46 PM, Igor Vaynberg igor.vaynb...@gmail.comwrote: On Sun, Aug 2, 2009 at 10:40 AM, Troy Caubletroycau...@gmail.com wrote: Much of the class design documentation assume knowledge of these things, especially when you get down to stuff like AjaxFormComponentUpdatingBehavior. WTF? what part of that name or javadoc is hard for you to understand? I'm saying it's hard for someone without a prior web development background. The javadoc says A behavior that updates ... via ajax, but I only have a vague idea why or when I might need to do that. Also it takes a javascript event string argument that is not explained. (I can google javascript events and guess or I can steal from example code.) Even more to the point, AttributeModifier require you to write javascript and know the likely form of what your modifying. Without googling examples of confirmation dialogs, I could have never guessed that AttributeModifier was the relevant class for that. This is not a criticism of Wicket or the docs. I know the target user is someone who's done traditional webdev first and came looking for something better. I was just curious if there happened to be any articles that filled in the gaps for those of us attempting to skip directly to Wicket. Thanks, -troy
Re: Wicket for non Web/AJAX developers?
I haven't seen any 'special' article of the kind you are looking for. However, I can just say for myself that when I started working with Wicket, all I new was basic HTML. I didn't even know exactly what was CSS. Slowly I became better in that area. Everyday I learned something new about webdev (as yo call it). I even 'stole' many example code. yes i did :) Which I believe is a very good way to learn. I can also tell you that I do feel sometimes the gap of not knowing really good JS and Ajax. For these special occasions we take an outside consultant. I usually look behind his shoulder and learn. or just read the svn difference when I update my project. What I suggest is, read the Wicket wiki, google, check this user list and ask questions (I once asked how to write the JS for closing a window. And was answered really quick.), check the example and if you can, have a phone number of an ajax / js expert for the REALLY complex stuff. Eyal Golan egola...@gmail.com Visit: http://jvdrums.sourceforge.net/ LinkedIn: http://www.linkedin.com/in/egolan74 P Save a tree. Please don't print this e-mail unless it's really necessary On Sun, Aug 2, 2009 at 11:46 PM, Troy Cauble troycau...@gmail.com wrote: On Sun, Aug 2, 2009 at 4:46 PM, Igor Vaynberg igor.vaynb...@gmail.com wrote: On Sun, Aug 2, 2009 at 10:40 AM, Troy Caubletroycau...@gmail.com wrote: Much of the class design documentation assume knowledge of these things, especially when you get down to stuff like AjaxFormComponentUpdatingBehavior. WTF? what part of that name or javadoc is hard for you to understand? I'm saying it's hard for someone without a prior web development background. The javadoc says A behavior that updates ... via ajax, but I only have a vague idea why or when I might need to do that. Also it takes a javascript event string argument that is not explained. (I can google javascript events and guess or I can steal from example code.) Even more to the point, AttributeModifier require you to write javascript and know the likely form of what your modifying. Without googling examples of confirmation dialogs, I could have never guessed that AttributeModifier was the relevant class for that. This is not a criticism of Wicket or the docs. I know the target user is someone who's done traditional webdev first and came looking for something better. I was just curious if there happened to be any articles that filled in the gaps for those of us attempting to skip directly to Wicket. Thanks, -troy
Re: Wicket for non Web/AJAX developers?
Hi, I think the Wicket in Action is a good book to start. It even has a chapter called Ajax explained :-) I don't know if it explains how the web app works as such but it goes through the entire development process of a Wicket web application so you should be able to get the idea behind. And it's less than 400 pages :-) cheers, Marcin -- View this message in context: http://www.nabble.com/Wicket-for-non-Web-AJAX-developers--tp24780111p24782743.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket for non Web/AJAX developers?
On Sun, Aug 2, 2009 at 2:46 PM, Troy Caubletroycau...@gmail.com wrote: On Sun, Aug 2, 2009 at 4:46 PM, Igor Vaynberg igor.vaynb...@gmail.comwrote: On Sun, Aug 2, 2009 at 10:40 AM, Troy Caubletroycau...@gmail.com wrote: Much of the class design documentation assume knowledge of these things, especially when you get down to stuff like AjaxFormComponentUpdatingBehavior. WTF? what part of that name or javadoc is hard for you to understand? I'm saying it's hard for someone without a prior web development background. without prior knowledge of java it would be hard to learn hibernate. without prior knowledge of sql it would be hard to learn plsql. thats just how things work, you need to know the context of your problem domain. The javadoc says A behavior that updates ... via ajax, but I only have a vague idea why or when I might need to do that. http://en.wikipedia.org/wiki/Ajax_%28programming%29 Also it takes a javascript event string argument that is not explained. (I can google javascript events and guess or I can steal from example code.) http://en.wikipedia.org/wiki/DOM_events both of those links are a google search away more to the point, why are you using this class as an example? you say you dont know when you need to use it...obviously if you dont know what it does then you dont need to use it. you are looking at a tool and complaining that you dont understand the problem it solves - thats a little backwards. Even more to the point, AttributeModifier require you to write javascript and know the likely form of what your modifying. Without googling examples of confirmation dialogs, I could have never guessed that AttributeModifier was the relevant class for that. sorry? All AttributeModifier does is Modify a markup Attribute. not a bad name. of course that attribute value can contain javascript if you wish, but not a requirement by any means. -igor This is not a criticism of Wicket or the docs. I know the target user is someone who's done traditional webdev first and came looking for something better. I was just curious if there happened to be any articles that filled in the gaps for those of us attempting to skip directly to Wicket. Thanks, -troy - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket for non Web/AJAX developers?
I guess the name LazyBoy says it all. -- View this message in context: http://www.nabble.com/Wicket-for-non-Web-AJAX-developers--tp24780111p24783233.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket for non Web/AJAX developers?
Hi, I'm sorry to see a couple of somewhat uncourteous responses in this thread. The guy is just asking a question that might well benefit others who are interested in Wicket too. Coming from e.g. Swing, there is indeed quite a lot of stuff to grok, and things can seem overwhelming, so why not just try and help each other out? That said, I would agree that becoming familiar with some of the basics of web related work isn't going to hurt, especially given the ubiquity of the web as a UI platform these days. If you want to do without that, things like Flex, or perhaps even WebOnSwing and POJO Application Server come to mind. Cheers, Erik On Mon, Aug 3, 2009 at 1:33 AM, shetcsh...@bellsouth.net wrote: I guess the name LazyBoy says it all. -- View this message in context: http://www.nabble.com/Wicket-for-non-Web-AJAX-developers--tp24780111p24783233.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket for non Web/AJAX developers?
whenever i try to be courteous i also usually try to start by including at least one wtf in my question :) -igor On Sun, Aug 2, 2009 at 4:48 PM, Erik Posteriksen...@gmail.com wrote: Hi, I'm sorry to see a couple of somewhat uncourteous responses in this thread. The guy is just asking a question that might well benefit others who are interested in Wicket too. Coming from e.g. Swing, there is indeed quite a lot of stuff to grok, and things can seem overwhelming, so why not just try and help each other out? That said, I would agree that becoming familiar with some of the basics of web related work isn't going to hurt, especially given the ubiquity of the web as a UI platform these days. If you want to do without that, things like Flex, or perhaps even WebOnSwing and POJO Application Server come to mind. Cheers, Erik On Mon, Aug 3, 2009 at 1:33 AM, shetcsh...@bellsouth.net wrote: I guess the name LazyBoy says it all. -- View this message in context: http://www.nabble.com/Wicket-for-non-Web-AJAX-developers--tp24780111p24783233.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket for non Web/AJAX developers?
Ok, sorry, you guys have always been very helpful to me. Maybe we can together with Barak and down a few beers :blush: -- View this message in context: http://www.nabble.com/Wicket-for-non-Web-AJAX-developers--tp24780111p24783661.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Stateless login form?
Jeremy Thomerson already gave you the hint: override isStateless and return true... thus you'll not get a session relative url. Ok. That might work, I actually get: https://localhost/login/wicket:interface/:0:loginForm::IFormSubmitListener::;jsessionid=139rzdeu5rm09 And on a first try, it really does seem to work though it appears stateful (=to an uneducated eye). Thank you! My next challenge is that sometimes users bookmark authenticated pages and when they return, for some reason Wicket instantiates such pages that require authentication though it should be prevented by specific annotations. Instatiation results in nullpointer exceptions due to lacking login data... ** Martin. Alex. MartinM wrote: Login page is visible, but the form action=/?wicket:interface=:0:1 which is stateful. If my session dies I will definitely get an error. Try clicking this link with a new browser that does not have a session on the site: http://www.tipspot.com/?wicket:interface=:0:1 This is what you would get if your browser loaded the page from cache (or if you let it wait until the session invalidates). Does not look professional and it is totaly unnecessary, in my opinnion. It should be possible to handle forms on virgin (=no state bound yet) invocations too. ** Martin 2009/8/2 Erik van Oosten e.vanoos...@grons.nl: Martin, I am not sure what you mean. On the site you are referring, the login page is always visible under /login. Regards, Erik. Martin Makundi wrote: If I understood correctly, you might find this interesting: http://day-to-day-stuff.blogspot.com/2008/10/wicket-extreme-consistent-urls.html Does appear to make stateless-looking urls AFTER you CLICK/REDIRECT (looking at the example page referred on the site). Not BEFORE you CLICK... - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- View this message in context: http://www.nabble.com/Stateless-login-form--tp24757066p24782234.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
ayax - close button - lightwindow (http://www.stickmanlabs.com/lightwindow/)
Hi all, I've implemented lightwindow widget (from london wicket example) and I need some extra work. I would like to know if any of you have added an ayax call back to the close button. My use case view is to refresh the original page when the lightwindow is closed. thanks in advance. -- Fernando Wermus. www.linkedin.com/in/fernandowermus
Doubt please help me to clear
Hello Friends, Could you please tell me things of Wicket Flex what are the advantages of both. what are the disadvandages.(Flex) Comapre Flex and Wicket Both are used to easy web development. Flex is also has a good UI Development.(I came to know that) -- Thanksregards, Gerald A
Re: Doubt please help me to clear
Hi! Here are some fast points: Flex is client side FAT client. It runs on BROWSER. Wicket runs on SERVER. Flex can do graphics. You must know Flex. Wicket can do graphics. You must know HTML/JavaScript/CSS. Not all people ALLOW Flex in their browsers (minority, these days). In a way, SERVER side application is littlebit safer because FULL data always remains on server. In Flex sometinmes programmer may compromise and send critical data to CLIENT BROWSER. ** Martin 2009/8/3 Gerald Fernando gerald.anto.ferna...@gmail.com: Hello Friends, Could you please tell me things of Wicket Flex what are the advantages of both. what are the disadvandages.(Flex) Comapre Flex and Wicket Both are used to easy web development. Flex is also has a good UI Development.(I came to know that) -- Thanksregards, Gerald A - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org