Hey
Nick,
This
was checked into svn on 29th March...
Are
you using the library version that was written much before
that?
If
not, then this might still not address the problems.
Thoughts?
-Mandy.
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]O
This is just my opinion, but after looking at the code I would say
that Form.element has a lot more to do with the retrieving data
(serialize, getValue) and Field has a lot more to do with the state of
the field (clear, focus, select, etc). I guess in the end it doesn't
really matter because they
Quick design question. I am trying to get a better understanding of
Prototype. While reading through the source I am stumped by form.js.
There is a "Field" object and a "Form.Element". Both object seem to
consists of a series of actions that making interacting with form fields
easier.
My ques
OK, scrap this, check out the latest in svn. this issue got raised in trac: http://dev.rubyonrails.org/ticket/4465On 5/11/06,
nick hemsley <[EMAIL PROTECTED]> wrote:
Disclaimer: Im still getting used to dynamic scoping. & _javascript_ as well.Which part clobbers window.property? If this _is_ the c
Hi,
I am using Rails' link_to_remote() and I want to do the same thing
Yahoo! UI's connection manager "argument" can do. From the Yahoo! UI
docs:
"argument: an object, string, number, or array containing data that
your success and failure functions might need in order to successfully
process the
My company uses DWR as our AJAX library to deal with our Java code on
the back-end. I would really like to use script.aculo.usto do all the cool
things it can do. Unfortunately, it seems the DWR and script.aculo.us/prototype
have functions and variables that use the same names. Is there a g
Disclaimer: Im still getting used to dynamic scoping. & _javascript_ as well.Which part clobbers window.property? If this _is_ the case, then suiltably unique name would be a temporary, but if you are talking about the for() loop itself, that is unchanged from the original source... actually lookin
On 5/10/06, nick hemsley <[EMAIL PROTECTED]> wrote:
for (property in methods) {
for (var property in methods) {
ensures that you're working with a locally-scoped property variable.
The way it's written, if window.property existed, then you just
clobbered it.
Todd
___
Slightly nicer:Element.extend = function(element) { if (!element) return; if (!element._extendedMethods) element._extendedMethods = {} if (!element._extended && element.tagName && element != window) {
var methods = Element.Methods; for (property in methods) { if (typeof methods[pro
