devicemap-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reza Naghibi <reza.nagh...@yahoo.com.INVALID>
Subject Re: Collecting Specs for UAs
Date Mon, 05 Jan 2015 13:39:55 GMT
Right now that field isn't really defined well nor is it used directly in the data. I just
put it on there to give devices a bit of hardware context.

Please look at this as an example from our previous release:

https://issues.apache.org/jira/browse/DMAP-76


I stuck to CPU, GPU, and memory.

      From: Volkan Yazıcı <volkan.yazici@gmail.com>
 To: "dev@devicemap.apache.org" <dev@devicemap.apache.org> 
 Sent: Monday, January 5, 2015 2:19 AM
 Subject: Re: Collecting Specs for UAs
   
One more question: What does "hardware" in the list refer to?



On Fri, Jan 2, 2015 at 10:23 AM, Volkan Yazıcı <volkan.yazici@gmail.com>
wrote:

> Hi all,
>
> The entire UA collection tickets (DMAP-94, 95, 96, 97, 98, 100, 102) I
> have submitted to JIRA are being marked as NeedsSpec, which is fine. In the
> explanation, I am being told that I need to collect the following
> properties for each UA:
>
>    - id
>    - vendor
>    - model
>    - marketing name
>    - resolution-x
>    - resolution-y
>    - pixel-density-ppi
>    - release-year
>    - default-os
>    - hardware
>
> I have some questions regarding these properties:
>
>    - How other people collect this sort of information? Is there a
>    certain set of steps that I can follow? I was considering writing a crawler
>    on top of a web-based proprietary UA resolver, would that be ok considering
>    the licensing issues?
>    - Is there scheme am I supposed to follow for the *id* attribute? Or
>    something descriptive would be just fine?
>    - *resolution-x/y* means the width and height of the screen in pixels,
>    right?
>    - How do we calculate *pixel-density-ppi*?
>
> Best.
>

  
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message