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 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://gitlab.com/baumrock/RockFinder/tree/master
       
      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 OLSA
      Hello for all,
      ConfigurationForm fieldtype module is one my experiment from 2016.
      Main target to build this module was to store multiple setup and configuration values in just 1 field and avoid to use 1 db table to store just single "number of items on page", or another db table to store "layout type" etc. Thanks to JSON formatted storage this module can help you to reduce number of PW native fields in project, save DB space, and reduce number of queries at front-end.
      Install and setup:
      Download (at the bottom ), unzip and install like any other PW module (site/modules/...). Create some filed using this type of field (ConfigurationForm Fieldtype) Go to field setup Input tab and drag some subfields to container area (demo). Set "Name" and other params for subfields Save and place field to templates ("Action tab") How to use it:
      In my case, I use it to store setup and configurations values, but also for contact details, small content blocks... (eg. "widgets").
      Basic usage example:
      ConfigForm fieldtype "setup" has subfields:
      "limit", type select, option values: 5, 10, 15, 20
      "sort", type select, option values: "-date", "date",  "-sort", "sort"
      // get page children (items) $limit = isset($page->setup->limit) ? $page->setup->limit : 10; $sort = isset($page->setup->sort) ? $page->setup->sort : '-sort'; $items = $page->children("limit=$limit, sort=$sort");  
      Screenshots:


       
      Notes:
      Provide option to search inside subfields Provide multilanguage inputs for text and textarea field types Provide option for different field layout per-template basis Do not place/use field type "Button" or "File input" because it won't works. Please read README file for more details and examples Module use JSON format to store values. Text and textarea field types are multilanguage compatible, but please note that main target for this module was to store setup values and small content blocks and save DB space. Search part inside JSON is still a relatively new in MySQL (>=5.77) and that's on you how and for what to use this module.
      Thanks:
      Initial point for this fieldtype was jQuery plugin FormBuiled and thanks to Kevin Chappel for this plugin.
      In field type "link" I use javascript part from @marcostoll module and thanks to him for that part.
      Download:
      FieldtypeConfigForm.zip
      Edit: 14. August 2018. please delete/uninstall previously downloaded zip
      Regards.
         
    • By bernhard
      @Sergio asked about the pdf creation process in the showcase thread about my 360° feedback/survey tool and so I went ahead and set my little pdf helper module to public.
      Description from PW Weekly:
       
      Modules Directory: https://modules.processwire.com/modules/rock-pdf/
      Download & Docs: https://gitlab.com/baumrock/RockPdf
       
      You can combine it easily with RockReplacer: 
      See also a little showcase of the RockPdf module in this thread:
       
    • By Thomas Diroll
      Hi guys I'm relatively new to PW and just finished developing a page for a client. I was able to include all necessary functionality using the core fieldtypes but now I it seems that I need to extend them with a custom one. What I need is a simple button, that copies the absolute url (frontend not PW-backend) of the page which is currently edited to the clipboard. As this feature is only needed inside a specific template, I tend to use a custom fieldtype which provides this feature. I've been looking inside the core modules code (eg. FieldtypeCheckbox.module) but I don't really get the structure of it and how its rendered to the admin page. I also didn't find a lot of tutorials covering custom fieldtypes.
      Maybe some of you could give me some tips on how to write a basic custom fieldtype that renders a button which copies the value of
      page->httpUrl() to the clipboard using JS. Thanks!
    • By bernhard
      Some of you might have followed the development of this module here: https://processwire.com/talk/topic/15524-previewdiscussion-rockdatatables/ . It is the successor of "RockDataTables" and requires RockFinder to get the data for the grid easily and efficiently. It uses the open source part of agGrid for grid rendering.
       
      WHY?
      ProcessWire is awesome for creating all kinds of custom backend applications, but where it is not so awesome in my opinion is when it comes to listing this data. Of course we have the built in page lister and we have ListerPro, but none of that solutions is capable of properly displaying large amounts of data, for example lists of revenues, aggregations, quick and easy sorts by the user, instant filter and those kind of features. RockGrid to the rescue 😉 
       
      Features/Highlights:
      100k+ rows Instant (client side) filter, search, sort (different sort based on data type, eg "lower/greater than" for numbers, "contains" for strings) extendable via plugins (available plugins at the moment: fullscreen, csv export, reload, batch-processing of data, column sum/statistics, row selection) all the agGrid features (cell renderers, cell styling, pagination, column grouping etc) vanilla javascript, backend and frontend support (though not all plugins are working on the frontend yet and I don't plan to support it as long as I don't need it myself)  
      Limitations:
      While there is an option to retrieve data via AJAX the actual processing of the grid (displaying, filtering, sorting) is done on the client side, meaning that you can get into troubles when handling really large datasets of several thousands of rows. agGrid should be one of the most performant grid options in the world (see the official example page with a 100k row example) and does a lot to prevent problems (such as virtual row rendering), but you should always have this limitation in mind as this is a major difference to the available lister options that do not have this limitation.
      Currently it only supports AdminThemeUikit and I don't plan to support any other admin theme.
       
      Download: https://gitlab.com/baumrock/RockGrid
      Installation: https://gitlab.com/baumrock/RockGrid/wikis/Installation
      Quikckstart: https://gitlab.com/baumrock/RockGrid/wikis/quickstart
      Further instructions: https://gitlab.com/baumrock/RockGrid/wikis/quickstart#further-instructions
       
      Module status: alpha, License: MIT
      Note that every installation and uninstallation sends an anonymous google analytics event to my google analytics account. If you don't want that feel free to remove the appropriate lines of code before installation/uninstallation.
       
      Contribute:
      You can contribute to the development of this and other modules or just say thank you by
      testing, reporting issues and making PRs at gitlab liking this post buying me a drink: paypal.me/baumrock/5 liking my facebook page: facebook.com/baumrock hiring me for pw work: baumrock.com  
      Support: Please note that this module might not be as easy and plug&play as many other modules. It needs a good understanding of agGrid (and JavaScript in general) and it likely needs some looks into the code to get all the options. Please understand that I can not provide free support for every request here in the forum. I try to answer all questions that might also help others or that might improve the module but for individual requests I offer paid support for 60€ per hour.
       
      Changelog
      180730 support subdir installations 180711 bugfix (naming issue) 180630 alpha realease  
      Use Cases / Examples:
      Colored grid cells, Icons, Links etc. The Grid also has a "batcher" feature built in that helps communicating with the server via AJAX and managing resource intensive tasks in batches:

      Filters, PW panel links and instant reload on panel close:

      You can combine the grid with a chart library like I did with the (outdated) RockDataTables module: