Or wrote:
>Wouldnt that take quite alot of conventional memory?
All that's required are pointers to xSwap (normally XMS) for each event in
every "HTML atom". Of course the ammount used depends on the ammount of
events implemented (and the number of atoms on the page in question). An
alternative would be to have one pointer to xSwap for all events (in every
atom) but the pointer conversion would IMHO make it too slow then.
(pointer, indexing and pointer again and then we have arrived to the actual
JS).
Personally I see no use for any events but onMouseOver, onMouseOut and
onClick so I'll start with them (or rather I've started with onClick so far
and have looked somewhat into onMouseOver. The events are rather
straightforward - the user functions and the entire object model of
JavaScript will be the tricky part. But by going step by step more and more
pages should be usable for Arachne users.
