Skip to content
Browse files

Fixed some python package issues reported by Chris Clark - thanks!

  • Loading branch information...
1 parent bcc3a1a commit a33721569dea47a9fd714e4f20bf4410ec67856b @scottpersinger committed Sep 6, 2011
Showing with 112 additions and 10 deletions.
  1. +1 −1
  2. +88 −0 docs/tutorial/
  3. +12 −8 docs/tutorial/
  4. +5 −0 m5/
  5. +5 −0 m5/
  6. +1 −1
@@ -1,4 +1,4 @@
-recursive-include templates *.html *.css *.js
+recursive-include templates *.html *.css *.js *.json
recursive-include docs *.*
recursive-include lib *.*
recursive-include jquery-mobile *.*
88 docs/tutorial/
@@ -0,0 +1,88 @@
+M5 Backstory
+I believe it has become possible to create really great mobile apps using just HTML5 and Javascript. Some
+examples of these great apps include: Gmail, Google Plus, Twitter mobile, Linkedin Touch, and Yahoo Mail.
+However, you'll notice that all of these apps come from big companies, and none of them are open source.
+I built M5 as a toolkit to make it easier for me and for others to build great HTML5 mobile apps just like
+the big boys.
+Compared to something like Apple's iOS platform, the tools, documentation, and _collective intelligence_ around
+building _great_ mobile web apps is sorely lacking. M5 is my attempt to help start closing that gap, but
+* A toolkit which supports all the steps required for app development - from getting started, to development
+and testing, through to deployment.
+* A place to codify _best practices_ for building great mobile web apps.
+Shouldn't I just build a native app?
+Yup. You should - I strongly recommend it. I've built iOS apps and the Apple platform is great. I
+estimate it should take a good developer about 8 weeks, full time, to become proficient on iOS.
+Now once you're over that hurdle, go pay $99 to Apple and submit your app for approval. Wait a
+few more weeks and you should be ready to launch! Now when you want to port your app to Android,
+go repeat the process, subtracting a few weeks for app approval, but adding them to the learning
+time due to Android's less mature platform.
+Or, you could build and launch an HTML app **today**. True, launching on the web does not (currently)
+give you access to any App Stores for distribution. And your app will not run as smoothly as
+a native app. And if you want to be paid for your app, then the App Store is pretty hard to beat.
+But I think there's a world of apps that don't necessarily have these requirements.
+M5 is not designed to support certain types of apps:
+* Apps which need access to native device features. If you need to shoot photos, or read the
+phone's address book, or run completely disconnected from the internet, then you should build a native app.
+* Games. Games have their own special requirements, and M5 is not designed to address those. There are other frameworks and tools built to help you build HTML5 games.
+* Apps to be distributed through the App Store or Android Market. It is possible to build HTML5 apps and
+wrap them as native apps for distribution through an app store. [Phonegap]( is the
+leading solution here. M5 can help you build one of these apps, but I designed the toolkit with web distribution
+in mind, and it includes techniques to make web-distributed apps work better.
+What is an M5 app?
+Due to the flexibility of web technology, exactly **how** you build an HTML "app" is subject to much
+debate. I tend to think about the various options like this:
+1. Standard web site. No special mobile support.
+1. Web site with mobile stylesheet. Custom styles make web pages easier to read on mobile device screens.
+1. Server generated mobile app. App is composed of pages with special CSS rules and Javascript to enable
+an "app-like" experience on a mobile device. But, each page is still generated on the server and served
+through a separate HTTP request.
+1. Client generated mobile app. The user interface for the app is generated in Javascript on the
+mobile device. Server requests are made only for data updates (usually JSON) and then displayed in
+the app via client-side DOM injection.
+The farther down you go on this list, the closer you get to the native "app" experience that users
+have come to expect. And if you look at the mobile apps from the leading tech companies (Google,
+Twitter, LinkedIn), they all use approach #4. For this reason, M5 is designed to build apps
+in that way. Thus M5 uses the following app definition:
+> *An app which generates the dynamic portion of its interface via Javascript executed on the client.
+Static HTML for all pages is usually included in the home page. The app is designed to be cached on the
+device, and only requires access to the internet in order to retrieve application data.
+Most apps will employ local storage and the application cache, and ideally should be able to
+run even in the absence of any internet connection.*
+This is not necessarily the easiest way to create a mobile web app. But apps that do adopt this architecture
+benefit from these advantages:
+* Server-independent. Since logic runs on the client, these apps may need little to no server-side
+* Short load times.
+* Good perceived responsiveness since app updates run locally.
+Web distribution is awesome
+Yes, app stores are cool, especially for independent developers. However, as the Apple App Store
+approaches 500,000 apps, its good to question whether that distribution channel is really that
+huge an advantage. Especially with the "winner take all" sorting lists (self reinforcing sorts like
+"Most Popular"), it gets harder every day to stand out in the crowded app store.
+Launching on the web on the other hand gives you all the power of existing web-based distribution
+approaches: organic search, social links, advertising, and upselling from existing sites. Even better
+is you can launch and update any time, no approval needed.
20 docs/tutorial/
@@ -1,14 +1,18 @@
M5 Mobile Toolkit
-M5 is designed to be a "batteries included" toolkit for building HTML5 mobile apps. The basic components
-of M5 include:
-* A basic mobile UI framework - currently jQuery Mobile ('jQM') - for building your application UI
-* Browser-based simulator which allows you to test and refine your app easily on the desktop
-* Javascript support modules for HTML5 features like local storage
-* Package management that makes it easy to include additional Javascript libraries
-* A free cloud service for hosting your app
+M5 is designed to be a "batteries included" toolkit for building HTML5 mobile apps. There exist
+many frameworks for creating mobile apps in HTML, so M5 attempts to help out with all the other
+steps required to build an app:
+* Getting started. M5 comes with a number of examples apps and documentation to help get you started.
+* Development. The bundled web server is great for local development and testing.
+* Debugging. The M5 "simulator" makes it easy to see how your app will look on a real device,
+while letting you use your desktop browser's Javascript tools for debugging.
+* Deployment. M5 can "build" your project to automatically remove debugging code and generate
+files ready for hosting. You can even deploy your app for free to the web site.
+You can read about the [M5 background]( for some more backstory.
Creating your app
5 m5/
@@ -4,7 +4,12 @@
import pdb
from StringIO import StringIO
import re
+ import json
+except ImportError:
+ import simplejson as json
class M5App:
def __init__(self,name,root_dir,container=None,index_path=None): = name;
5 m5/
@@ -17,6 +17,11 @@
import glob
import random
+ import json
+except ImportError:
+ import simplejson as json
from compiler import *
from app import M5App
@@ -22,7 +22,7 @@ def gen_data_files(*dirs):
packages = ['m5'],
scripts = ['m5/m5'],
- install_requires = ['slimit>=0.5.3','bottle>=0.9.5','cherrypy'],
+ install_requires = ['slimit>=0.5.3','bottle>=0.9.5','cherrypy','urllib2-file','Markdown'],
data_files = gen_data_files("docs", "lib", "jquery-mobile", "templates"),

0 comments on commit a337215

Please sign in to comment.
Something went wrong with that request. Please try again.