On Fri, Feb 3, 2012 at 8:26 PM, Scott Wilson <[email protected] > wrote:
> On 3 Feb 2012, at 17:24, Bertrand Delacretaz wrote: > > > One thing that we discussed with Philip is using a neutral, text-based > > and diff-friendly format to store our core data. > > > > We can then derive various formats (json, xml maybe) using Maven or > > another build tool. > > > > We initially discussed using json for that, but in the meantime I > > think we should rather used the java properties format, as writing > > json by hand is no fun, whereas properties are easy to read/write both > > by hand and from code. > > > > I'd use a structure where folders represent device brands, series, > > models etc., and a properties file contains all that we know about a > > given device. > > > > I do like the idea of the native description format being something its > easy to edit in a text editor. > Yes, definitely. And yes, thinking of it I also feel that json is a bit awkward to write by hand, so the java properties format seems a good idea to me combined with a folder structure. I suppose any hierarchies within the properties could be handled using dot > notation on the property names. > Yes, that's a good possibility. Actually folder structures/hierarchies are good topics in itself and I guess we need to discuss these a bit as there might be some potential pitfalls to avoid early on. The Apple models are fairly straightforward to represent, however with Android this can change. For example certain models are region specific, or the same device is marketed with different names in different regions (I believe HTC did/does this) or special editions of existing phones are marketed, like a Ferrari edition or whatnot. I wonder how this is best represented (given possible constructs like 'that's me, over there' is certain cases). Ideas? -Philip
