Subject has been changed...
"Lasse Reichstein Nielsen" <lrn@hotpop.com> wrote in message
news:n0dguqeq.fsf@hotpop.com...[color=blue]
> "Richard A. DeVenezia" <radevenz@ix.netcom.com> writes:
>
>
> What you can do, is to assign the onmouseout handler from Javascript
> instead:
>
> var adjunctData = { a:1, b:2, c:3, ..., j:10 }
> document.write('<td id="foo"> .... </td>');
> document.getElementById("foo").onmouseout =
> function () {
> Out(this,adjunctData);
> };[/color]
I like this solution very much and is quite in step with my concept that the
adjunctData really belongs to the cell.
I don't like having to id and get, but in this approach those steps are
unavoidable.
As you stated prior it's not good practice or valid to add custom properties
to HTML tags, but how about post rendering of the HTML ? This works, but is
adding properties to existing window objects.
document.write('<td id="foo" onmouseout="Out(this)"> .... </td>');
document.getElementById("foo").adjunctData = { a:1, b:2, c:'I will appear',
d:4, e:5, f:6 }
Out = function (o)
{
o.innerHTML = o.adjunctData.c // cell innerHTML changes to 'I will
appear'
}
[color=blue]
>
> This avoids Javascript creating more scripts as strings, which I
> personlly don't like.
>[/color]
concur
[color=blue][color=green]
> >
> > document.write ('... <TD onmouseout="Out(this, ' + function () { return
> > adjunctData } + ')" > text </TD>...')
> > might work (will try soon)?[/color]
>
> Probably not. The function is still converted to a string. That string
> is then parsed again as Javascript, but in a different scope. The
> scope is lost because you go through a string. Strings have no notion
> of scope or evaluation context.
>[/color]
didn't work, the return was undefined ... unless it was a global ref
[color=blue]
>[color=green]
> > adding and managing a function property of type array that holds[/color][/color]
references[color=blue][color=green]
> > to the 'parametric' objects and pass the index into this array[/color]
> ...
>
> This is simply the simplest way of not polluting the global namescape:
> Create *one* global variable, put an object (e.g., a function) in it,
> and store the rest of your variables in that object.
>
> Building an array, and using an integer as index, is not different from
> indexing an object by name ... it's just easier to come up with the
> names :)[/color]
I've done this on other pages, but get annoyed I have to id something I
already have.
[color=blue]
>[color=green]
> > Of these is there a 'best of breed' technique, or is it more a matter of
> > personal style ?[/color]
>
> Personal style goes a long way :)
>[/color]
After a fair amount of experimentation, I found I could build the table
without document.writing any HTML at all!
Not sure how cross-browser this is, but works for my windows IE6 and is spot
on for my personal style.
Again the question of propriety and validness is raised regarding adding
properties to window elements. I don't know.
function X (s) {
this.abc = 123
document.write (
'<P>' + s + '</P>'
+'<TABLE ID="myTable" BORDER="1" CELLPADDING="10"></TABLE>'
)
table = window.myTable;
// is document.getElementById really needed if window.<id> or
window['<id>'] seems to always work ?
row = table.insertRow (0);
cell = row.insertCell (0);
cell.innerHTML = 'Show me'
cell.foo = '123'
cell.adjunctData = { a:1, b:2, c:'I will appear', d:4, e:5, f:6 }
cell.onmouseover = function (EventSource) { X.over (this) } // during
invocation context this is the cell
}
X.over = function (o)
{
o.innerHTML = o.adjunctData.c
}
X('Hello')
--
Richard A. DeVenezia
