The-M-Project: A HTML5 enabled JavaScript framework to target mobile devices

http://the-m-project.net/

by pfleidi • 16 years ago

18 10 16 years ago

the-m-project.net

rayboyd• 16 years ago

Is this just a fork of jQuery Mobile?

bsstoner• 16 years ago

Looks like jquery mobile + client side MVC-like framework.

Adding node.js as a requirement to do client side development seems like it would be a big deterrent.

astrofinch• 16 years ago

How does this compare to http://www.phonegap.com/?

dmix2• 16 years ago

A better comparison would be backbone.js.

It don't see any mention of it building natively to devices on the site. So you could still use Phonegap in combination with it.

I'm currently building a mobile app with backbone.js + jQuery Mobile + Phonegap. Backbone works great for me so I see no reason to switch.

detst• 16 years ago

Care to talk more about how you're using Backbone.js and jQuery Mobile?

I'm interested in this combination and wondering why this project wouldn't choose to build on Backbone.js. It seems they would just be reinventing the wheel here and losing the benefit of using the same library on full apps and mobile.

bherms• 16 years ago

I'm not quite seeing how this differentiates from JQTouch or just vanilla jQuery Mobile.

However, since I'm doing mobile HTML5/js development right now, I'll check it out after work and give my thoughts after playing around with it.

catshirt• 16 years ago

One difference at least seems to be that this encourages development entirely through Javascript. In that sense, it seems more like trying to compare jQuery to Backbone.

The disadvantage of this of course, is you lose the true cross platform (plain html) capability that jQuery mobile and jQtouch both provide. Though I don't imagine that would be hard for this project to facilitate at some point.

cdsanchez• 16 years ago

Interesting - I'm about to start working on a mobile site and I noticed there weren't many mobile frameworks that also used the MVC pattern. However, at first glance, I don't like that it requires node.js since I'm mostly on Windows.

This is just me nitpicking here: why did they feel the need to define two global variables (YES/NO) as aliases for true and false, respectively?

swerler• 16 years ago

We were defining it just for better readability:

isAsync:YES just sounds more naturally than isAsync:false.

Saw and liked it in Objective-C....

The-M-Project: A HTML5 enabled JavaScript framework to target mobile devices

Related Stories