similar to: Firefox 1.5b1

Sorry if this sounds cynical, ( i do love script.aculo.us scripts ) , but I am wondering if people know of some good real world examples of uses of drag n drop and sortable lists. such a cute script will likely be *ab*used as much as it is used. obviously the point here is to use script.aculo.us to improve the user interface rather than just have some k00l eFX. e.g. the drag n drop instantly

I copied an exact copy of "http://demo.script.aculo.us/ajax/autocompleter" to my harddisc inclusive all .js and .css. Then I changed "new Ajax.Autocompleter(''contact_name'', ''contact_name_auto_complete'', ''/ajax/auto_complete_for_contact_name'', {})" to "new Ajax.Autocompleter(''contact_name'',

Hi list, So, some hard work today, but the Wiki is quickly taking shape. I''ve now moved all the documentation I could find into it. The URL again: http://wiki.script.aculo.us/ There are also some new features in there, like: FAQ: http://wiki.script.aculo.us/scriptaculous/show/FAQ Wishlist (moved from Rails wiki): http://wiki.script.aculo.us/ scriptaculous/show/TheWishlist And the

Hi list, With the very latest SVN trunk of script.aculo.us having all sorts of nice unit testing thanks to efforts of Jon Tirsen (and some make-it- look-good additions from Michael Schuerig) a very nice framework for (more or less pragmatic) in-browser unit testing of JavaScript (and HTML!) has come in to place (it''s still to be considered quite alpha, but it basically works).

I can''t get the inplace editor to do anything for me. The output appears as regular formated, unclickable text. Maybe I am missing something simple. 1. I just downloaded script.aculo.us <http://script.aculo.us> 1.5_rc3 and copied it to my javascript folder. 2. To set up a simple test, I created a new test page containing only the copied from demo1 from the script.aculo.us

Today marks the release of script.aculo.us 1.5_pre4 The single biggest addition are the new effects queue and the text effects. Head to http://script.aculo.us/__trunk_test/test/ run_functional_tests.html and give "effects_queue" and "texteffects_test.html" a try. As always, loads of fixes and improvements. Specials thanks to all of you who help with ideas, patches and bug

I am new to script.aculo.us and prototype and I am having problem using it. It only has problem in IE. There is no problem in Firefox and it works fine. I am using script.aculo.us InPlaceEditor and it always returns object expected as an exception. What I could debug so far is I could see element and url which are the parameters. I could see object in Ajax.InPlaceEditor after creating class but

Hi, I noticed that the scriptaculous shopping cart demo doesn''t work in safari 1.03. I was wondering if there was documentation somewhere that would tell me what my minimal browser requirements were for running scriptaculous? I found this comparative analysis on the web: http://wiki.osafoundation.org/bin/view/Projects/AjaxLibraries but I think it might be a bit out of date. I did

So, the first script.aculo.us 1.5 release candidate is out! Important changes and fixes from 1.5_pre4 (for a detailed list, see the CHANGELOG file): * Droppables w/greedy and hoverclass are now reverted when dragged item is no longer over them, fixes #2184 * Let Effect.Highlight correctly parse IE colors, add String.prototype.parseColor() for this, fixes #2037 * Make scriptaculous.js work

Heya, I''m doing a one-day training on everything Ajax mainly focusing on script.aculo.us, but naturally including Prototype and a look on Ruby on Rails Ajax capabilities as well, on March 17, here in Vienna, Austria (for german speaking audiences). Here are the (in-german) details: In diesem eintägigen Seminar zeigt Ihnen Thomas Fuchs wie Sie die Benutzerfreundlichkeit und

Hi, i''m trying to use a visual indicator for my Ajax requests. It''s based on the shopping cart demo at script.aculo.us and works great in Firefox, Konqueror and Opera, but fails in IE6. For some reason (timing problems?) onComplete is executed before onLoading, so the indicator is shown but not hidden when the request has finished. Oddly enough it works fine in the shopping

Hi all, Been working with prototype and script.aculo.us now for around 3 days after never really touching javascript so I am still getting to grips with things. So far I have successfully created 4 ajax based functions, or so I thought until I stupidly showed a client one of them before I had tested it in IE. The function in question works fine in FireFox succesfully inserting any new values

* I sent this message previously from the wrong address so it didn''t go through so, I apologize in advance if a duplicate shows up * Hello, I am very new to script.aculo.us and prototype but was trying to implement some of the cool ajax functionality with Webwork. I have been having a little trouble with the sortable element demo. I have the following code below: <html>

I ran across an issues using the Autocompleter over HTTPS in IE (6.0 in WinXP Pro SP2). I plan to submit a bug report to the Ruby on Rails trac, but first I''d like "to discuss this on th[is] Mailing List beforehand, maybe it''s already known and in the works, or it isn''t a bug" (per http://wiki.script.aculo.us/scriptaculous/show/BugReports) The autocomplete

|Hi i''m New First Question: to use a script.aculo.us it needs to include prototype.js and scriptaculous.js.... but doesn''t work!!; instead ||using ||scriptaculous.shrunk of Alister Cameron, work; what are the expedient to use to include the ||scriptaculous.js ? Second question: in script.aculo.us |Ajax.Autocompleter

Heya, I''ve just released script.aculo.us V1.5_pre1. Please give it a try! Important new stuff (since V1.1b1): * Added a main scriptaculous.js file to load in the other libraries transparently. * Fixed a condition where standard a href=xxx links wouldn''t work in autocomplete results. These do now, the onclick event is not cancelled. [thx to Jasper Slits] * Added

I have been working with the Ajax.Autocompleter for about a day so forgive my ignorance. Is there any value in adding additional callbacks. I want perform an action when the user selects a choice. So I was thinking of adding an option {select: function(selectedElement) {}} similar to the callbacks on Ajax.Request in the prototype library. Call me out if you think I am crazy my feelings

I had one point in my project where I needed a synchronous Ajax call; in other words, I wanted the Ajax.Updater call to not return until the content of my page had been updated. However, I found that if you call Ajax.Updaterwith the {asynchronous: false} option, the onComplete() function would never be called and your content would not be updated. Was this the intended behavior? I added the

Hi folks, I''m in the process of updating a mostly-server-side web app to 21st century functionality, using the prototype.js etc packages. I''m mostly a server-side PHP guy, so please pardon the level of ignorance about Javascript. I''m having some strange problems, and right now, I''m trying to localize whether the problems are generic browser-things or whether

I''ve managed to consistently crash firefox 1.5 (mac) using script.aculo.us. Is this a known issue? The page in question works in Safari enough. It happens on a link_to_remote where I''m :updating the same div that I''m currently in. Would it help if I try to isolate the code? Would it be more a firefox bug, or a JS bug? i.e. do we think we can fix the