All geek questions in one place

Cross-browser library, degrading touch events, no extra weight

I am creating a one-page web application and I was looking for a library that implements only a set of touch events, click, tap, swipe, etc., but not:

  • a) get me to use Sencha Touch.
  • b) come with a bunch of superfluous things that I don’t want, without the ability to break only part of the events (JQuery mobile and Sencha Touch).

I tried to snatch only events from jQuery mobile, and swipe events stopped working, not knowing why.

My experiments with jQuery mobile upset me, it made me create my application in my own way, adding data-role = "page" to my container to stop the page when it was turned on, adding loading divs to the body (yuk). Since I already have a working application, I don’t want this.

Does anyone have any recommendations?

Greetings

+4
source share
1 answer

jQM is now untied:

Widgets: now unleashed for flexible buildings

We wanted to separate all of our widgets from the page plugin for a long time and were pleased to announce that we had finally landed a change. So what does the meaning mean? Well, separate widgets and utilities have always been separate script files. However, the page plugin was responsible for handling the automatic initialization of all official plugins found in the markup when creating the page. This situation did not allow you to remove plugins that you do not need without causing errors, and generally set a bad precedent for future additions to widgets.

Now almost all of the user interface widgets in the jQuery Mobile library are completely decoupled, so you can simply remove them if they are not needed for a specific project. This change allows you to significantly reduce the size of the library, including only a specific set of widgets or functions that you need, in addition to a handful of required core files. Although we still plan to do more decoupling and cleaning up, the following files are now decoupled and can be removed from the make file before performing custom builds:

  • page title / content / footer
  • collapsible
  • controlgroup
  • fieldcontain
  • fixheaderfooter
  • Button
  • checkboxradio
  • select
  • slider
  • Textinput
  • links with links
  • Listview
  • Navbar
  • Grid

We will be working on a dependency map because several widgets rely on others to work. For example, the button layout plugin is called by many of the widgets above, so it can be excluded, but if you are not using any of the widgets that depend on the buttons.

Our recommendations on creating a dependency plugin and unleashing things even more worked out. This will eventually pop up in the download tool, so stay tuned!

You can go to your GIT registry and just download what you want:

+3
source

Source: https://habr.com/ru/post/1387434/

More articles:


All Articles