sliderfield

Attached is a screenshot of the widget.

Thanks rogical, it certainly could work with selects where the index of the selected item is based on the slider value. I will definitely put that on the planned feature list, but first I would like to knock out range support since I've seen that requested a few times.

As part of the review process I discovered I'm supposed to do some research and post about the different modules which may already do something similar.

There are two similar modules in existence:

1. http://drupal.org/project/cck_slider
   This project is 6.x only. Does not support decimal or float input. Does not support prefixes/suffices (such as ", $, %, MM, etc.). Another fundamental difference is that cck_slider does NOT use the core number field widget form, instead it builds its own.
2. http://drupal.org/project/slider_textfield Also 6.x only, slider_textfield is another one that has the exact same limitations as cck_slider. In fact, their code is almost identical except that slider_textfield uses a process callback to add its extra HTML markup. slider_textfield also does not allow negative values. slider_textfield also does not support step. No commits for over 2 years.

Notable Differences:

• I don't add any markup to the number field, only a class. This makes fallback (javascript disabled) slightly more graceful. BOTH slider_textfield and cck_slider add markup.
• Because I use the core number widget form here:$element += number_field_widget_form($form, $form_state, $field, $instance, $langcode, $items, $delta, $element);, it should be more resilient to changes and updates to core field modules if they happen to change, add a setting, etc. (source: sliderfield.module line 28). The sliderfield module simply adds a process callback which provides settings and attaches the javascript.
• The decimal field is integral to my use case. Having a 0.5 step on a 1 to 10 slider is a very important feature.
• Both cck_slider and slider_textfield have randomly set defaults for min/max. slider_textfield has set it to 0-600. Why 600? I have no idea. cck_slider uses a slightly more logical 0-100. Rather than make assumptions, I simply altered the number settings form to require them.
• The other difference is that I plan to expand sliderfield to have its own range field type (so it's not simply a widget) and as Rogical suggested, slider widget for select boxes. I do NOT plan to have a 6.x release.
• Because this module was developed for D7, it has no dependencies outside of core (field, number). Both D6 modules require jQuery update and jQuery UI modules making installation cumbersome.

Thanks for the review klausi, renaming to sliderfield_process doesn't work because it tries to implement hook_process. I'll ask the module dev IRC folks for help on that.

I granted the request for mrfelton to be a co-maintainer. Thanks!

Changing the status because this module is now a full project. Or should I just mark it as closed? I noticed I don't have the permission to promote full projects, is that something done through this queue? Project: http://www.drupal.org/project/sliderfield

Neither of those do what sliderfield does. Sliderfield is a single input with a slider. The output is a single number.

1. The first one, elements simply makes use of native fields, i.e. HTML5.
2. The second one stores two values, basically a differential. Moving the slider reduces one value and increases the other, it's a "transfer" slider... actually I think it's an entire new field type.

Thanks Klausi, will do.