also a Preview, but if the .NET projects were compatible with VS Code ( https://code.visualstudio.com/) or at least the Community Edition that would certainly lower the entry barrier to use it.
On Mon, Aug 3, 2015 at 8:20 PM, Reza Naghibi <[email protected]> wrote: > > I'll get busy on .Net version > > Awesome!!! Reach out if you have any questions or comments. > > On Mon, Aug 3, 2015 at 2:08 PM, eberhard speer jr. <[email protected]> > wrote: > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > I'll get busy on .Net version > > > > esjr > > > > On 2015-08-03 19:13, Reza Naghibi wrote: > > > I converted the 1.0 xml device data to 2.0 json. So given we now > > > have a reference client, reference domains, our device domain in > > > 2.0, and everything came together as designed, I think thats enough > > > to say we have an alpha release (pre beta). Beta and final release > > > will be in the August and September timeframe respectively. > > > > > > *Reference client*: > > > https://svn.apache.org/repos/asf/devicemap/trunk/clients/2.0/reference > > / > > > > > > This is pretty much done. I have a few small todos. Much simpler > > > than the 1.0 client and performance is still top notch, if not > > > better. Given that all parsing and matching configuration is driven > > > by the domain, 2.0 will be a big step forward in simplicity, > > > configuration, and performance. > > > > > > > > > *Reference domains*: > > > https://svn.apache.org/repos/asf/devicemap/trunk/data/2.0/reference/ > > > > > > There are 6 reference domains which hit on many aspects of the > > > 2.0 specification. This is also pretty much done. > > > > > > > > > *Device domain* (aka device data): > > > https://svn.apache.org/repos/asf/devicemap/trunk/data/2.0/device/ > > > > > > I went ahead and did a straight conversion from XML to JSON. All > > > 1309 unit tests from 1.0 pass on 2.0. However, the data still > > > contains browsers and other rules which need to be moved into the > > > OS and browser domains. Also, the attribute spec needs to be > > > implemented. So there will be several iterations of refinement and > > > enhancements here. > > > > > > > > > *Browser domain*: > > > > > > This is a todo. Shooting to have this done by August/September. > > > Will be part of the 2.0 release. > > > > > > > > > *OS domain*: > > > > > > This is a todo. Once again, completed by August/September. Will be > > > part of the 2.0 release. > > > > > > > > > *Java client*: > > > > > > This can be ported from the reference client. No ETA. Volkan and > > > other volunteers can take lead on this. > > > > > > > > > *Javascript client*: > > > > > > I will likely spearhead this if there are no volunteers. Shooting > > > for a September timeframe. > > > > > > > > > *C client*: > > > > > > I will own this as well, however no ETA. > > > > > > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG v2.0.22 (MingW32) > > > > iQEcBAEBAgAGBQJVv64YAAoJEOxywXcFLKYc6REH+gKAoO1rFrCqj7jRjJkQP8mq > > TQo2oAqloDGtVVy9wuJANt7VPg+LRZuBqLLTti7zGqWRx9sVYMRbN2BkWSQNGu0N > > HRjFj3jock9yUf7IokfgcrZ6DXOsfll3uUPS9lEpKpbKPU6Oy6YYstrjNq9Q89Pf > > CV3nC9/EEHuZbu/SQ8p1QcBV+KYyUB9WUEUAXy7xgAmlbS1SKYMSrf7tw0XBZoH3 > > QQk4vMKHJF3DuuUO7hRWkjcuBQ7wosmfrDJ4Y8O+9PH6p4Kf7olSCVHK+WRBR7jU > > F+e5gmt/1C9/ecf+p1Vj3O5odHlXHnqEmr+Jfk8GiVgu6d02McEeXovouseSygE= > > =S0xl > > -----END PGP SIGNATURE----- > > > > >
