I am building a iPhoto like (Read rip-off) interface for thumbnails and I am having a couple problems that I thought some one on the list might be able to assist me on ... first off here is the page: http://v4.incontrolsolutions.com/galltest/I am no _javascript_ whizz and I am sure there is a FAR m
Well, both. ajaxOptions is used to pass-through options to the
underlying AJAX infrastructure inside the InPlaceEditor. So they are
the standard Ajax.Xxxx options. The use of 'ajaxOptions' itself for
this purpose is probably not entirely standard (but maybe it should
be).
On 1/31/06, Jamie Orchard
Hi Jerod
WoW! Thanks for the great response. I will check out all the links
that you gave me and read in the scriptaculous wiki.
Thanks again!
Peter
On 1/29/06, Jerod Venema <[EMAIL PROTECTED]> wrote:
> Hey Peter!
>
> Many of the questions you have are mixed into two areas. One is
> script.aculo.
i am having problems with editing items which are inside a sortable list...
different on browsers
PC IE - Works fine
PC FF - select boxes work, input boxes are NOT editable
MAC Safari - select boxes are NOT edtable, input boxes work
thanks!
___
Rails-sp
It's standard with anything ajax related.On 1/30/06, Jamie Orchard-Hays <[EMAIL PROTECTED]> wrote:
Thanks for that tip Jon. I hadn't noticed that one. So ajaxOptions isstandard in the framework?btw, Nicolas's solution also worked.JamieOn Jan 30, 2006, at 2:57 PM, Jon Tirsen wrote:> I think you shou
Thanks for that tip Jon. I hadn't noticed that one. So ajaxOptions is
standard in the framework?
btw, Nicolas's solution also worked.
Jamie
On Jan 30, 2006, at 2:57 PM, Jon Tirsen wrote:
I think you should be able to use the ajaxOptions option just like you
would any other option for an Ajax
I think you should be able to use the ajaxOptions option just like you
would any other option for an Ajax.Request. IIRC ajaxOptions:
{onSuccess: function() {...blah...}} should do the trick.
HTH
Cheers,
Jon
On 1/26/06, Jamie Orchard-Hays <[EMAIL PROTECTED]> wrote:
> I'm looking for onSuccess: in
thanks greg, i changed it to onChange... but its still not doing
anythin!! AHHH...
i even pared it down to only the alert, and nothing. the list IS
draggable, so the JS is running. and i am doing it in firefox to watch for
JS errors but nothing.
here is my new code:
Oh... if you use 'onUpdate', then you must follow the rules for
Sortable.serialize (i.e. each element has an id that matches the pattern
\w+_\d+ (such as item_1, item_2, etc)). This is because onUpdate uses
Sortable.serialize before and after the drag to see if the value
changed. If you would rat
oh right, value... god i always do that.
but, its not even alerting 'hi' so its not getting to that point even.
its making the list sortable, but nothing happens after i drag around.
> Well, if they are hidden input fields, then I'm not sure you can use
> innerHTML (all self-enclosed tags
Well, if they are hidden input fields, then I'm not sure you can use
innerHTML (all self-enclosed tags should have no innerHTML). You need
to set the value on them (ids[i].value = '' + i, instead of
ids[i].innerHTML = i). Or by 'hidden fields', do you not mean ?
Greg
ids is an array of all elements with the class name of 'linkIndexNumber'
which is only the hidden fields.
i figured that getElementsByClassName would return them in the order they
appear on the page, so i am using that to base which number they are in
the list.
then i am setting each of them to t
Assuming that $(ids[i]) is the hidden input field, wouldn't the
following line need to reference it as a form element?
> $(ids[i]).innerHTML = i;
I would assume it should be (the "'' + " makes it a string, not sure if
you can set a form element value to an in
here is most likely an easy question how come this will not work?
i am trying to change the values of a hidden input inside each sortable to
the current index.
thanks!
Sortable.create('list_filmLnks', {
onUpdate: function() {
Thanks Nico, I'll try that and then look at adding a patch for onSuccess.JamieOn Jan 28, 2006, at 6:24 AM, Nicolas wrote:I'm using : "if (!transport) return;" at the beginning of onComplete.It does the trick.Regards,NicoOn 1/26/06, Jamie Orchard-Hays <[EMAIL PROTECTED]> wrote:I'm looking for onSuc
Thomas, I’m mostly writing this to you. A couple weeks
ago I grabbed the latest SVN version of dragdrop.js because I needed the
auto-scroll functionality. I just fixed something in that script that wasn’t
working correctly and thought you might want to hear about it. You may have
already ca
Code for AjaxQueue with example usage:
var AjaxQueue = {
batchSize: 1, //No.of simultaneous AJAX requests allowed, Default : 1
urlQueue: [], //Request URLs will be pushed into this array
elementsQueue: [], //Element IDs of elements to be updated on
completion of a request (
Thanks. I'll have a look at this.
Eifion
On 30 Ion 2006, at 12:27, Irfan, Ghouseuddin Syed wrote:
I have written this small script for queuing ajax calls. Hope this
helps.
//
-
var AjaxQueue = {
batchSize: 1,
Adding requests to the queue:
AjaxQueue.push(url, options); // for Ajax.request
AjaxQueue.push(url, options, elementId); // for Ajax.updater calls
Default batch size is 1.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Irfan,
Ghouseuddin Syed
Sent: Monday, J
I have written this small script for queuing ajax calls. Hope this helps.
//-
var AjaxQueue = {
batchSize: 1,
urlQueue: [],
elementsQueue: [],
optionsQueue: [],
setBatchSize: function(bSize)
afaik firefox has a limit of 2 concurrent xmlhttp requests and ie not ...you could build a sort of queue for your requests (queueing ajax requests if active request count > 2 or sth else) hth
2006/1/30, Eifion <[EMAIL PROTECTED]>:
This is slightly OT for which I apologise in advance, but I waswonde
This is slightly OT for which I apologise in advance, but I was
wondering if anyone here has had any problems when making multiple
ajax calls at the same time. I'm working on a large Intranet
application which makes heavy use of ajax calls and the bugs are
flying in from the testers that if
Also when I
recreate the Sortable, the page becomes sluggish. AFAIK the sortable.create()
destroys the old sortable and recreates a new one, then why is it eating up the
browser memory. The dnd becomes sluggish as time passes by.
Regards
Varun Mehta
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
23 matches
Mail list logo