Re: modal window before submitting ajax-less form

2012-10-22 Thread lukuperman
We are using 1.4.15 for now. Lucas Kuperman -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/modal-window-before-submitting-ajax-less-form-tp4653108p4653196.html Sent from the Users forum mailing list archive at Nabble.com.

Re: modal window before submitting ajax-less form

2012-10-22 Thread lukuperman
Thanks Eduardo! I managed to get the modal shown, following your hint. But taking a closer look, I realize I have new challenges to solve: - currently (and I believe I saw it in wicket 6 also) the getWindowOpenJavascript() script generates a new div element in the DOM, with a form inside, when it

Re: modal window before submitting ajax-less form

2012-10-22 Thread lukuperman
Trying client-side now. In the meantime, for clarity: I need a form with checkboxes and a dropdown be submitted. The sequence should be: 1) select desired checkboxes in the page, 2) click a button and show a modal window with the dropdown, 3) select the option from the dropdown, 4) click an

modal window before submitting ajax-less form

2012-10-19 Thread lukuperman
Hi. I need guidance on how to achieve the following: there is a page in my application that has a StatelessForm with several Checks. The checks allow to select rows in a table to be deleted when the form is submitted. Now the customer had requested to have another button that when clicked, a modal

Re: modal window before submitting ajax-less form

2012-10-19 Thread lukuperman
Thanks Sven, I'll have that in mind. Do you think there are other options? It sounds to me I would not be exploiting the framework too much in that case (I would have to take care of the hiding, modal-like appearance, etc?). Thanks Lucas Kuperman -- View this message in context:

Re: modal window before submitting ajax-less form

2012-10-19 Thread lukuperman
Makes sense. In that case, Sven, how can I have a modal window rendered before hand so I can hide/show as needed, something like an ajax-less modal? I wouldn't like to duplicate the effort of rendering a modal window myself. Any idea? Lucas -- View this message in context:

Re: modal window before submitting ajax-less form

2012-10-19 Thread lukuperman
Thanks Eduardo! It looks like what I need!! But when trying to go step by step, trying the OpenOnLoadModalWindow as-is, I get the following exception: ERROR [1534679929@qtp-1426937101-4] (RequestCycle.java:1529) - Error creating page for modal dialog. org.apache.wicket.WicketRuntimeException:

Re: performance on nested dataviews

2012-10-14 Thread lukuperman
Martin, I've implemented my own webmarkupcontainer object and I write the html in the onComponentTagBody() method. It works super fast. Now my question is, how can I reuse other components I created (labels, etc) from within this method? I'm still not familiar with the order of calls, sorry. Any

refresh ajaxlazyloadpanel

2012-10-12 Thread lukuperman
Hello, I'm using an ajaxlazyloadpanel and I already read that instantiating a new instance is the way to 'refresh' the panel. But my question is where do you think is the most appropriate/elegant way to do so when I have various different places in my page that reloads the panel's parent form,

Re: Centralizing ajax inline javascript

2012-10-08 Thread lukuperman
Sebastien, Ernesto, I had to repost because after centralizing the ajax behavior I saw the browser does not send CheckBox ajax requests in parallel any more. Is this because we centralized the behavior? Lucas Kuperman -- View this message in context:

performance on nested dataviews

2012-10-04 Thread lukuperman
Hi, in the project I work on there is a matrix that grows in both dimensions. Currently it is implemented as 2 nested DataViews. I'm seeing the inner-most dataview's onBeforeRender() takes 2-3 seconds to process 200 checkboxes, which if I combine it with a 15 outer-most dataview gives me the

Re: performance on nested dataviews

2012-10-04 Thread lukuperman
Hi Martin, yes I did some profiling focusing on my classes. I'll post the results shortly. In the meantime, is there any preference between 2 nested dataviews vs datatable when table has dynamic number of columns, considering performance as driver? Lucas Kuperman -- View this message in

Re: Centralizing ajax inline javascript

2012-09-30 Thread lukuperman
Hi Sebastien, I applied your last approach and I think it would work. It is working but step 4 Get the component back is not finding the checkbox because of (what I believe) an incomplete path. It doesn't sound complicated, I'll investigate. However I am starting to understand things more due to

Re: Centralizing ajax inline javascript

2012-09-30 Thread lukuperman
Hi Ernesto. We seem to be in the same page now. Sebastien's approach is also about a single behavior, with the small difference of adding the CheckBoxes onclick event in the server side (I did it in the onComponentTag method instead of relying on attributemodifiers because of performance) rather

Re: Centralizing ajax inline javascript

2012-09-30 Thread lukuperman
Hi Sebastien, just to understand, if I don't need an AjaxCheckBox anymore then I shouldn't extend from it right? I'm in troubles, cause if I dont extend, I have no behavior to call back, and if I do extend then the original problem arise about the inline onclick script being attached to each

Re: Centralizing ajax inline javascript

2012-09-29 Thread lukuperman
Thanks Ernesto and Sebastien! I'm going to apply your suggestions during the weekend and keep you posted. In the meantime, Ernesto, I want to clarify that I don't want to pass any additional parameter to the server. I just want the proper onUpdate() method of the proper AjaxCheckBox instance be

Centralizing ajax inline javascript

2012-09-28 Thread lukuperman
Hello all, I am working on an application that was built with Wicket 1.4.15. It has to show a table with an AjaxCheckBox on each cell. Most of the final html size is because of the inline ajax behavior on each cb (ie 20Mb for a 200x200 table). Leaving aside the fact of rendering big tables (which

Re: Centralizing ajax inline javascript

2012-09-28 Thread lukuperman
Hi Vineet. I knew someone would ask. Lots of components right? Yes, I agree. The component tree is giving us a hard time with performance in general (around 5 minutes to process) and stack overflows when serializing, etc. But focusing back to my original question, unfortunately the business

Re: ModalWindow accessibility - DIV placeholder not used

2012-03-26 Thread lukuperman
Hi Martin, I took a look at the post you mentioned, but in that patch the div node is still being appended to the document.body node, resulting in the behavior i'm seeing. However I have to admit that appending the new div node to the placeholder is just a nice to have. A more appropriate solution

Re: ModalWindow accessibility - DIV placeholder not used

2012-03-26 Thread lukuperman
Hi Martin, ticket 4472 created (https://issues.apache.org/jira/browse/WICKET-4472) But since I'm new to OSS contributions, I didn't attach a patch. Due to the low complexity of the change I don't think my patch is a blocker for you? I'll start setting up my env, to be ready to deliver patches in

Re: ModalWindow accessibility - DIV placeholder not used

2012-03-26 Thread lukuperman
Done. Made the requested updates to the ticket. Lucas PD: do you think i should create another ticket for the related post I mentioned above? -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/ModalWindow-accessibility-DIV-placeholder-not-used-tp4501891p4506115.html

adding associated text to the close anchor on modal windows

2012-03-25 Thread lukuperman
Hello, I work on a team that supports a web application implemented with Wicket, and because of accessibility compliance I'm addressing some DQA findings. It would be nice to have the close anchor of modal windows (top right corner) having an associated text, for assistive technologies. This can

ModalWindow accessibility - DIV placeholder not used

2012-03-24 Thread lukuperman
Hello, I inherited an application that uses Apache Wicket 1.4.15. Everything works fine, but because of accessibility standards I have to address some findings we received from DQA team, which includes missing wai-aria attributes around to the modal windows. However I noticed the DIV placeholder I