So is this something worthy of core prototype?
On 1/26/08, kangax <[EMAIL PROTECTED]> wrote:
>
> Simple subclassing should do the job (haven't tested but it should
> work):
>
> Ajax.Replacer = Class.create(Ajax.Updater, {
> initialize: function($super, container, url, options) {
> options =
Ok so I have the request object. Sorry for the ignorance but how to I
get for example a parameter called "fieldName" I sent.
request.getParameter("fieldName") Will this work?
Shy.
On 27 ינואר, 03:52, Tobie Langel <[EMAIL PROTECTED]> wrote:
> Hi,
>
> The request and transport objects are av
found a ticket for this issue
http://dev.rubyonrails.org/ticket/9466
gonna attach this example too
On Jan 18, 9:51 am, "Michel David" <[EMAIL PROTECTED]> wrote:
> I attached a demo file and two prototype 1.6 files...
> The fixed version was made by myself, but you can user the prototype version
Someone correct me if i'm wrong but the parameters/postbody you sent do not
automatically come back in your response/transport.
What I do, is anything I *need* to come back, eg an element id etc, I pass
in the querystring instead of the form (append to the URL).
The reason i do this, (i use asp.ne
Hi,
I just made a really simple benchmark:
var d = new Date;
/* Prototype 1.6.0.1 entire source code */
alert(new Date - d);
On my macbook it alerts (in milliseconds) :
6 in Safari 3
12-13 in Firefox 2
12-20 in Opera 9
Is Prototype initialization a bottle-neck ?
I definitely don't think
Try:
new Ajax.Request(url, {
parameters: { foo: 'hello world' },
onComplete: function(t) {
alert(t.request.parameters.foo);
}
});
Best,
Tobie
On Jan 27, 11:12 pm, "Gareth Evans" <[EMAIL PROTECTED]> wrote:
> Someone correct me if i'm wrong but the parameters/postbody you sent do not
>
Gareth,
new instance of Ajax.Response is passed as a first argument into a
callback. That instance has request property which points to request
object (the one that has all your settings/parameters, etc.). I don't
really see a reason to do what you're doing.
Best,
kangax
--~--~-~--~~
I always thought the parameter to the callback was just the server reply
(response)
The docs show transport as a param, I didn't realise it was an instance of
the request.
Given this information, you're right, there's not a lot of sense to what i'm
doing.
After a quick spot of searching the API d
