Soma

Module
jQuery UI Range Slider Fieldtype

29 posts in this topic

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!

2 people like this

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); 
}
1 person likes this

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
      Hi,
      just stumbled over a little module that i built for my last project. it helped me to test performance of my rockdatatables module to generate 3000 random json datasets and i want to share it with you. maybe it saves some time for someone.
      https://gitlab.com/baumrock/RockDummyData/
      easy example:
      $rdd = $modules->get('RockDummyData'); for($i=0; $i<15; $i++) { // this has to be inside the for-loop to always get a new dummy $dummy = $rdd->getDummy(); echo date("d.m.Y H:i:s", $dummy->timestamp) . "<br>"; } more advanced:
      $json = new stdClass(); $json->data = array(); $rdd = $modules->get('RockDummyData'); for($i=0; $i<3000; $i++) { // this has to be inside the for-loop to always get a new dummy $dummy = $rdd->getDummy(); $obj = new stdClass(); $obj->name = $dummy->forename . ' ' . $dummy->surname; $obj->position = $dummy->job; $obj->office = $dummy->city; $obj->color = $dummy->color; $obj->start_date = new stdClass(); $obj->start_date->display = date('d.m.Y',$dummy->timestamp); $obj->start_date->sort = $dummy->timestamp; $obj->salary = rand(0,10000); $json->data[] = $obj; } echo json_encode($json); you have to store your random datasets on your own into the /data folder. there are several services for creating all kinds of random data on the web - if you know one service that allows sharing those datasets let me know and i can include common needed data into the module
    • By AndySh
      Hello!
      I need your assistance please. I purchased the module FormBuilder. Unfortunately, the module discontinued delivering customer submissions to e-mail box specified in the module settings. Direct mailing to the e-mail box works OK. The module settings stays the same and are correct, like "Send e-mail to administrator(s) is checked. The last version of FormBuilder 3.0 has been installed. Please advise how to resolve the issue becase I cannot get orders from customers anymore (((
    • By kixe
      As described in this post (https://processwire.com/talk/topic/8551-custom-urls-for-pages/?p=82742) the option 'Name Format Children' under the tab 'Family' in template settings doesn't work properly and also not as expected. I had a look inside the code and made some changes which are working properly, which offers much more options, more consistency and less code too.

      The result is the following. You have 3 Options for generating name and title, which could be combined in endless variations.
      Name is always derived from title, same like creating pages manually.
      type date: if function detects # character anywhere in the string, conversion will be: deletion of # and string will be used as format parameter for PHP date() function type field: if string is a fieldname of the parent page the value of this field will be used type string: if string doesn't fit to the 2 preceeding it will be taken as it is All parts (separated by comma) will be composed in the order of setting. You can use unlimited numbers of parts

      I made a pull request on github: https://github.com/ryancramerdesign/ProcessWire/pull/831

      Example screenshots

      Setting ...


      will result in


       
    • By kongondo
      FieldtypeRuntimeMarkup and InputfieldRuntimeMarkup
       
      Modules Directory: http://modules.processwire.com/modules/fieldtype-runtime-markup/
      GitHub: https://github.com/kongondo/FieldtypeRuntimeMarkup
       
      This module allows for custom markup to be dynamically (PHP) generated and output within a page's edit screen (in Admin).
       
      The value for the fieldtype is generated at runtime. No data is saved in the database. The accompanying InputfieldRuntimeMarkup is only used to render/display the markup in the page edit screen.
       
      The field's value is accessible from the ProcessWire API in the frontend like any other field, i.e. it has access to $page and $pages.
       
      The module was commissioned/sponsored by @Valan. Although there's certainly other ways to achieve what this module does, it offers a dynamic and flexible alternative to generating your own markup in a page's edit screen whilst also allowing access to that markup in the frontend. Thanks Valan!
       
      Warning/Consideration
      Although access to ProcessWire's Fields' admin pages is only available to Superusers, this Fieldtype will evaluate and run the custom PHP Code entered and saved in the field's settings (Details tab). Utmost care should therefore be taken in making sure your code does not perform any CRUD operations!! (unless of course that's intentional) The value for this fieldtype is generated at runtime and thus no data is stored in the database. This means that you cannot directly query a RuntimeMarkup field from $pages->find(). Usage and API
       
      Backend
      Enter your custom PHP snippet in the Details tab of your field (it is RECOMMENDED though that you use wireRenderFile() instead. See example below). Your code can be as simple or as complicated as you want as long as in the end you return a value that is not an array or an object or anything other than a string/integer.
       
      FieldtypeRuntimeMarkup has access to $page (the current page being edited/viewed) and $pages. 
       
      A very simple example.
      return 'Hello'; Simple example.
      return $page->title; Simple example with markup.
      return '<h2>' . $page->title . '</h2>'; Another simple example with markup.
      $out = '<h1>hello '; $out .= $page->title; $out .= '</h1>'; return $out; A more advanced example.
      $p = $pages->get('/about-us/')->child('sort=random'); return '<p>' . $p->title . '</p>'; An even more complex example.
      $str =''; if($page->name == 'about-us') { $p = $page->children->last(); $str = "<h2><a href='{$p->url}'>{$p->title}</a></h2>"; } else { $str = "<h2><a href='{$page->url}'>{$page->title}</a></h2>"; } return $str; Rather than type your code directly in the Details tab of the field, it is highly recommended that you placed all your code in an external file and call that file using the core wireRenderFile() method. Taking this approach means you will be able to edit your code in your favourite text editor. It also means you will be able to type more text without having to scroll. Editing the file is also easier than editing the field. To use this approach, simply do:
      return wireRenderFile('name-of-file');// file will be in /site/templates/ If using ProcessWire 3.x, you will need to use namespace as follows:
      return ProcessWire\wireRenderFile('name-of-file'); How to access the value of RuntimeMarkup in the frontend (our field is called 'runtime_markup')
       
      Access the field on the current page (just like any other field)
      echo $page->runtime_markup; Access the field on another page
      echo $pages->get('/about-us/')->runtime_markup; Screenshots
       
      Backend
       

       

       
      Frontend