On Fri, Oct 11, 2013 at 01:08:15PM -0300, Liu, David wrote: > HI, Gustavo > Thanks. Sounds nice. > For Android, if the format is not defined as C++ class but manifest Json > format, whether it is accepted？ > Of course, the format field representations of android can follow the > unified ones from Tizen and Chromium, > only the implementation of representations is different.
I don't get what you mean with Json. I suppose that's the input format, the one that will be parsed and converted into something generic/common to be used by rest of crosswalk. If that's the case, then sure, being Json or XML is expected. The C++ class I'm talking is the runtime container of information, the class that will store the information extracted from Json or XML. You may simplify it as a simple "Model" class (MVC nomenclature) that stores the meta information (name, description), entry points, permissions and extensions it will use. This one will be shared by all platforms, so be it Android or Tizen, your extension load system will query this class for permissions and extensions to load. Then one extension that provides multiple capabilities (think of Bluetooth) may query it for fine grained features to expose (remember this is still abstract, extensions run in their own process and we'd need a protocol to communicate with the main process to exchange this information). Our design should not bypass/short-circuit different parts, for instance if Android right now just supports Json parser and the extensions are specific we shouldn't abuse and start doing Json calls to the original file from everywhere. This is just bad design! What would happen if you then start to support Tizen package format on Android? By having an unified common model to store this information you simplify those, I do expect that the parsers to convert crx/wgt/... to something usable by Crosswalk will be cross-platform. -- Gustavo Sverzut Barbieri Intel Open source Technology Center _______________________________________________ Crosswalk-dev mailing list Crosswalk-dev@lists.crosswalk-project.org https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
