Re: isElement - determining if an object is an element

"Henry" <rcornford@xxxxxxxxxxxxxx> wrote in message
news:5e276c47-b1ed-4c6f-8a39-71f1ce7243fe@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Jul 31, 5:15 pm, Aaron Gray wrote:
Henry wrote in message
On Jul 31, 4:19 pm, kangax wrote:
<snip>
... . It appears, though, that the need
for "isElement" exists.

How does that appear? It appears that there is a desire and that
the desire is being serviced but nothing has yet suggested a need.

You have to double or tripple up on constructors to do the same
trick. Its neater with one constructor and using what in static
class languages is called overoading.

That should be 'overloading'.

That does not follow, and still no need then.

Basically take an accordian widget, that either gets initialized from a DIV
or UL,LI structure, hence needing to know its element based, or via a JSON
based approach. Now either you have two constructors one for each casew or
you have one overrided constructor that detects the parameter type. Which is
what I prefer to do until I see any reason not to and to use two
constructors.

Aaron


.

Relevant Pages