Things that I see missing are: - shipping with no "core" APIs/plugins (but that hinges on master cli script and plugin discovery). - Getting Andrew Lunny's plugin spec [1] documented / integrated
Things that warrant more discussion: - what specifically to do about the media API. Highest priority I think based on # of issues that exist related to it in the JIRA. - file API path normalization. For sure. Also a "fuller" implementation: right now, the Entry objects have no association to a FileSystem object. So if you request a TEMPORARY FS and create an Entry in that FileSystem, and later do the same using a PERSISTENT FS, you will not be able to tell the difference between the two (unless you do it manually based on the probably platform-specific and differing paths each will have). - notifications API: YES!!! We already have plugins in the wild that we simply need to normalize the JS interface to the w3c spec [1] https://github.com/alunny/cordova-plugin-spec On 7/24/12 7:58 AM, "Brian LeRoux" <b...@brian.io> wrote: >Hey guys, i've just updated the wiki [1] with some near-term goals and >a first pass at the long desired core API audit. Essentially it notes >where things have moved forward in the standards process or, in some >cases, cordova specific upgrades we've discussed in the past. > >Please discuss! > >[1] http://wiki.apache.org/cordova/RoadmapProjects
