Daniel Carrera wrote:
Kay Schenk wrote:
What Daniel would like would be *insanely* uncomplicated if we had a DB backend and could use something like php or Perl cgis to access it.
However, using JS to do basically DB operations is a nightmare! What happens is all possible entries must be maintained as individual items within the script itself.
NO no no no.
Look at the implementation I proposed. I proposed that tasks lie inside <div> tags and that we use the 'id' attribute for the classification.
For example:
<div id='component=writer__difficulty=medium__skill=C'>
I'd need to look into further but I'm fiarly certain what you're proposing won't work--well not in the way you're thinking anyway. You'd need a completely separate identifier for each an every task...not just the lot lumped under some <div> tag as you've indicated. Really this sounds like a LOT of very complicated JS, but, again, I'd need to look into further.
I'll need to get back to this in a day or two after some research.
-- ====================================================================== MzK
Kay Schenk
"Things have a way of workin' out if you can just keep your head out of your behind." -- Piebald Plato
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
