Mobile web projects/VE on MobileFrontend

Questions to be answered:

 * What does it take to load VE in MobileFrontend now?
 * Target VE dependencies for mobile
 * Create base MobileFrontEnd integration modules.
 * What dependencies are there right now? - sizes determined via mw.loader.inspect on en.wikipedia.org
 * VE MobileFrontEnd integration modules ( WIP ) [which modules, what sizes?]
 * VE core modules - 591.01 KB
 * Other depenencies ( in order of importance ):
 * rangy ( cross browser selection ) - 86.59 KB
 * oojs ( event system, core ui widgets ) - 5.45 KB
 * unicodejs.wordbreak - word boundary support - 33.52 KB
 * mediawiki.user - 2.58 KB
 * user.options - 3.64 KB
 * user.tokens - 189 B
 * mediawiki.Title - 4.71 KB
 * mediawiki.Uri - 3.21 KB
 * jquery.byteLength - 159 B
 * jquery.byteLimit - 1.74 KB
 * jquery.client - 3.40 KB
 * mediawiki.feedback - 6.13 KB
 * mediawiki.jqueryMsg - 14.70 KB
 * mediawiki.notify - 209 B
 * jquery.placeholder - 1.00 KB
 * jquery.visibleText - 492 B
 * mediawiki.api - 2.58 KB
 * What are the impacts of loading all these dependencies right now?
 * I've compared the amount of resources on the same test page in KB before adding dependencies and after.
 * Before adding dependencies: 300kb
 * Before adding depenencies after clicking edit: 318kb
 * With dependencies: 333kb
 * With dependencies after activating VE: 1.3MB.
 * Activating VE with current dependencies ( Not including experimental features ) adds 860KB
 * In this case the data being delivered by Parsoid was 2.3kb ( small article on my local wiki )
 * What are your recommendations for untangling these dependencies and optimizing this for mobile?
 * Eliminate modules not needed by mobile ( modern ) browsers in the mobile target and init scripts.
 * For example: We probably don't need mediawiki.api or jquery.client as MobileFrontEnd has its own home brewed api and browser detection.