Hi,
I would like to participate.  I was looking at some older code that I was 
updating to use JQuery Mobile 1.4 and wasn't very neat, the code was a bit 
sloppy.  I was taking the JSON returned from a WordPress JSON API blog 
(meaning I was using the JSON API plugin for the WordPress blogging 
platform)  and dynamically building up content to go into the div with 
data-role="content."  I thought there must be a cleaner and better way of 
doing this.  I was thinking at first, just using HandlebarsJS, Mustache or 
Dust.js to clean up the code.  Then I thought that I'd just jump right into 
Angular.js with JQuery Mobile.  I didn't realize that it would be 
complicated to just let Angular.js control parts of a page, like the div 
with data-role of content.  So, essentially, I was trying JQuery & JQuery 
Mobile, followed by JQM+JQ+Templates and finally JQ+JQM+Angular.js.  
     Now, I'm interested in this plan that you discuss here.  I'll have to 
get the repo and review it.  Not sure if you still need contributors or not.
Thanks,
Bruce

On Wednesday, May 29, 2013 4:10:20 AM UTC-4, Tobias Bosch wrote:
>
> Hi,
>
> after developing and using the jquery-mobile-angular-adapter we (the 
> mobile team of OPITZ CONSULTING) came to the conclusion, that we should 
> change it’s architecture:
>
> Use angular and the css of jqm only, but not the JavaScript part of jqm.
>
> Why?
>
>    - Download size: If you want to use the JavaScript part of jqm, you 
>    also need to use jquery. In total you need angular, jquery, jqm and the 
>    adapter. A lot of stuff…
>    - Performance: The original jqm widgets not always do things the most 
>    performant way. E.g. they use a lot of css selector queries. Furthermore, 
>    they usually only have one refresh method to refresh to whole widget 
>    (e.g. alistview), but not parts of it.
>    - Maintainability: Using the jqm JavaScript part requires some dirty 
>    hacks so that it works with angular. However, to maintain those hacks you 
>    need a lot of knowledge about the internas of jqm and angular.
>
> This is very similar to the angular bootstrap integration: There is an 
> adapter that uses the JavaScript part of bootstrap, angular-strap (
> http://mgcrea.github.io/angular-strap/), and another version that uses 
> the boostrap css only from the angular-ui team (
> http://angular-ui.github.io/bootstrap/).
>
> To ensure that our directives work correctly we will create special ui 
> tests that compare the generated markup of our directives with the markup 
> generated by plain jquery mobile. By this it should also be easy to keep 
> track of changes in jquery mobile when they release newer versions.
>
> Here are some questions:
>
>    - Does this make sense? What things should we especially care for when 
>    doing this?
>    - Did anyone already do this?
>    - Does anyone like to participate?
>
> We will be hosting the new project here: 
> https://github.com/opitzconsulting/angular-jqm
>
> Feedback welcome!
>
> Tobias (@tigbro)
>

-- 
You received this message because you are subscribed to the Google Groups 
"AngularJS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.

Reply via email to