Geek asks and answers

JavascriptMVC jqueryMX Controller VS. widgets - can we all get along?

We created the ajax website and are thinking of porting to javascriptMVC. Our site has its own home-made controller that processes ajax calls for html and JS, and the user interface makes extensive use of jQuery UI widgets.

I read a little about javascriptMVC and I liked how the models are processed. especially how easy it is to interact with ajax to read your data. I assume that I have always, although models as JSON objects (structures in a sense), and forgot how powerful methods of adding to models can be.

However, while delving into javascriptMVC, I noticed that the controller takes up most of the functions of the JQuery UI widgets. I hate dropping our already working widgets. What are our options?

Can we only accept the jQueryMX model? is it wise? Should we completely change our controller and widgets and all-in in JavascriptMVC? Any other options?

Speaking of goals - we want to have a structure for future Ajax sites (controller + widgets).

+3
source share
1 answer

You can wrap JQuery UI widgets inside JMVC controllers as an intermediate step, but you are losing the important advantages that controllers have over typical JQuery plugins. Most jQuery plugins are written in an all-or-nothing style (see jqGrid Example). Mixing multiple jQuery plugins is usually not possible, or at least quite complicated, and leads to an ugly code base that doesn't work well (memory leak problems, etc.) ..).

JMVC , , . mxui "" JQueryUI

https://github.com/jupiterjs/mxui

http://forum.javascriptmvc.com/topic/what-are-the-plans-for-mxui

+2

More articles:


All Articles