Re: setOutputMarkupId and Ajax
No, I understand. An eclipse plugin could solve a lot of this issues. An Wicket view that could warn, etc for all things that could go wrong. I understand now why the programmer needs to set the output and not the framework -- View this message in context: http://www.nabble.com/setOutputMarkupId-and-Ajax-tp19802839p19822392.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: setOutputMarkupId and Ajax
Why can't all components always output that id? Or can't it be a global option to turn it on/off for all components? Is there some situation where you do not want that id? /Anders Igor Vaynberg wrote: like which ones? -igor On Fri, Oct 3, 2008 at 12:44 PM, Rob Sonke [EMAIL PROTECTED] wrote: I understand that but why not adding it by default to the constructor of all ajax components? Rob Igor Vaynberg wrote: wicket only knows that the component needs it when you add it to the ajax request target. by the time you add it to the ART the component has already been rendered into the browser during the previous request, and so its too late at this point - all we can do is warn you. -igor On Fri, Oct 3, 2008 at 11:01 AM, Mathias P.W Nilsson [EMAIL PROTECTED] wrote: Hi! I don't know if this has already been answered but here it goes. When use Ajax with wicket you have to set the the component to output it's markup id or else wicket framework complains about not having it set. Now Why isn't the components markup set automatically when wicket knows about it? Why not skip this, for ajax anyway. If you want to do some other javascript the output it but otherwise wicket could take care of it or maybe I'm missing something. // Mathias -- View this message in context: http://www.nabble.com/setOutputMarkupId-and-Ajax-tp19802839p19802839.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: setOutputMarkupId and Ajax
it significantly increases the size of markup. it will also override any id put in html by the designer for styling. just not a very good global setting. -igor On Sat, Oct 4, 2008 at 8:38 AM, Anders Peterson [EMAIL PROTECTED] wrote: Why can't all components always output that id? Or can't it be a global option to turn it on/off for all components? Is there some situation where you do not want that id? /Anders Igor Vaynberg wrote: like which ones? -igor On Fri, Oct 3, 2008 at 12:44 PM, Rob Sonke [EMAIL PROTECTED] wrote: I understand that but why not adding it by default to the constructor of all ajax components? Rob Igor Vaynberg wrote: wicket only knows that the component needs it when you add it to the ajax request target. by the time you add it to the ART the component has already been rendered into the browser during the previous request, and so its too late at this point - all we can do is warn you. -igor On Fri, Oct 3, 2008 at 11:01 AM, Mathias P.W Nilsson [EMAIL PROTECTED] wrote: Hi! I don't know if this has already been answered but here it goes. When use Ajax with wicket you have to set the the component to output it's markup id or else wicket framework complains about not having it set. Now Why isn't the components markup set automatically when wicket knows about it? Why not skip this, for ajax anyway. If you want to do some other javascript the output it but otherwise wicket could take care of it or maybe I'm missing something. // Mathias -- View this message in context: http://www.nabble.com/setOutputMarkupId-and-Ajax-tp19802839p19802839.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: setOutputMarkupId and Ajax
wicket only knows that the component needs it when you add it to the ajax request target. by the time you add it to the ART the component has already been rendered into the browser during the previous request, and so its too late at this point - all we can do is warn you. -igor On Fri, Oct 3, 2008 at 11:01 AM, Mathias P.W Nilsson [EMAIL PROTECTED] wrote: Hi! I don't know if this has already been answered but here it goes. When use Ajax with wicket you have to set the the component to output it's markup id or else wicket framework complains about not having it set. Now Why isn't the components markup set automatically when wicket knows about it? Why not skip this, for ajax anyway. If you want to do some other javascript the output it but otherwise wicket could take care of it or maybe I'm missing something. // Mathias -- View this message in context: http://www.nabble.com/setOutputMarkupId-and-Ajax-tp19802839p19802839.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: setOutputMarkupId and Ajax
I understand that but why not adding it by default to the constructor of all ajax components? Rob Igor Vaynberg wrote: wicket only knows that the component needs it when you add it to the ajax request target. by the time you add it to the ART the component has already been rendered into the browser during the previous request, and so its too late at this point - all we can do is warn you. -igor On Fri, Oct 3, 2008 at 11:01 AM, Mathias P.W Nilsson [EMAIL PROTECTED] wrote: Hi! I don't know if this has already been answered but here it goes. When use Ajax with wicket you have to set the the component to output it's markup id or else wicket framework complains about not having it set. Now Why isn't the components markup set automatically when wicket knows about it? Why not skip this, for ajax anyway. If you want to do some other javascript the output it but otherwise wicket could take care of it or maybe I'm missing something. // Mathias -- View this message in context: http://www.nabble.com/setOutputMarkupId-and-Ajax-tp19802839p19802839.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: setOutputMarkupId and Ajax
like which ones? -igor On Fri, Oct 3, 2008 at 12:44 PM, Rob Sonke [EMAIL PROTECTED] wrote: I understand that but why not adding it by default to the constructor of all ajax components? Rob Igor Vaynberg wrote: wicket only knows that the component needs it when you add it to the ajax request target. by the time you add it to the ART the component has already been rendered into the browser during the previous request, and so its too late at this point - all we can do is warn you. -igor On Fri, Oct 3, 2008 at 11:01 AM, Mathias P.W Nilsson [EMAIL PROTECTED] wrote: Hi! I don't know if this has already been answered but here it goes. When use Ajax with wicket you have to set the the component to output it's markup id or else wicket framework complains about not having it set. Now Why isn't the components markup set automatically when wicket knows about it? Why not skip this, for ajax anyway. If you want to do some other javascript the output it but otherwise wicket could take care of it or maybe I'm missing something. // Mathias -- View this message in context: http://www.nabble.com/setOutputMarkupId-and-Ajax-tp19802839p19802839.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: setOutputMarkupId and Ajax
Oh stupid, you're right. Only the targets needs the setOutputMarkupId true... Igor Vaynberg wrote: like which ones? -igor On Fri, Oct 3, 2008 at 12:44 PM, Rob Sonke [EMAIL PROTECTED] wrote: I understand that but why not adding it by default to the constructor of all ajax components? Rob Igor Vaynberg wrote: wicket only knows that the component needs it when you add it to the ajax request target. by the time you add it to the ART the component has already been rendered into the browser during the previous request, and so its too late at this point - all we can do is warn you. -igor On Fri, Oct 3, 2008 at 11:01 AM, Mathias P.W Nilsson [EMAIL PROTECTED] wrote: Hi! I don't know if this has already been answered but here it goes. When use Ajax with wicket you have to set the the component to output it's markup id or else wicket framework complains about not having it set. Now Why isn't the components markup set automatically when wicket knows about it? Why not skip this, for ajax anyway. If you want to do some other javascript the output it but otherwise wicket could take care of it or maybe I'm missing something. // Mathias -- View this message in context: http://www.nabble.com/setOutputMarkupId-and-Ajax-tp19802839p19802839.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
