I cranked out a library for making prototype based (custom styled) scrollbars over the weekend. If anybody has some time, I''d love some feedback on it: http://theblogthatnoonereads.tunasoft.com/scrollbox_js/ -dave --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Hi Dave! Dave Grijalva <grijalva-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> I cranked out a library for making prototype based (custom styled) > scrollbars over the weekend. If anybody has some time, I''d love some > feedback on it: > > http://theblogthatnoonereads.tunasoft.com/scrollbox_js/+ Very nice! + Clean, understandable code. + Adds scroll-wheel Event support! Woot! ? Did you consider writing this as a Scriptaculous Effect? Seems like that would have made it simpler/smaller and/or easier-to-write. If so, did you run into problems with that approach, or did you just want to simplify the installation / # of dependencies? ? You mention that you were "continually disappointed by the quality of the available [js-based scrollbar] libraries". Which ones did you try, and what disappointed you about them? For instance, was the killer (missing) feature, for you, the scroll-wheel support? (I always miss keyboard navigation binding, myself in these widgets -- like, can I press down-arrow, page-down, home, end?) I always find it very helpful when someone documents all the other packages "out there" that they tried, what they saw as their strengths and weaknesses as, and cite the reasons they chose to write their own instead. It helps me evaluate the univalves of options (in areas where there are many similar or related projects), see if I agree with the authors'' analyses and, sometimes, watch the fur fly :-) Anyway, thanks for this. and... Nice Work! I''m definitely taking it out for an extended test drive. -dave, threatening to send some patches for keyboard navigabilities --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Thanks for the feedback. I thought about using scriptaculous, but i decided against it in favor of not requiring another library. I looked at several different libraries, including some that the company I work for has purchased licenses to. What I generally found is that they all too often either don''t implement all the functionality of the built in scrollbar, don''t integrate easily into applications, are too difficult to customize, or pollute the namespace with too many globally exposed functions. What I see as a good library is one that works well, is simple to implement, and at least moderately easy to customize, in that order. As for missing features, I find that many/most of the libraries don''t handle named anchors very gracefully (I''m working on this presently for mine). Keyboard navigation is a great idea. I hadn''t thought of that one. -dave On 4/10/07, David Kaufman <david-8ZdJMhgJluNWk0Htik3J/w@public.gmane.org> wrote:> > > Hi Dave! > > Dave Grijalva <grijalva-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > I cranked out a library for making prototype based (custom styled) > > scrollbars over the weekend. If anybody has some time, I''d love some > > feedback on it: > > > > http://theblogthatnoonereads.tunasoft.com/scrollbox_js/ > > + Very nice! > > + Clean, understandable code. > > + Adds scroll-wheel Event support! Woot! > > ? Did you consider writing this as a Scriptaculous Effect? Seems like > that would have made it simpler/smaller and/or easier-to-write. If so, > did you run into problems with that approach, or did you just want to > simplify the installation / # of dependencies? > > ? You mention that you were "continually disappointed by the quality of > the available [js-based scrollbar] libraries". Which ones did you try, > and what disappointed you about them? > > For instance, was the killer (missing) feature, for you, the > scroll-wheel support? (I always miss keyboard navigation binding, > myself in these widgets -- like, can I press down-arrow, page-down, > home, end?) > > I always find it very helpful when someone documents all the other > packages "out there" that they tried, what they saw as their strengths > and weaknesses as, and cite the reasons they chose to write their own > instead. It helps me evaluate the univalves of options (in areas where > there are many similar or related projects), see if I agree with the > authors'' analyses and, sometimes, watch the fur fly :-) > > Anyway, thanks for this. and... Nice Work! I''m definitely taking it > out for an extended test drive. > > -dave, threatening to send some patches for keyboard navigabilities > > > > >--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Okay. I added keyboard navigation support as well as support for jumping to named anchors within the content div. -dave On 4/10/07, Dave Grijalva <grijalva-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> > Thanks for the feedback. > > I thought about using scriptaculous, but i decided against it in favor of > not requiring another library. > > I looked at several different libraries, including some that the company I > work for has purchased licenses to. What I generally found is that they all > too often either don''t implement all the functionality of the built in > scrollbar, don''t integrate easily into applications, are too difficult to > customize, or pollute the namespace with too many globally exposed > functions. > > What I see as a good library is one that works well, is simple to > implement, and at least moderately easy to customize, in that order. As for > missing features, I find that many/most of the libraries don''t handle named > anchors very gracefully (I''m working on this presently for mine). > > Keyboard navigation is a great idea. I hadn''t thought of that one. > > -dave > > On 4/10/07, David Kaufman < david-8ZdJMhgJluNWk0Htik3J/w@public.gmane.org> wrote: > > > > > > Hi Dave! > > > > Dave Grijalva < grijalva-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > I cranked out a library for making prototype based (custom styled) > > > scrollbars over the weekend. If anybody has some time, I''d love some > > > feedback on it: > > > > > > http://theblogthatnoonereads.tunasoft.com/scrollbox_js/ > > > > + Very nice! > > > > + Clean, understandable code. > > > > + Adds scroll-wheel Event support! Woot! > > > > ? Did you consider writing this as a Scriptaculous Effect? Seems like > > that would have made it simpler/smaller and/or easier-to-write. If so, > > did you run into problems with that approach, or did you just want to > > simplify the installation / # of dependencies? > > > > ? You mention that you were "continually disappointed by the quality of > > the available [js-based scrollbar] libraries". Which ones did you try, > > and what disappointed you about them? > > > > For instance, was the killer (missing) feature, for you, the > > scroll-wheel support? (I always miss keyboard navigation binding, > > myself in these widgets -- like, can I press down-arrow, page-down, > > home, end?) > > > > I always find it very helpful when someone documents all the other > > packages "out there" that they tried, what they saw as their strengths > > and weaknesses as, and cite the reasons they chose to write their own > > instead. It helps me evaluate the univalves of options (in areas where > > there are many similar or related projects), see if I agree with the > > authors'' analyses and, sometimes, watch the fur fly :-) > > > > Anyway, thanks for this. and... Nice Work! I''m definitely taking it > > out for an extended test drive. > > > > -dave, threatening to send some patches for keyboard navigabilities > > > > > > > > > > >--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
I got a new revision up over the weekend. It''s basically feature complete. -dave On 4/10/07, Dave Grijalva <grijalva-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> > Okay. I added keyboard navigation support as well as support for jumping > to named anchors within the content div. > > -dave > > On 4/10/07, Dave Grijalva <grijalva-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > Thanks for the feedback. > > > > I thought about using scriptaculous, but i decided against it in favor > > of not requiring another library. > > > > I looked at several different libraries, including some that the company > > I work for has purchased licenses to. What I generally found is that they > > all too often either don''t implement all the functionality of the built in > > scrollbar, don''t integrate easily into applications, are too difficult to > > customize, or pollute the namespace with too many globally exposed > > functions. > > > > What I see as a good library is one that works well, is simple to > > implement, and at least moderately easy to customize, in that order. As for > > missing features, I find that many/most of the libraries don''t handle named > > anchors very gracefully (I''m working on this presently for mine). > > > > Keyboard navigation is a great idea. I hadn''t thought of that one. > > > > -dave > > > > On 4/10/07, David Kaufman < david-8ZdJMhgJluNWk0Htik3J/w@public.gmane.org> wrote: > > > > > > > > > Hi Dave! > > > > > > Dave Grijalva < grijalva-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > I cranked out a library for making prototype based (custom styled) > > > > scrollbars over the weekend. If anybody has some time, I''d love > > > some > > > > feedback on it: > > > > > > > > http://theblogthatnoonereads.tunasoft.com/scrollbox_js/ > > > > > > + Very nice! > > > > > > + Clean, understandable code. > > > > > > + Adds scroll-wheel Event support! Woot! > > > > > > ? Did you consider writing this as a Scriptaculous Effect? Seems like > > > that would have made it simpler/smaller and/or easier-to-write. If > > > so, > > > did you run into problems with that approach, or did you just want to > > > simplify the installation / # of dependencies? > > > > > > ? You mention that you were "continually disappointed by the quality > > > of > > > the available [js-based scrollbar] libraries". Which ones did you > > > try, > > > and what disappointed you about them? > > > > > > For instance, was the killer (missing) feature, for you, the > > > scroll-wheel support? (I always miss keyboard navigation binding, > > > myself in these widgets -- like, can I press down-arrow, page-down, > > > home, end?) > > > > > > I always find it very helpful when someone documents all the other > > > packages "out there" that they tried, what they saw as their strengths > > > and weaknesses as, and cite the reasons they chose to write their own > > > instead. It helps me evaluate the univalves of options (in areas > > > where > > > there are many similar or related projects), see if I agree with the > > > authors'' analyses and, sometimes, watch the fur fly :-) > > > > > > Anyway, thanks for this. and... Nice Work! I''m definitely taking it > > > out for an extended test drive. > > > > > > -dave, threatening to send some patches for keyboard navigabilities > > > > > > > > > > > > > > > > > >--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
ajevans85-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org
2007-Apr-20 16:35 UTC
Re: Scrolling Box Widget
Hiya, thanks for this code it has come in usefull.
I''m new to javascript and seem to be having some trouble trying to
find a bug in your script.
I''ve added tow functions extending what you already have:
addUpHandle: function(element){
Event.observe(element, ''mouseover'',
function(e){this.buttonDown(e,
this.scrollUp.bind(this));}.bindAsEventListener(this));
Event.observe(element, ''mouseout'',
this.buttonUp.bindAsEventListener(this));
Event.observe(element, ''mousedown'',
function(e){this.buttonDown(e,
this.scrollUp.bind(this));}.bindAsEventListener(this));
Event.observe(element, ''mouseup'',
this.buttonUp.bindAsEventListener(this));
}
addDownHandle: function(element){
Event.observe(element, ''mousedown'',
function(e){this.buttonDown(e,
this.scrollDown.bind(this));}.bindAsEventListener(this));
Event.observe(element, ''mouseup'',
this.buttonUp.bindAsEventListener(this));
Event.observe(element, ''mouseover'',
function(e){this.buttonDown(e,
this.scrollDown.bind(this));}.bindAsEventListener(this));
Event.observe(element, ''mouseout'',
this.buttonUp.bindAsEventListener(this));
}
This allows me to hide the scroll bar by not including the relevent
css, and attach two up and down buttons ie <div id=upButton>Up</div>
.
I also use css to style the button. This all works fine :)
My problem is the scrollbox scrolls a unsorted list of links acting as
a menu. When I click these links the page will not load. Firebug
throws no errors. If I aad a onclick="alert(''test'')"
event to the
links though an alert box is shown.
Do you have any ideas what could be causing this problem?
It seems the links in the left box of your demo also have the same
problem. I have tested this both in IE6 and Firefox 2.0.0.3
Thanks
Adam
On Apr 17, 6:33 pm, "Dave Grijalva"
<grija...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:> I got a new revision up over the weekend. It''s basically feature
complete.
>
> -dave
>
> On 4/10/07, Dave Grijalva
<grija...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
>
>
> > Okay. I added keyboard navigation support as well as support for
jumping
> > to named anchors within the content div.
>
> > -dave
>
> > On 4/10/07, Dave Grijalva
<grija...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> > > Thanks for the feedback.
>
> > > I thought about using scriptaculous, but i decided against it in
favor
> > > of not requiring another library.
>
> > > I looked at several different libraries, including some that the
company
> > > I work for has purchased licenses to. What I generally found is
that they
> > > all too often either don''t implement all the
functionality of the built in
> > > scrollbar, don''t integrate easily into applications, are
too difficult to
> > > customize, or pollute the namespace with too many globally
exposed
> > > functions.
>
> > > What I see as a good library is one that works well, is simple to
> > > implement, and at least moderately easy to customize, in that
order. As for
> > > missing features, I find that many/most of the libraries
don''t handle named
> > > anchors very gracefully (I''m working on this presently
for mine).
>
> > > Keyboard navigation is a great idea. I hadn''t thought
of that one.
>
> > > -dave
>
> > > On 4/10/07, David Kaufman <
d...-8ZdJMhgJluNWk0Htik3J/w@public.gmane.org> wrote:
>
> > > > Hi Dave!
>
> > > > Dave Grijalva <
grija...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> > > > > I cranked out a library for making prototype based
(custom styled)
> > > > > scrollbars over the weekend. If anybody has some time,
I''d love
> > > > some
> > > > > feedback on it:
>
> > > > >http://theblogthatnoonereads.tunasoft.com/scrollbox_js/
>
> > > > + Very nice!
>
> > > > + Clean, understandable code.
>
> > > > + Adds scroll-wheel Event support! Woot!
>
> > > > ? Did you consider writing this as a Scriptaculous Effect?
Seems like
> > > > that would have made it simpler/smaller and/or
easier-to-write. If
> > > > so,
> > > > did you run into problems with that approach, or did you
just want to
> > > > simplify the installation / # of dependencies?
>
> > > > ? You mention that you were "continually disappointed
by the quality
> > > > of
> > > > the available [js-based scrollbar] libraries". Which
ones did you
> > > > try,
> > > > and what disappointed you about them?
>
> > > > For instance, was the killer (missing) feature, for you, the
> > > > scroll-wheel support? (I always miss keyboard navigation
binding,
> > > > myself in these widgets -- like, can I press down-arrow,
page-down,
> > > > home, end?)
>
> > > > I always find it very helpful when someone documents all the
other
> > > > packages "out there" that they tried, what they
saw as their strengths
> > > > and weaknesses as, and cite the reasons they chose to write
their own
> > > > instead. It helps me evaluate the univalves of options (in
areas
> > > > where
> > > > there are many similar or related projects), see if I agree
with the
> > > > authors'' analyses and, sometimes, watch the fur fly
:-)
>
> > > > Anyway, thanks for this. and... Nice Work! I''m
definitely taking it
> > > > out for an extended test drive.
>
> > > > -dave, threatening to send some patches for keyboard
navigabilities
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
I''ll look into the issue as soon as i have a chance. I have noticed that the behavior of named anchor links within the content is a bit erratic. To your first point, you should be able to use just two buttons without the bar or handle using just css. just set the handle to display:none and set the background of the handle to transparent. If you want the up/down buttons to be next to eachother, set the size of the scrollbar to the combined height of the buttons. You can also absolutely position the scrollbar just about anywhere at that point. -dave On Apr 20, 9:35 am, "ajevan...-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org" <ajevan...-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org> wrote:> Hiya, thanks for this code it has come in usefull. > > I''m new to javascript and seem to be having some trouble trying to > find a bug in your script. > > I''ve added tow functions extending what you already have: > > addUpHandle: function(element){ > Event.observe(element, ''mouseover'', function(e){this.buttonDown(e, > this.scrollUp.bind(this));}.bindAsEventListener(this)); > Event.observe(element, ''mouseout'', > this.buttonUp.bindAsEventListener(this)); > Event.observe(element, ''mousedown'', function(e){this.buttonDown(e, > this.scrollUp.bind(this));}.bindAsEventListener(this)); > Event.observe(element, ''mouseup'', > this.buttonUp.bindAsEventListener(this)); > } > > addDownHandle: function(element){ > Event.observe(element, ''mousedown'', function(e){this.buttonDown(e, > this.scrollDown.bind(this));}.bindAsEventListener(this)); > Event.observe(element, ''mouseup'', > this.buttonUp.bindAsEventListener(this)); > Event.observe(element, ''mouseover'', function(e){this.buttonDown(e, > this.scrollDown.bind(this));}.bindAsEventListener(this)); > Event.observe(element, ''mouseout'', > this.buttonUp.bindAsEventListener(this)); > } > > This allows me to hide the scroll bar by not including the relevent > css, and attach two up and down buttons ie <div id=upButton>Up</div> . > I also use css to style the button. This all works fine :) > > My problem is the scrollbox scrolls a unsorted list of links acting as > a menu. When I click these links the page will not load. Firebug > throws no errors. If I aad a onclick="alert(''test'')" event to the > links though an alert box is shown. > > Do you have any ideas what could be causing this problem? > > It seems the links in the left box of your demo also have the same > problem. I have tested this both in IE6 and Firefox 2.0.0.3 > > Thanks > > Adam > > On Apr 17, 6:33 pm, "Dave Grijalva" <grija...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > I got a new revision up over the weekend. It''s basically feature complete. > > > -dave > > > On 4/10/07, Dave Grijalva <grija...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > Okay. I added keyboard navigation support as well as support for jumping > > > to named anchors within the content div. > > > > -dave > > > > On 4/10/07, Dave Grijalva <grija...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > > Thanks for the feedback. > > > > > I thought about using scriptaculous, but i decided against it in favor > > > > of not requiring another library. > > > > > I looked at several different libraries, including some that the company > > > > I work for has purchased licenses to. What I generally found is that they > > > > all too often either don''t implement all the functionality of the built in > > > > scrollbar, don''t integrate easily into applications, are too difficult to > > > > customize, or pollute the namespace with too many globally exposed > > > > functions. > > > > > What I see as a good library is one that works well, is simple to > > > > implement, and at least moderately easy to customize, in that order. As for > > > > missing features, I find that many/most of the libraries don''t handle named > > > > anchors very gracefully (I''m working on this presently for mine). > > > > > Keyboard navigation is a great idea. I hadn''t thought of that one. > > > > > -dave > > > > > On 4/10/07, David Kaufman < d...-8ZdJMhgJluNWk0Htik3J/w@public.gmane.org> wrote: > > > > > > Hi Dave! > > > > > > Dave Grijalva < grija...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > > > I cranked out a library for making prototype based (custom styled) > > > > > > scrollbars over the weekend. If anybody has some time, I''d love > > > > > some > > > > > > feedback on it: > > > > > > >http://theblogthatnoonereads.tunasoft.com/scrollbox_js/ > > > > > > + Very nice! > > > > > > + Clean, understandable code. > > > > > > + Adds scroll-wheel Event support! Woot! > > > > > > ? Did you consider writing this as a Scriptaculous Effect? Seems like > > > > > that would have made it simpler/smaller and/or easier-to-write. If > > > > > so, > > > > > did you run into problems with that approach, or did you just want to > > > > > simplify the installation / # of dependencies? > > > > > > ? You mention that you were "continually disappointed by the quality > > > > > of > > > > > the available [js-based scrollbar] libraries". Which ones did you > > > > > try, > > > > > and what disappointed you about them? > > > > > > For instance, was the killer (missing) feature, for you, the > > > > > scroll-wheel support? (I always miss keyboard navigation binding, > > > > > myself in these widgets -- like, can I press down-arrow, page-down, > > > > > home, end?) > > > > > > I always find it very helpful when someone documents all the other > > > > > packages "out there" that they tried, what they saw as their strengths > > > > > and weaknesses as, and cite the reasons they chose to write their own > > > > > instead. It helps me evaluate the univalves of options (in areas > > > > > where > > > > > there are many similar or related projects), see if I agree with the > > > > > authors'' analyses and, sometimes, watch the fur fly :-) > > > > > > Anyway, thanks for this. and... Nice Work! I''m definitely taking it > > > > > out for an extended test drive. > > > > > > -dave, threatening to send some patches for keyboard navigabilities--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
also, my next version will automatically add class names for hover and down states on the buttons and handle. -dave On Apr 20, 9:35 am, "ajevan...-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org" <ajevan...-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org> wrote:> Hiya, thanks for this code it has come in usefull. > > I''m new to javascript and seem to be having some trouble trying to > find a bug in your script. > > I''ve added tow functions extending what you already have: > > addUpHandle: function(element){ > Event.observe(element, ''mouseover'', function(e){this.buttonDown(e, > this.scrollUp.bind(this));}.bindAsEventListener(this)); > Event.observe(element, ''mouseout'', > this.buttonUp.bindAsEventListener(this)); > Event.observe(element, ''mousedown'', function(e){this.buttonDown(e, > this.scrollUp.bind(this));}.bindAsEventListener(this)); > Event.observe(element, ''mouseup'', > this.buttonUp.bindAsEventListener(this)); > } > > addDownHandle: function(element){ > Event.observe(element, ''mousedown'', function(e){this.buttonDown(e, > this.scrollDown.bind(this));}.bindAsEventListener(this)); > Event.observe(element, ''mouseup'', > this.buttonUp.bindAsEventListener(this)); > Event.observe(element, ''mouseover'', function(e){this.buttonDown(e, > this.scrollDown.bind(this));}.bindAsEventListener(this)); > Event.observe(element, ''mouseout'', > this.buttonUp.bindAsEventListener(this)); > } > > This allows me to hide the scroll bar by not including the relevent > css, and attach two up and down buttons ie <div id=upButton>Up</div> . > I also use css to style the button. This all works fine :) > > My problem is the scrollbox scrolls a unsorted list of links acting as > a menu. When I click these links the page will not load. Firebug > throws no errors. If I aad a onclick="alert(''test'')" event to the > links though an alert box is shown. > > Do you have any ideas what could be causing this problem? > > It seems the links in the left box of your demo also have the same > problem. I have tested this both in IE6 and Firefox 2.0.0.3 > > Thanks > > Adam > > On Apr 17, 6:33 pm, "Dave Grijalva" <grija...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > I got a new revision up over the weekend. It''s basically feature complete. > > > -dave > > > On 4/10/07, Dave Grijalva <grija...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > Okay. I added keyboard navigation support as well as support for jumping > > > to named anchors within the content div. > > > > -dave > > > > On 4/10/07, Dave Grijalva <grija...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > > Thanks for the feedback. > > > > > I thought about using scriptaculous, but i decided against it in favor > > > > of not requiring another library. > > > > > I looked at several different libraries, including some that the company > > > > I work for has purchased licenses to. What I generally found is that they > > > > all too often either don''t implement all the functionality of the built in > > > > scrollbar, don''t integrate easily into applications, are too difficult to > > > > customize, or pollute the namespace with too many globally exposed > > > > functions. > > > > > What I see as a good library is one that works well, is simple to > > > > implement, and at least moderately easy to customize, in that order. As for > > > > missing features, I find that many/most of the libraries don''t handle named > > > > anchors very gracefully (I''m working on this presently for mine). > > > > > Keyboard navigation is a great idea. I hadn''t thought of that one. > > > > > -dave > > > > > On 4/10/07, David Kaufman < d...-8ZdJMhgJluNWk0Htik3J/w@public.gmane.org> wrote: > > > > > > Hi Dave! > > > > > > Dave Grijalva < grija...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > > > I cranked out a library for making prototype based (custom styled) > > > > > > scrollbars over the weekend. If anybody has some time, I''d love > > > > > some > > > > > > feedback on it: > > > > > > >http://theblogthatnoonereads.tunasoft.com/scrollbox_js/ > > > > > > + Very nice! > > > > > > + Clean, understandable code. > > > > > > + Adds scroll-wheel Event support! Woot! > > > > > > ? Did you consider writing this as a Scriptaculous Effect? Seems like > > > > > that would have made it simpler/smaller and/or easier-to-write. If > > > > > so, > > > > > did you run into problems with that approach, or did you just want to > > > > > simplify the installation / # of dependencies? > > > > > > ? You mention that you were "continually disappointed by the quality > > > > > of > > > > > the available [js-based scrollbar] libraries". Which ones did you > > > > > try, > > > > > and what disappointed you about them? > > > > > > For instance, was the killer (missing) feature, for you, the > > > > > scroll-wheel support? (I always miss keyboard navigation binding, > > > > > myself in these widgets -- like, can I press down-arrow, page-down, > > > > > home, end?) > > > > > > I always find it very helpful when someone documents all the other > > > > > packages "out there" that they tried, what they saw as their strengths > > > > > and weaknesses as, and cite the reasons they chose to write their own > > > > > instead. It helps me evaluate the univalves of options (in areas > > > > > where > > > > > there are many similar or related projects), see if I agree with the > > > > > authors'' analyses and, sometimes, watch the fur fly :-) > > > > > > Anyway, thanks for this. and... Nice Work! I''m definitely taking it > > > > > out for an extended test drive. > > > > > > -dave, threatening to send some patches for keyboard navigabilities--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---