Need a convenient way to run the plugin

[glebkema]

The plugin currently uses too many entities:

• It adds specific CSS class names for inherent CSS properties.
• It is required to call the jQuery method for the selector with the select field that the user wants to style.
• The user can define their own CSS classes for the HTML layout that will be compiled by the plugin.

So, we already have 3 types of CSS classes:

1. define target select \field
2. provide oligatory CSS properties
3. apply user CSS properties

I would like to simplify the start method and to make the final ierarchy of CSS clases more predictable. For example:

• User can start the plugin without JS-code:
  • by adding of specific CSS class name (as Owl Carousel);
  • by adding of specific data attributes (as FancyBox).
• User can define the structure of CSS clases:
  • by the data atributes;
  • by setting of the plugin defaults;
  • by the array of options for the plugin function.