> Is it because it is not accessing the javascript files correctly

Yes. The prototype.js and scriptaculous.js files returned by your
server[1][2] are HTML files; they look like you've gone to the
script.aculo.us github account, viewed the source (with markup and
surrounding github stuff) and done a "save as" or something. You need
to download[3][4] and (in the case of script.aculo.us) unpack them
correctly. There's a "quick start" on the script.aculo.us wiki[5].
Note that although I've linked the download page for prototype below,
you can use the one supplied with script.aculo.us in its `lib`
subdirectory. Scripty is still supplying, though, and 1.6.1
has been out a while now. You'd have to ask someone more knowledgeable
about scripty than myself if scripty 1.8.3 is thoroughly tested with
1.6.1; I'd guess not, or the package would have been updated by now.

[1] http://caritos.github.com/javascripts/prototype.js
[2] http://caritos.github.com/javascripts/scriptaculous.js
[3] http://prototypejs.org/download
[4] http://script.aculo.us/downloads
[5] http://wiki.github.com/madrobby/scriptaculous/

T.J. Crowder
Independent Software Consultant
tj / crowder software / com

On Jan 24, 9:29 am, sotirac <soti...@gmail.com> wrote:
> Having trouble getting the Effect.toggle to work.
> Is it because it is not accessing the javascript files correctly or
> something else.
> you can view the sample code live athttp://caritos.com.
> The source code can be viewed here:
> http://gist.github.com/285116

You received this message because you are subscribed to the Google Groups 
"Prototype & script.aculo.us" group.
To post to this group, send email to prototype-scriptacul...@googlegroups.com.
To unsubscribe from this group, send email to 
For more options, visit this group at 

Reply via email to