After upgrading to prototype 1.5.0 and scriptaculous 1.7.0 my autocompleter.local died... firebug reports that effects.js is to blame calling Element.addMethods(); I can not find out why cause as far as I can see it does exist in prototype.js. Any pointers anyone :( --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
skaue
2007-Feb-21 10:27 UTC
Re: Element.addMethods() is not a function after upgrade to 1.7.0
Wow... didt take me long after posting my question before I found the problem... (after desperate attempts trying ANYTHING) Seems some function added in the code by Dreamweaver caused prototype to break: [code] /*function MM_jumpMenu(targ,selObj,restore){ //v3.0 eval(targ+".location=''"+selObj.options[selObj.selectedIndex].value +"''"); if (restore) selObj.selectedIndex=0; } */ [/code] On 21 Feb, 11:12, "skaue" <tommy.sk...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> After upgrading to prototype 1.5.0 and scriptaculous 1.7.0 my > autocompleter.local died... firebug reports that effects.js is to > blame calling Element.addMethods(); > > I can not find out why cause as far as I can see it does exist in > prototype.js. > > Any pointers anyone :(--~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
Fred
2007-Feb-21 23:12 UTC
Re: Element.addMethods() is not a function after upgrade to 1.7.0
On Feb 21, 8:27 pm, "skaue" <tommy.sk...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Wow... didt take me long after posting my question before I found the > problem... (after desperate attempts trying ANYTHING) > > Seems some function added in the code by Dreamweaver caused prototype > to break: > > [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. -- 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 rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
Eric Harrison
2007-Feb-22 10:58 UTC
Re: Element.addMethods() is not a function after upgrade to 1.7.0
> > > > [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 -E -- Eric Ryan Harrison --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
Colin Mollenhour
2007-Feb-22 16:33 UTC
Re: Element.addMethods() is not a function after upgrade to 1.7.0
Eric Harrison wrote:> 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 > > -E >Lol! Hilarious! Simple answer to your solution: don''t use Dreamweaver. I think you''re going to have a hard time getting any further advice from anyone here because there is no telling what the problem is... Colin --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
Fred
2007-Feb-23 02:12 UTC
Re: Element.addMethods() is not a function after upgrade to 1.7.0
On Feb 22, 8:58 pm, "Eric Harrison" <blis...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 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 rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
skaue
2007-Feb-23 07:26 UTC
Re: Element.addMethods() is not a function after upgrade to 1.7.0
On 22 Feb, 17:33, Colin Mollenhour <eliteii...-NPSFNn/7+NYVo650/ln6uw@public.gmane.org> wrote:> Eric Harrison wrote: > > 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 > > > -E > > Lol! Hilarious! > > Simple answer to your solution: don''t use Dreamweaver. I think you''re > going to have a hard time getting any further advice from anyone here > because there is no telling what the problem is... > > ColinI''m very satisfied with Dreamweaver and have been for the last 7-8 years using it professionally. That code snippet which crippled Element.addMethods() was commented out, but I could just as well remove it, cause the page did not use the function. And for what its worth; I stopped using the javascriptsnippets available within Dreamweaver many years ago, since there are a lot more elegant ways to solve those functions. But all these things are evolution. I bet if you poke your code from a couple of years ago (given you''ve been coding for a while) you''d find a lot of weird, unpractical, messy, bad performing, etc... code. We all find better ways while learning. And if YOU dont wanna help me cause I use Dreamweaver, I bet someone else will regardless of chosen tool ;-) -Tommy --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
Colin Mollenhour
2007-Feb-23 09:15 UTC
Re: Element.addMethods() is not a function after upgrade to 1.7.0
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> I certainly was not saying "I don''t want to help you because you use Dreamweaver". I was saying that nobody is going to want to dig through a bunch of Dreamweaver-generated code to fix problems as basic as loading Prototype if that''s the case. That''s all. Sorry if that came across impolitely... Anyway, apparently you are quite comfortable with Dreamweaver and like using IDEs, but considering how things have changed and the direction your web development has taken, you may consider an IDE that is... more geared toward your skill level, like Aptana perhaps.<br> <br> Colin<br> <br> skaue wrote: <blockquote cite="mid:1172215613.463295.107030-XPL1xs/Qva072vtPnJj/rmB/v6IoIuQBVpNB7YpNyf8@public.gmane.org" type="cite"> <pre wrap=""> On 22 Feb, 17:33, Colin Mollenhour <a class="moz-txt-link-rfc2396E" href="mailto:eliteii...-NPSFNn/7+NYVo650/ln6uw@public.gmane.org"><eliteii...-NPSFNn/7+NYVo650/ln6uw@public.gmane.org></a> wrote: </pre> <blockquote type="cite"> <pre wrap="">Eric Harrison wrote: </pre> <blockquote type="cite"> <pre wrap="">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 </pre> </blockquote> <blockquote type="cite"> <pre wrap="">-E </pre> </blockquote> <pre wrap="">Lol! Hilarious! Simple answer to your solution: don''t use Dreamweaver. I think you''re going to have a hard time getting any further advice from anyone here because there is no telling what the problem is... Colin </pre> </blockquote> <pre wrap=""><!----> I''m very satisfied with Dreamweaver and have been for the last 7-8 years using it professionally. That code snippet which crippled Element.addMethods() was commented out, but I could just as well remove it, cause the page did not use the function. And for what its worth; I stopped using the javascriptsnippets available within Dreamweaver many years ago, since there are a lot more elegant ways to solve those functions. But all these things are evolution. I bet if you poke your code from a couple of years ago (given you''ve been coding for a while) you''d find a lot of weird, unpractical, messy, bad performing, etc... code. We all find better ways while learning. And if YOU dont wanna help me cause I use Dreamweaver, I bet someone else will regardless of chosen tool ;-) -Tommy </pre> </blockquote> <br> --~--~---------~--~----~------------~-------~--~----~<br> You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. <br> To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <br> To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <br> For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en <br> -~----------~----~----~----~------~----~------~--~---<br> </body> </html> <br>
skaue
2007-Feb-24 22:15 UTC
Re: Element.addMethods() is not a function after upgrade to 1.7.0
Its all good m8... I just googled aptana and at first glance it looks appealing (/me downloads). Have a nice weekend! On 23 Feb, 10:15, Colin Mollenhour <eliteii...-NPSFNn/7+NYVo650/ln6uw@public.gmane.org> wrote:> I certainly was not saying "I don''t want to help you because you use Dreamweaver". I was saying that nobody is going to want to dig through a bunch of Dreamweaver-generated code to fix problems as basic as loading Prototype if that''s the case. That''s all. Sorry if that came across impolitely... Anyway, apparently you are quite comfortable with Dreamweaver and like using IDEs, but considering how things have changed and the direction your web development has taken, you may consider an IDE that is... more geared toward your skill level, like Aptana perhaps. > Colin--~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---