Best approach for adopting responsive HTML when using jQuery UI

I have a web application that was built using jQuery UI and all our own CSS frameworks. I would like to modify the application to use a flexible structure so that I can work better with mobile devices. The first thing that comes to mind is Twitter Bootstrap. I am wondering what other people are going through, considering conflicts with the jQuery and Bootstrap user interface. The best thing

  • Get rid of the jQuery UI and convert everything to bootstrap controls (most of the work).
  • Save the jQuery user interface and just use the Twitter Bootstrap stand (possibly the best option).
  • Use a completely different forest infrastructure.
  • Something else
+4
source share
3 answers

This is such an open question that it would be impossible to answer correctly. What for? Because the reasoning for such a switch depends on many different factors on technical characteristics, such as jQuery UI widgets, which are used throughout the application, to how convenient you are as a developer with new frameworks. Therefore, in response to several questions to ask yourself to help you decide.

  • Am I using jQuery UI widgets throughout the application?

If so, consider introducing solutions to fill in the voids in the JQUI CSS framework. The most noticeable mesh scaffold. Switching JQUI widgets to other providers can be time consuming.

Gridpak sensitive grid generator

Set up Twitter bootloader to fill in JQUI spaces

  • Switching to another CSS structure will really help me?

Unfortunately, with well-known gaps in the JQUI CSS structure, the answer to this question (for me) was yes. Mostly I use either Twitter Bootstrap or Foundation, but I still use JQUI, they are just sure about the JS and CSS that I need when I set up the JQUI build.

CSS Framework Basis

  • How long will it cost me to switch and then re-factor?

The answer to this question is very important. If you lose a short term from the switch, it would probably be better to continue what you have, however, if the long-term gain is significantly higher than the short-term loss, it can tip the balance in favor of switching.

If you switched, and you haven't done it yet, maybe introducing parsing like SASS or LESS into the equation might be worth it. (SASS is my preferred route)

Twitter Bootstrap SASS'ified

Also check out Compass

  • When I finish, have I really achieved what I originally planned?

This is solely subject to due diligence and fact. Know what you are now tuned to before making a decision. This, in essence, is what this issue boils down to.

+3
source

Generally speaking, many Bootstrap / jQueryUI conflicts can be avoided by making sure bootstrap.js follows jqueryui.js and knowing which components are susceptible to conflicts (e.g. tabs, buttons, etc.)

If you use only Bootstrap for a sensitive mesh, you do not need to include bootstrap.js at all - just use CSS.

You may also be interested to see the Addy Osmani project:

https://github.com/addyosmani/jquery-ui-bootstrap

+3
source

You should try the Foundation framework.

+2
source

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


All Articles