The whole desktop "guessing" with an assumed 800x600 screen was vague and
still is, putting those values into the main file probably even made that
worse. The fact that you cannot assume THE desktop device and no
server-side solution without the help of e.g. some Ajax, etc. can know the
size of a monitor is why ODDR had put it to "Patch". As a template to work
with and adjust if necessary. All of the below
<device id="genericDesktop" parentId="generic-">
<property name="displayHeight" value="600"/>
<property name="displayWidth" value="800"/>
<property name="is_wireless_device" value="false"/>
<property name="is_desktop" value="true"/>
<property name="ajax_support_javascript" value="true"/>
<property name="ajax_support_getelementbyid" value="true"/>
<property name="ajax_support_inner_html" value="true"/>
<property name="ajax_manipulate_dom" value="true"/>
<property name="ajax_manipulate_css" value="true"/>
<property name="ajax_support_events" value="true"/>
<property name="ajax_support_event_listener" value="true"/>
</device>
Is wrong or just a "best guess" default for some or many desktop computers.
Take the whold "ajax_" those often depend on the browser or user's choice.
"is_desktop" is the only value that can be said safely in a default. Which
is why it would conceptually be more correct (and not break any existing
APIs) if
DeviceDataSource.xml held:
<device id="genericDesktop" parentId="generic-">
<property name="is_wireless_device" value="false"/>
<property name="is_desktop" value="true"/>
</device>
(the "is_wireleless" is also fuzzy, but probably what separates a desktop
from a tablet, but where does my "notebook" sit from that perspective?;-D)
And had the good old Patch with a well-documented set of assumed values
like these:
<device id="desktopDevice" parentId="genericDesktop">
<property name="displayHeight" value="600"/>
<property name="displayWidth" value="800"/>
<property name="ajax_support_javascript" value="true"/>
<property name="ajax_support_getelementbyid" value="true"/>
<property name="ajax_support_inner_html" value="true"/>
<property name="ajax_manipulate_dom" value="true"/>
<property name="ajax_manipulate_css" value="true"/>
<property name="ajax_support_events" value="true"/>
<property name="ajax_support_event_listener" value="true"/>
</device>
Everything else is like the lady reading from the glass ball;-)
Werner
On Wed, Sep 10, 2014 at 5:58 PM, eberhard speer jr. <[email protected]>
wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Werner,
>
> I have to agree with you too, the whole desktop thing is vague and
> needs "a bit of explaining" :-)
>
> But incomplete is *much* more preferable to providing
> 'mickey-mouse'/'default' data. I mean just adding a screen width and
> height [any 'fair' guess] property to desktop is silly and as a
> general rule adding 'defaults' *reduces* the quality of the service/data.
>
> If you tell me Samsung so-and-so does Flash, does it really do that or
> is that just the system guessing and adding fluff/'defaults' to look
> complete ?
> It undermines the overall value.
>
> esjr
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.22 (MingW32)
>
> iQEcBAEBAgAGBQJUEHVBAAoJEOxywXcFLKYcDiIIAJDngtNFr3Cttl3OdgrFTBRO
> lEkwJbffrGbzBfWZeUgEVpPYoERAGfM8KBq9MRt4JMjtsobKqSg69T06gE0//3AP
> 93pvWEiezHPyCF5icSJ97kOmIYdTZysl1kZpRobcKuZhJaysgbvq6ErT/K1KVmB9
> Y+ZnUzewJgSqjrKocIGtAWbB7w3d+i2oq0qVR+DBEoecV7bgN0UiciLbsCtt1LAN
> huinVaHB21TrPG1UzEreszMgDLe9afjW24M/EOEliaocENoJKlQTH3VLiQqDZV5J
> 1pZkKvrSEsm83HHXxZzAY8+16cVXeuZe+dlz60sVZxqPKhM76D9+cu86bAh2tA0=
> =MIM6
> -----END PGP SIGNATURE-----
>
