Thomas,
Sorry for the delayed reply. This is the first time since the
release that the bug tracker has worked for me, despite several
attempts daily. (It failed a couple of times today too.)
There are still a few issues with scrolling and draggables. Bug 5017
has references to several of them, and the patch suggested there can
be implemented independent of the other scrolling drag/drop issues.
I also have some more general questions. The bottom line here is, I
want to help, but am a "guest" in your "house"--I don't want to be
figuratively rearranging the furniture without your permission. A set
of posted community standards would be helpful to me. Specifically:
Do you want our help filtering the bug list? What's the best way to
go about it--do you have some "moderator" guidelines available?
See bug 2766, for example. The problem is most likely with the
submitter's style sheet, not Scriptaculous. Despite two requests for
a test case, the submitter hasn't responded in six months. Do you
want our help in closing these bugs?
If you wish to retain control over closing bugs, may I suggest a
common set of helper keywords, such as "DUPLICATE", "NOTABUG", and/
or "ABANDONED"?
Other questions regarding the bug tracker:
1. Is there a better way to filer by Scriptaculous component? For
example, Draggables, Effects, Builder, etc. I'm significantly more
comfortable in the Draggable code than in the Builder code, for
example. Is there a custom field or set of accepted keywords that can
make filtering the list a bit easier?
2. Is there a way for us to indicate "votes" for a particular bug/
patch in a way that will appear on the search results list?
3. What methods are in place to reduce/eliminate comment spam?
Regards,
Tom Gregory
On Aug 15, 2006, at 8:48 AM, Thomas Fuchs wrote:
script.aculo.us 1.6.2 is ready for download at http://
script.aculo.us/downloads
This release is a (mostly) bug-fix only service release.
As always, thanks to all who did patches and/or reported issues! :)
Reports (good or bad) are welcome. If you find something was
omitted (that is,
pending patches not being included), please say so. :)
Best,
Thomas
_______________________________________________
Rails-spinoffs mailing list
Rails-spinoffs@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
_______________________________________________
Rails-spinoffs mailing list
Rails-spinoffs@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs