Soma

jQuery UI Range Slider Fieldtype

Recommended Posts

Before we can repeat, we can slide! :)

ProcessWire2+ RangeSlider Fieldtype

This fieldtype let's you create slider input fields in the admin using the built in jQuery UI Slider. You can use it as a regular

single value slider, or enable "Range" setting under details of the field edit screen, which gives you two number.

In the front-end templates you can use the field as follows:

If used as single value slider

	echo $page->fieldname

If ranged slider is enabled

echo $page->fieldname->min
echo $page->fieldname->max

Use in selectors strings

With a regular single value slider

	$pages->find("range=120");

If range slider is enabled

	$pages->find("range.min>=100, range.max<120");

post-100-0-73766900-1329543474_thumb.png

It comes with various settings.

-------------------------------------------------------------------

- range enable

- width of slider (%)

- default value

- min value

- max value

- step

- prefix for displayed value(s)

- suffix for displayed value(s)

Download

-------------------------------------------------------------------

You can download the Module from Github.

https://github.com/s...nic/RangeSlider

How to install

-------------------------------------------------------------------

1. Download and place the RangeSlider folder in: /site/modules/

2. In the admin control panel, go to Modules. At the bottom/top of the

screen, click the "Check for New Modules" button.

3. Now scroll to the RangeSlider Fieldtype module and click "Install".

4. Create a new Field with the new "RangeSlider" Fieldtype. Once saved

you can configure the fieldtype, with various options under "Details" tab.

I have made some testing, and installed on different PW installs. But if you find any issue, I'd like to hear.

Have fun!

  • Like 2

Share this post


Link to post
Share on other sites

Thanks, Soma! Looks pretty cool. I'll test it as soon as possible.

Share this post


Link to post
Share on other sites

Soma, that's a nice one!

Maybe a possibility to optionally define a function for calculating value range to make the value grow non-linearly as you slide could be a nice enhancement.

Could be handled like custom API calls for page ref fields, a field for js code like "return Math.pow({$x})". But that's just an idea.

Share this post


Link to post
Share on other sites

Thanks guys! Glad you like it.

Soma, that's a nice one!

Maybe a possibility to optionally define a function for calculating value range to make the value grow non-linearly as you slide could be a nice enhancement.

Could be handled like custom API calls for page ref fields, a field for js code like "return Math.pow({$x})". But that's just an idea.

Thanks for the idea. Not sure where this could be useful though. But something with a "code" field would be possible.

I'm more thinking something to be able to do floats. This could be done with formatter function too. So you could specify digits precision and have 0-1000 would really mean 0-10.00 - but operations like this could be done on output too.

Also there's still some other settings that might be useful but these are more visual than functional. I'll add 1-2 more for type max,min for regular slider.

Share this post


Link to post
Share on other sites

Well I realized it still isn't as good as I wanted. It has still a text field for storing data. And the fact that it can used as one value and two value range makes it hard to implement with only 1 integer table field. I'm not sure how it would be possible to have 2 integer fields on a fieldtype. So this current version doesn't work with selectors. Would it be possible to have selector like "range[0]>100, range[1]<120" ? I don't understand how selectors works exactly.

Simplest would be for doing ranges is having two single value slider with real integer field type. But I think it's not as ideal. So i'm kinda stuck here and little overwhelmed with how this else could be implemented better.

Edit:

I think I'm on a path that works. Even with page selectors. I'm doing a little more testing and experimenting.

Actually I'm diving a little more int PW's implementation of fieldtypes and how it works.

So it works now like "range.data>100, range.data2<120", and output is array like before $page->range["data"].

Will hopefully get it working soon and update the repo.

Share this post


Link to post
Share on other sites

Soma great module!! It should be no problem to make your Fieldtype support two integers. Take a look at the FieldtypeMapMarker module for an example of how to have multiple fields in the module. To start you are going to want to have a DB schema something like this:

public function getDatabaseSchema(Field $field) {
   $schema = parent::getDatabaseSchema($field);
   $schema['data'] = 'int NOT NULL default 0'; // min
   $schema['data_max'] = 'int NOT NULL default 0'; // max
   $schema['keys']['data'] = 'KEY data(data, data_max)';
   $schema['keys']['data_max'] = 'KEY data(data_max)';
   return $schema;
}

Basically, use the required 'data' column for one of your pieces of data, and then you can add any other columns you want. I called it 'data_max' here, but you could call it whatever you want.

Share this post


Link to post
Share on other sites

I was just thinking the other day that it would be great to have a fieldtype like this for when an integer field always falls within a predictable range. This is even better!

One suggestion: How about having the number display editable, in case there is a specific number you need to enter (and there's a large range that might be difficult to hit with the slider)?

Share this post


Link to post
Share on other sites

I've reworked the whole module to use integer fields and it works a little different now.

Best of it is, it now works in selectors and uses real integers. :)

I have updated the repo on github just now and also the first post to reflect the changes.

If you installed it already you should first uninstall it before updating.

Share this post


Link to post
Share on other sites

Is this using standard jQuery UI skinning?

Good work neverthless.

Yes this is using jQuery UI skinning. Thanks!

Share this post


Link to post
Share on other sites

I was just thinking the other day that it would be great to have a fieldtype like this for when an integer field always falls within a predictable range. This is even better!

Or you can even use it to set states. For example use it like an option 1,2,3

One suggestion: How about having the number display editable, in case there is a specific number you need to enter (and there's a large range that might be difficult to hit with the slider)?

This would be possible, but then why have a slider? :P This also would require to implement some validation through js or the module.

I suggest, if you have large numbers you can put it in the near and use arrow keys to get to the value you want.

EDIT: Just found that there seems to be a bug with the left range handle not able to move with keyboard arrow keys. I found out that the current jquery 1.6.2 core included in PW is the reason. I copied in latest jquery 1.7.1 and it starts working.

Share this post


Link to post
Share on other sites

Great work Soma! I'm really liking this fieldtype. I wanted to mention one potential improvement that would be easy to make. Rather than having to use the technical sounding range.data and range.data_max in selectors, wouldn't it be nice if you could use range.min and range.max? If you want to do that, add this to your Fieldtype:

public function getMatchQuery($query, $table, $subfield, $operator, $value) {
   if($subfield == 'min') $subfield = 'data';
   if($subfield == 'max') $subfield = 'data_max';
   return parent::getMatchQuery($query, $table, $subfield, $operator, $value); 
}
  • Like 1

Share this post


Link to post
Share on other sites

Thanks Ryan! Glad you like it.

Wow thanks, did you read my mind? I was about to look for this particular function to see if there's a way to map those. Thanks for pointing out!

I'll quickly put it in and update the repo.

Edit: Just updated the fieldtype, tested and pushed to github.

Now we can use range.min, range.max in selectors!

Share this post


Link to post
Share on other sites

Thanks a lot Soma! I detected a bug in this last iteration, while trying to use it, on line 81 of InputfieldRangeSlider.module:

  $display = "$( '#RangeSlider_{$this->name}_display1' ).text( '$this->prefix' + ui.value + '$this->suffix');";

  $constrain = "$( '#Inputfield_{$this->name}1' ).val( ui.value );"	   // !!! there is a semicolon missing here
  // for change event checks
  $constrain .= "$( '#Inputfield_{$this->name}1' ).trigger( 'change' );";

When I added the semicolon, everything started working again!

PS: I'm fairly new to web coding and communities, is there a place where I could have posted this bug? (in the Git, or something like that?)

Cheers :)

Share this post


Link to post
Share on other sites

Thanks tiagoroldao, nice catch! Seems as not much are using it yet, otherwise someone would have run into this. Though it worked with range enabled. :)

Well, you can always open new issue on github repo. It's public. https://github.com/somatonic/RangeSlider/issues

It's fixed and commited. I also improved the module install. You only need to install the FieldtypeRangeSlider and the InputfieldRangeSlider will be installed and deinstalled automaticly. If you already have it installed it's safe to just replace with the new files.

Share this post


Link to post
Share on other sites

I wonder if this was only a browser-specific issue anyway? I know IE goes crazy when you miss out semicolons, but in other cases other browsers are fine with it.

Share this post


Link to post
Share on other sites

Nope Peteee, it wasn't working when using single value slider, a missing semicolon will break javascript if it's not the last line :)

Share this post


Link to post
Share on other sites

Hi Soma, Thanks for the module! I've been testing the slider and was wondering if it's possible to make 0.5 (half) increments. It would be nice to have a score Range field and let the user select between 1-5 and half increments (4.5 stars).

Share this post


Link to post
Share on other sites

You're welcome landitus. Unfortunately this seems not possible as I know, it is using the jquery UI slider and there's only numbers not floats supported.

You could then maybe use 1-10 and divide them by 2?

Or you could use page field and create 10 pages with the increments and then use them to select. If the range is never gonna change this might be a option too.

Share this post


Link to post
Share on other sites

Hey there, nice module. I'm using it for percentages to set fluid sizes and such.

I ran into a small issue, it seems like it always ignores the default value - i can't get it to be 100% as default, for example

thanks for any input!

Share this post


Link to post
Share on other sites

Thanks joe_g for mention it.

I just updated the module and fixed the issue with the default value.

Share this post


Link to post
Share on other sites

Just committed another update.

I made sure the default value (if any defined) is also being returned by the API even if the page is not yet saved and there's no range value in the Database.

Share this post


Link to post
Share on other sites

Hi, I want use this with PW 2.4.+ in a Modules-Configpage. Is this possible?

    EDIT: yes it is possible! :)

I have tried the following code but I do something wrong, the slider isn't displayed in the config page:

    EDIT: The settings for minValue, maxValue etc. belongs to the $field, not to the $slider. This was what I have done initially wrong

            $field = $modules->get("InputfieldRangeSlider");
            if(!empty($field) && class_exists('RangeSlider')) {
	            $field->attr('name', 'integer');
                        $slider = new RangeSlider();
                    $field->attr('value', $slider);
                    $field->width = 90;
                    $field->minValue = 1;
                    $field->maxValue = 100;
                    $field->defaultValue = $data['integer']>0 && $data['integer']<=100 ? $data['integer'] : 50;
                    $field->step = 1;
	            $field->label = 'Test with integer value';
	            $fieldset->add($field);
            } else {
            ...

The only thing what is not working is the $field->defaultValue, - what I'm doing wrong here?

Edited by horst

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By BitPoet
      I'm really in love with FormBuilder, but the one thing missing to match all my end users' expectations were repeatable field groups. Think repeaters, in ProcessWire terms. Our primary application of PW is our corporate intranet, so "lines" of fields are quite common in the forms I build. We have all kinds of request forms where the information for a varying number of colleagues needs to be entered (from meal order to flight booking request) and where it is simply impractical to send a form for each, and I don't want to clutter my forms with multiple instances of fields that may only get used ten percent of the time.
      That's why I started to build FormBuilderMultiplier (link to GitHub).
      What it does:
      Adds an option to make a regular Fieldgroup repeatable Lets you limit the number of instances of a Fieldgroup on the form Adds an "Add row" button the form that adds another instance of the Fieldgroup's fields Adds a counter suffix at the end of every affected field's label Stores the entered values just like regular fields Makes the entered values available in preview and email notifications Supports most text based fields, textareas and selects (really, I haven't had enough time to test all the available choices yet) What it doesn't do (yet):
      Support saving to ProcessWire pages (i.e. real Repeaters) I haven't tested all the validation stuff, Date/Time inputs etc. yet, but since I'm utterly swamped with other stuff at work, I didn't want to wait until I have it polished. Any feedback is welcome. There might also be some issues with different output frameworks that I haven't encountered yet. The forms I work with mostly use UIKit.
      Status:
      Still alpha, so test well before using it in the field.
      Known issues:
      When rows are added, the form's iframe needs to be resized, which isn't completely clean yet.
      How it works:
      The Fieldgroup settings are added through regular hooks, as is the logic that adds the necessary field copies for processing the form and displaying previews.
      "Multiplied" field instances are suffixed with _NUM, where NUM is an incremental integer starting from 1. So if you have add two fields named "surname" and "givenname" to a fieldgroup and check the "multiply" checkbox, the form will initially have "surname_1" and "givenname_1" field (I'm still considering changing that to make the risk to shoot oneself into the foot by having a regular "surname_1" field somewhere else in the form less likely).
      When a "row" is added, the first row is cloned through JS and the counter in the fields' IDs, names and "for" attributes as well as the counter in the label are incremented before appending the copies to the Fieldset container in the form.
      To keep backend and frontend in sync, a hidden field named [name of the fieldset]__multiplier_rows is added to the form. Both the backend and the frontend script use this to store and retrieve the number of "rows".
      ToDo:
      Naturally, add the option to store the data in real repeaters when saving to pages. Do a lot of testing (and likely fixing). Make a few things (like the "Add row" button label etc.) configurable in field(set) context. Add a smooth API to retrieve the multiplied values as WireArrays. The mandatory moving screenshot:

    • By MoritzLost
      Hello there,
      I'm working on a tiny textformatter module that searches the text for titles of other pages on your site and creates hyperlinks to them. I'm not sure if something like this exists already, but I haven't found anything in the module directory, so I wrote my own solution 🙂
      It's not properly tested yet and is still missing some functionality I would like to implement, so at the moment it should be considered in BETA. Features include limiting the pages that will get searched by template, and adding a custom CSS class to the generated hyperlinks. As I'm writing this I noticed that it will probably include unpublished and hidden pages at the moment, so yeah ... it's still in development alright 😅
      You can download the module from Github:
      https://github.com/MoritzLost/TextformatterPageTitleLinks
      There's some more information in the readme as well.
      Anyway, let me know what you think! I'm happy about any feedback, possible improvements or ideas on how to improve the module. Cheers.
    • By adrian
      This module provides a way to rapidly generate Page fields and the required templates and pages for use as a drop down select (or any other Page field type).
      This module will let you create a full page field setup in literally a few seconds 
      To use, run Page Field Select Creator from the Setup Menu
      Enter a Field Title, eg: Room Types Select Options - These will become the child pages that will populate the page field select options. There are two different options.
       
      Option 1. TITLE FIELD ONLY - enter one option per line, eg:
       
      Single
      Double
      Suite
       
       
      Option 2. MULTIPLE FIELDS - the first line is used for the field names and the first field must be 'Title'. Subsequent lines are the values for the fields, eg:
       
      Title, Number of Beds, Number of People, Kitchen Facilities
      Single, 1, 1, Fridge Only
      Double, 2, 2, Fridge Only
      Suite, 3, 6, Full Kitchen
        Choose the parent where the page tree of options will be created, eg a hidden "Options" parent page Select a "Deference in API as" option depending on your needs Choose the input field type Check whether "Allow new pages to be created from field?" should be enabled. As an example, if you entered "Room Types" as the field title, you would end up with all of the following automatically created:
      a fully configured page field called: room_types MULTIPLE FIELDS OPTION - 3 additional fields - number_of_beds, number_of_people, kitchen a parent template called: room_types a child template called: room_types_items (with either just a title field, or with the 3 additional fields as well) a parent page called: Room Types a series of child pages named and titled based on the per line entries in the Select Options textarea The templates are configured such that the "room_types_items" child template can only have the main "room_types" template as a parent, and vice versa.

      Then all you have to do is add the newly created page field to any template you want and you're ready to go!
       
      You can grab it from:
       
      Modules directory: http://modules.processwire.com/modules/process-page-field-select-creator/
      Github: https://github.com/adrianbj/ProcessPageFieldSelectCreator
       

    • By bernhard
      WHY?
      This module was built to fill the gap between simple $pages->find() operations and complex SQL queries.
      The problem with $pages->find() is that it loads all pages into memory and that can be a problem when querying multiple thousands of pages. Even $pages->findMany() loads all pages into memory and therefore is a lot slower than regular SQL.
      The problem with SQL on the other hand is, that the queries are quite complex to build. All fields are separate tables, some repeatable fields use multiple rows for their content that belong to only one single page, you always need to check for the page status (which is not necessary on regular find() operations and therefore nobody is used to that).
      In short: It is far too much work to efficiently and easily get an array of data based on PW pages and fields and I need that a lot for my RockGrid module to build all kinds of tabular data.

      Basic Usage

       
      Docs & Download
      https://modules.processwire.com/modules/rock-finder/
      https://github.com/BernhardBaumrock/RockFinder
       
      Changelog
      180817, v1.0.6, support for joining multiple finders 180810, v1.0.5, basic support for options fields 180528, v1.0.4, add custom select statement option 180516, change sql query method, bump version to 1.0.0 180515, multilang bugfix 180513, beta release <180513, preview/discussion took place here: https://processwire.com/talk/topic/18983-rocksqlfinder-highly-efficient-and-flexible-sql-finder-module/
    • By BitPoet
      MediaLibrary
      Update: MediaLibrary can now be found in the official module list.
      Out of necessity, I've started to implement a simple media library module.
      The basic mechanism is that it adds a MediaLibrary template with file and image fields. Pages of this type can be added anywhere in the page tree.
      The link and image pickers in CKEditor are extended to allow quick selection of library pages from dropdowns. In the link picker this happens in the MediaLibrary tab, where you can also see a preview of the selected image. In the image picker, simply select a library from the dropdown at the top, everything else is handled by standard functionality.
      I've put the code onto github. This module is compatible with ProcessWire 3.
      Steps to usage:
      Download the module's zip from github (switch to the pw3 branche beforehand if you want to test on PW 3.x) and unpack it into site/modules Click "Modules" -> "Refresh" in the admin Click "Install" for MediaLibrary For testing, create a page with the MediaLibrary template under home (give it an expressive title like 'Global Media') and add some images and files Edit a differnt page with a CKEditor field and add a link and an image to see the MediaLibrary features in action (see the screencap for details) Optionally, go into the module settings for MediaLibrary Note: this module is far from being as elaborate as Kongondo's Media Manager (and doesn't plan to be). If you need a feature-rich solution for integrated media management, give it a look.
      Feel free to change the settings for MediaFiles and MediaImages fields, just keep the type as multiple.
      There are some not-so-pretty hacks for creating and inserting the correct markup, which could probably be changed to use standard input fields, though I'm a bit at a loss right now how to get it to work. I've also still got to take a look at error handling before I can call it fit for production. All feedback and pointers are appreciated (that's also why I post this in the development section).

      Edit 09.03.2016 / version 0.0.4: there's now also a "Media" admin page with a shortcut to quickly add a new library.

      Edit 01.05.2016:
      Version 0.0.8:
      - The module now supports nested media libraries (all descendants of eligible media libraries are also selectable in link/image picker).
      - There's a MediaLibrary::getPageMediaLibraries method you can hook after to modify the array of available libraries.
      - You can switch between (default) select dropdowns or radio boxes in the module configuration of MediaLIbrary to choose libraries.
      Edit 10.10.2018:
      Version 0.1.3:
      - Dropped compatibility for ProcessWire legacy versions by adding namespaces
      - Allow deletion of libraries from the Media overview admin page
      - Added an option to hide media libraries from the page tree (optionally also for superusers)