Hi Peter,
PHP is outputting the default state of the drop downs.
Without javascript the user clicks the button, the page refreshses and
the secondary content area containing the drop downs is refresh by
PHP.
With javascript I don't go back to the server - jquery refreshes the
content (stops page jigging up and down and, even with delay, is a
better experience)
Are you saying that don't use jquery to pick over the dom to refresh
the content but get it to fetch the raw xhtml from the serverside?
Joel
(p.s.. annoyingly I've posted this message atleast twice - couldn't
get my head around Google groups pah!)
On Oct 3, 1:02 am, Peter Bengtsson [EMAIL PROTECTED] wrote:
Can't you do it in the server side templating language. Bound to be
much much faster.
On 10/2/07, jojet [EMAIL PROTECTED] wrote:
Hi all,
this is my first message here so apologies if I'm breaking protocol!
I have posted some code at a href=http://paste2.org/p/7819;
http://paste2.org/p/7819/a
Basically the above code gets executed when the user clicks on a
button and its purpose is to refresh a secondary content area which
is a long list of select boxes (90?). It refreshes the select boxes
based on some previously retrieved JSON data ('slotData').
My issue is that is takes a while (2.5 secs) to run this routine which
is a bit of a pain from a user experience point of view. Yes I can put
please wait... etc but I'd like first to trim this time down as much
as possible.
I was hoping someone might be able to spot where I'm going wrong as
far as coding/performance is concerned.
It gives me these kind of speeds on IE7, IE6, FF2. Oddly enough Safari
on Windows runs lightning fast!
I realise that lines 19 to 23 don't really need to be in the nest sub
routine but moving them outside doesn't change much.
Any thoughts (however general) gratefully appreciated.
Joel Hughes
--
Peter Bengtsson,
workwww.fry-it.com
homewww.peterbe.com
hobbywww.issuetrackerproduct.com