Still, all other sysapps API's are "prefixed" as they are under the sysapps.* namespace. Thus if the specs change at some point they can be migrated to another place and two incompatible implementations can be supported in parallel, with the one under sysapps.* as deprecated. When you add things directly under navigator.* you can never reuse that place for the final API when it reached Recommendation level.
This scares me. Kenneth On Tue, Nov 19, 2013 at 10:07 AM, Poussa, Sakari <[email protected]>wrote: > Hi, > > I would not like to prefix it. Actually, I think it would be fine to use > the namespace as in the the spec (navigator). All the SysApps APIs are now > more or less experimental and if we start second guessing what is more > mature than the other, we’ll have this discussion for each API. > > Thus, my recommendation is just to implement the spec as it is now. > > BR; Sakari >
_______________________________________________ Crosswalk-dev mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
