On Thu, May 20, 2010 at 12:28 PM, Edward Zarecor
wrote:
> Rewinding this thread. Comments and suggestion in-line.
>
>
> > The problem is that it renders very slowly in browsers.
> >
> > The reason is not directly network speed but it is the VERY heavy
> > markup. Each table cell has 3 ajax compo
Hi!
> So you're doing ~60 network round trips for the calender component alone, if
> I understand correctly,
No, that's not it, you have misunderstood. No roundtrips. Just single
pageload. Ajax events occur only if user clicks on components, but
that is not the issue. The issue is the heavy marku
Rewinding this thread. Comments and suggestion in-line.
> The problem is that it renders very slowly in browsers.
>
> The reason is not directly network speed but it is the VERY heavy
> markup. Each table cell has 3 ajax components and the ajax call
> functions are loong.
>
>
So you're
Well not true in this case, because it's the rendering itself that are
slow not the transfer. But true it will add a overhead to page load
transfer time and if latency are bad it would be even worse.
2010/5/20 Matthias Keller :
> And it would not speed up page loading at all since in the end, the
Depends on how you do it, but if you always know the height then no,
the rows would just appear.. You could use a ajax indicator to tell
the user that the page are loading.
2010/5/20 Martin Makundi :
> Would this not flicker a lot?
>
> **
> Martin
>
> 2010/5/20 nino martinez wael :
>> ok the idea
Hi.
W dniu 2010-05-20 10:28, Matthias Keller pisze:
And it would not speed up page loading at all since in the end, the
same data would have to be transferred but splitted into multiple
requests which adds the request overhead to the total loading time
compared to the prepared complete page.
And it would not speed up page loading at all since in the end, the same
data would have to be transferred but splitted into multiple requests
which adds the request overhead to the total loading time compared to
the prepared complete page.
On 2010-05-20 10:25, Martin Makundi wrote:
Would thi
Would this not flicker a lot?
**
Martin
2010/5/20 nino martinez wael :
> ok the idea are this:
>
> First render the page with out the grid.
> Then add the empty grid
> Then add row 1 to grid
> Adding row 1 triggers a new request adding row 2 and so on until all
> rows are loaded..
>
> All done wi
ok the idea are this:
First render the page with out the grid.
Then add the empty grid
Then add row 1 to grid
Adding row 1 triggers a new request adding row 2 and so on until all
rows are loaded..
All done with ajax.
It's just an idea, but I think it should help. However it causes more
load on t
Yes.. what you mean cascade load?
**
Martin
2010/5/20 nino martinez wael :
> No havent had the problem myself. But I guess you should start by
> loading the page without the listview enabled, and then add the
> listview afterwards and see if that helps. Next step would be to
> cascade load the ro
No havent had the problem myself. But I guess you should start by
loading the page without the listview enabled, and then add the
listview afterwards and see if that helps. Next step would be to
cascade load the rows...
2010/5/19 Martin Makundi :
> Hmm.. can you show me an example of something lik
Hmm.. can you show me an example of something like that, how is it done?
**
Martin
2010/5/19 nino martinez wael :
> about the lazyloading, I was thinking to cascade load the rows after
> page render, it should perform better in theory:)...
>
> 2010/5/19 Martin Makundi :
>> Hi!
>>
>>> hmm could'nt
about the lazyloading, I was thinking to cascade load the rows after
page render, it should perform better in theory:)...
2010/5/19 Martin Makundi :
> Hi!
>
>> hmm could'nt just use a custom ajax decorator? Or override the js part
>> of the onchangeajaxbehaviour?
>
> Hmm.. sounds like a good start
Hi!
> hmm could'nt just use a custom ajax decorator? Or override the js part
> of the onchangeajaxbehaviour?
Hmm.. sounds like a good starting point... thanks.
BTW: I totally lost you on that lazy loading thing... the user would
like the page to load in a snap and using it to be like a snap. Ho
hmm could'nt just use a custom ajax decorator? Or override the js part
of the onchangeajaxbehaviour?
2010/5/19 Jeremy Thomerson :
> Well, if the rendering of all that extra JS is what's causing the problem,
> I'd try to limit it to one rendering of the (slightly-modified) behavior.
>
> You can bas
2010/5/19 Martin Makundi :
> Hi!
>
>> Otherwise you could extract the long inline
>> code into a seperate js and wrap them into induvidual methods,
>> although I do not know if it makes page load faster or there could be
>> other issues.
>
> I will try somehow the individual function approach. My p
Hmm.. I am afraid of losing the component update processing in
onchangeajaxbehavior and its superclasses.
Actually the true solution is to leave out the selects completely ,] I
wonder if I could render them somewhere else... like bottom of page
and then just move them onto the table when displayin
Well, if the rendering of all that extra JS is what's causing the problem,
I'd try to limit it to one rendering of the (slightly-modified) behavior.
You can basically render something like this:
function somethingInMyTableChanged(rowInd) {
return wicketAjaxGet('{standardBehaviorUrl}&rowIndex='
Hi!
Yes.. my question now is: how to easily extract the JS? It is from
onchangeajaxbehavior etc.
I would like to continue using wicket standard onchangeajaxbehavior
but somehow override the way it injects the js into the component tag.
Suggestions to accomplish this?
**
Martin
2010/5/19 Jeremy
If you've already proven that removing the AJAX removes the contention, I'd
go with Nino's "otherwise" route. That was my first guess. Depending on
what you're doing with those AJAX calls, you could probably make it so that
you have one to three of them for the entire table, wrapped in a custom
f
Hi!
> Otherwise you could extract the long inline
> code into a seperate js and wrap them into induvidual methods,
> although I do not know if it makes page load faster or there could be
> other issues.
I will try somehow the individual function approach. My point is,
however, that there is very
The easiest thing would probably to lazy load the rows somehow, how
are load time pr row?.. Otherwise you could extract the long inline
code into a seperate js and wrap them into induvidual methods,
although I do not know if it makes page load faster or there could be
other issues.
2010/5/19 Marti
Hi!
HELP!
I have a problem. I have a table with 20 columns and 30 rows ("calendar").
The problem is that it renders very slowly in browsers.
The reason is not directly network speed but it is the VERY heavy
markup. Each table cell has 3 ajax components and the ajax call
functions are lo
23 matches
Mail list logo
