On Feb 22, 8:58 pm, "Eric Harrison" <[EMAIL PROTECTED]> wrote:
> > > [code]
> > > /*function MM_jumpMenu(targ,selObj,restore){ //v3.0
> > > eval(targ+".location='"+selObj.options[selObj.selectedIndex].value
> > > +"'");
> > > if (restore) selObj.selectedIndex=0;}
>
> > If that is indicative of the quality of code provided by Dreamweaver,
> > I would stop using it immediately.
>
> Oh come on now Fred. Can't you see that Dreamweaver is using eval?
> That is obviously some high-level JavaScript coding... ;) Perhaps it's
> just TOO complex for our feeble minds to comprehend.
>
> I, for one, congratulate Dreamweaver in their efforts of making a
> large portion of the web development community mindless zombies. It
> makes it much easier for me to get work... :D
<g>
Great response!
But it's more than just eval - the addition of an empty string to the
value returned from the form control (presumably to force it to being
a string) is pointless - it's already a string.
Apart from that, there's the well-known user access issues of using a
select element for navigation, made particularly onerous if it keeps
resetting itself.
--
Fred
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Spinoffs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---
