I don't know if this is really something I can fix via Prototype, or if it's in
any way a Prototype issue, but I'll try here first. Here is my problem - which
unfortunately I can’t show you because I'm only developing it on my local
system at the moment - slightly simplified:
I have a pair of
On 29 Sep 2011, at 15:00, Chris Sansom wrote:
I've tried various things to stop it caching, such as loading the top image
via a tiny php script
Forgot to mention, before anyone else does, that the first thing I tried, after
Googling, was to put various query strings [such as '?' + (new
On 29 September 2011 15:00, Chris Sansom ch...@highway57.co.uk wrote:
In sequence, this happens:
- User clicks image
- Ajax request is created, running a php script with various parameters, in
which...
- ...the necessary renaming takes place (which involves checking for
duplicates
On 29 Sep 2011, at 15:51, Richard Quadling wrote:
Does ALL the JS work take place inside the onSuccess callback?
The Back in JS bit has to be part of the onSuccess callback
otherwise it will happen out of sequence. The A in AJAX is potentially
the hiccough here.
That's what I suspected but
On 29 September 2011 16:58, Chris Sansom ch...@highway57.co.uk wrote:
On 29 Sep 2011, at 15:51, Richard Quadling wrote:
Does ALL the JS work take place inside the onSuccess callback?
The Back in JS bit has to be part of the onSuccess callback
otherwise it will happen out of sequence. The A
This is an interesting problem... my first reaction is that you'd want
to use onComplete to update the div's instead of onSuccess.
Test this with a couple of alerts and see which one gets called first and
which is last (just as onCreate is the first call, onComplete is the last).
To my way if
I didnt address the caching because I had to look to see if I could find
where I had saved this link off the last time I had this problem... found
it!
The caching is probably on the browser side, not the server side. Setting
the server side cache variables will only affect the page reload.
The
i know you resolve your problem but It wont be easy if you delete from
the dom the img / tag storing the actual images then... create new
new Images() append to the div and finally add a query cheat link???
just a shot...
best
ncubica...
On 29 sep, 13:28, Phil Petree phil.pet...@gmail.com wrote:
What I have done in the past is to simply update the src attribute of the
image. The result is immediate and doesn't suffer from any cache issues.
Walter
On Sep 29, 2011, at 8:58 PM, ncubica wrote:
i know you resolve your problem but It wont be easy if you delete from
the dom the img / tag
ok ... So T.J. I know you not have the ultimate decision for designate
a candidate for any position at Prototype community but certanly you
are the most near with the core team. So I would like to know if you
could email one of them and try to start designate person for
revitalize this
Walter, you're right that's generally all that's needed but since one img
name would stay the same the browser would look in cache first and not
reload the image... which is what he's experiencing.
On Sep 29, 2011 9:39 PM, Walter Lee Davis wa...@wdstudio.com wrote:
What I have done in the past is
Might have been asleep during my previous google searches but I found
tj's site http://proto-scripty.wikidot.com today which seems like
answers questions of what I would want and think prototype needs to
grow.No sense in reinventing something that is there which is what
I ahd posted
12 matches
Mail list logo
