Re: Large number components and redering time

2010-02-19 Thread Juha Palomäki
If you want to avoid mixing HTML and Java, you could write your component with using a templating engine, such as Velocity or Freemarker. I believe there is wicket-velocity project somewhere that provides for example Panels that can render Velocity templates files. br, Juha On Thu, Feb 18, 2010

Large number components and redering time

2010-02-17 Thread dev
Hi, I have a question on how to address a certain problem that arose in my current project: we have a two-dimensional array with a variable number of rows and columns (not exactly rocket science, I know) that needs to be rendered in an HTML table where each cell is currently represented by a

RE: Large number components and redering time

2010-02-17 Thread Josh Chappelle
Could you use a PageableListView or does that not fall within your business requirements? Josh -Original Message- From: d...@agentlab.de [mailto:d...@agentlab.de] Sent: Wednesday, February 17, 2010 12:08 PM To: users@wicket.apache.org Subject: Large number components and redering time

Re: Large number components and redering time

2010-02-17 Thread Martin Makundi
Hi! Did you jprofile where the time is spent? ** Martin 2010/2/17 d...@agentlab.de: Hi, I have a question on how to address a certain problem that arose in my current project: we have a two-dimensional array with a variable number of rows and columns (not exactly rocket science, I know)

Re: Large number components and redering time

2010-02-17 Thread dev
business requirements? Josh -Original Message- From: d...@agentlab.de [mailto:d...@agentlab.de] Sent: Wednesday, February 17, 2010 12:08 PM To: users@wicket.apache.org Subject: Large number components and redering time Hi, I have a question on how to address a certain problem that arose

Re: Large number components and redering time

2010-02-17 Thread Ilja Pavkovic
: d...@agentlab.de [mailto:d...@agentlab.de] Sent: Wednesday, February 17, 2010 12:08 PM To: users@wicket.apache.org Subject: Large number components and redering time Hi, I have a question on how to address a certain problem that arose in my current project: we have a two

Re: Large number components and redering time

2010-02-17 Thread dev
I set up a WicketTester Testcase and used Eclipse TPTP to look into the app. Over 90% were spent in beforeRender calls... However, since the load that was produced by running the testcase within a monitored environment brought my computer to its knees, I will have to dwell deeper into the problem

Re: Large number components and redering time

2010-02-17 Thread Scott Swank
wrote: Could you use a PageableListView or does that not fall within your business requirements? Josh -Original Message- From: d...@agentlab.de [mailto:d...@agentlab.de] Sent: Wednesday, February 17, 2010 12:08 PM To: users@wicket.apache.org Subject: Large number components

Re: Large number components and redering time

2010-02-17 Thread dev
@wicket.apache.org Subject: Large number components and redering time Hi, I have a question on how to address a certain problem that arose in my current project: we have a two-dimensional array with a variable number of rows and columns (not exactly rocket science, I know) that needs to be rendered

Re: Large number components and redering time

2010-02-17 Thread dev
a PageableListView or does that not fall within your business requirements? Josh -Original Message- From: d...@agentlab.de [mailto:d...@agentlab.de] Sent: Wednesday, February 17, 2010 12:08 PM To: users@wicket.apache.org Subject: Large number components and redering time Hi, I have a question on how

Re: Large number components and redering time

2010-02-17 Thread Igor Vaynberg
i would imagine you would have the same problem even in a local environment such as swing... the solution is quiet simple, instead of using wicket components to model the table and the cell simply use a single component that writes out html for the entire table. -igor On Wed, Feb 17, 2010 at

Re: Large number components and redering time

2010-02-17 Thread Martin Makundi
To: users@wicket.apache.org Subject: Large number components and redering time Hi, I have a question on how to address a certain problem that arose in my current project: we have a two-dimensional array with a variable number of rows and columns (not exactly rocket science, I know

Re: Large number components and redering time

2010-02-17 Thread James Carman
components and redering time Hi, I have a question on how to address a certain problem that arose in my current project: we have a two-dimensional array with a variable number of rows and columns (not exactly rocket science, I know) that needs to be rendered in an HTML table where each cell

Re: Large number components and redering time

2010-02-17 Thread bht
Swing uses a variety of TableCellRenderer on a per table instance basis. What component are you suggesting to use for this behavior in Wicket? Bernard On Wed, 17 Feb 2010 11:04:09 -0800, you wrote: i would imagine you would have the same problem even in a local environment such as swing... the

Re: Large number components and redering time

2010-02-17 Thread Igor Vaynberg
On Wed, Feb 17, 2010 at 1:31 PM, b...@actrix.gen.nz wrote: Swing uses a variety of TableCellRenderer on a per table instance basis. if you had a table cell that needed a button then you wouldnt use a renderer What component are you suggesting to use for this behavior in Wicket? a

Re: Large number components and redering time

2010-02-17 Thread bht
In case of repeated buttons I think I would use a combination of a TableCellEditor and a TableCellRenderer with a button behind them, still only single instances serving many rows. There would only be a single event listener that would check selected row index. Would it make sense to have that in

Re: Large number components and redering time

2010-02-17 Thread Igor Vaynberg
we already provide support for all this... class cheaprenderer implements ilinklistener { protected void oncomponenttagbody(...) { ... getresponse.write(href=\); getresponsr.write(urlfor(this, ilinklistener.interface)+x=+x+y=+y)); } public final void onclick() {

Re: Large number components and redering time

2010-02-17 Thread bht
Many thanks. I like it. Good when memory is expensive :) On Wed, 17 Feb 2010 16:21:16 -0800, you wrote: we already provide support for all this... class cheaprenderer implements ilinklistener { protected void oncomponenttagbody(...) { ... getresponse.write(href=\);

Re: Large number components and redering time

2010-02-17 Thread dev
Hi, Igor Vaynberg wrote: i would imagine you would have the same problem even in a local environment such as swing... absolutely, I was just wondering what would be the best way to do it in Wicket... the solution is quiet simple, instead of using wicket components to model the table and the