http://wiki.webos-internals.org/api.php?action=feedcontributions&user=Reeder.29&feedformat=atomWebOS Internals - User contributions [en]2024-03-29T09:24:18ZUser contributionsMediaWiki 1.35.1http://wiki.webos-internals.org/index.php?title=JavaScript_Services&diff=22019JavaScript Services2014-10-21T03:49:13Z<p>Reeder.29: /* Reserved errorCode Values */</p>
<hr />
<div>'''Some notes to flesh out the [https://developer.palm.com/content/api/dev-guide/js-services/overview.html old primary documentation]''' and the [http://developer.lge.com/webOSTV/develop/js-services/ new primary documentation]<br />
<br />
== Node versions ==<br />
* webOS 1.x: node not present<br />
* webOS 2.x: node v0.2.3<br />
* webOS 3.0: node v0.4.12<br />
* webOS TV: ?<br />
* LuneOS (webOS 3.5): node v0.10.25<br />
<br />
<br />
== Values returned over the PalmBus ==<br />
To return a success, set future.result to an object with the desired properties (where future is the future passed to the Command Assistant).<br />
<br />
To return a failure, set future.exception to an object (often some kind of Error). Best practice is to set both '''message''' and '''errorCode''' properties.<br />
(If you set the errorCode property of the object, that<br />
will be the errorCode returned over PalmBus, and the errorText will be copied from the message property. Otherwise, errorCode will be -9999 and errorText will be "MojoService: no errorCode supplied "+(reply.errorText||""))<br />
errorCode is nominally an integer, but some system services return a string.<br />
<br />
<br />
While the Command Assistant run() method is called "inside" the future, it's not clear that you can compose the passed future with others.<br />
<br />
<br />
== Reserved errorCode Values ==<br />
The following errorCode value should not be used by your service, because they are used by the PalmBus itself:<br />
<br />
* -1: missing service<br />
* 504: command timeout<br />
* -9999: no errorCode returned by JS service<br />
* 400 (or -9999 under webOS 3.0.0 and earlier): ? parameters don't match schema<br />
<br />
== Service Initialization ==<br />
If you have common setup which must be done, regardless of which command is called first, define a [https://developer.palm.com/content/api/reference/config/services.json.html Service Assistant] <br />
<br />
If you return a Future from the [https://developer.palm.com/content/api/dev-guide/js-services/services-faq.html#setup Service Assistant's setup method]<br />
your Command Assistant will not be called until that Future is resolved. If that Future fails, your Command Assistant will never be called, and the service call will eventually time out. So, ensure the Future always succeeds (storing an error if necessary):<br />
<br />
<code><pre><br />
MyServiceAssistant.prototype.setup = function () {<br />
return this.myAsyncMethod().then(function (f) {<br />
console.log("MyServiceAssistant.setup overall success", f.result);<br />
return f.result = f.result;<br />
}, function (f) {<br />
console.error("MyServiceAssistant.setup overall failure", f.exception);<br />
f.result = {foo: "bar"};<br />
});<br />
};<br />
</pre></code></div>Reeder.29http://wiki.webos-internals.org/index.php?title=JavaScript_Services&diff=22017JavaScript Services2014-10-20T21:22:33Z<p>Reeder.29: Added errorCodes returned by PalmBus itself.</p>
<hr />
<div>'''Some notes to flesh out the [https://developer.palm.com/content/api/dev-guide/js-services/overview.html old primary documentation]''' and the [http://developer.lge.com/webOSTV/develop/js-services/ new primary documentation]<br />
<br />
== Node versions ==<br />
* webOS 1.x: node not present<br />
* webOS 2.x: node v0.2.3<br />
* webOS 3.0: node v0.4.12<br />
* webOS TV: ?<br />
* LuneOS (webOS 3.5): node v0.10.25<br />
<br />
<br />
== Values returned over the PalmBus ==<br />
To return a success, set future.result to an object with the desired properties (where future is the future passed to the Command Assistant).<br />
<br />
To return a failure, set future.exception to an object (often some kind of Error). Best practice is to set both '''message''' and '''errorCode''' properties.<br />
(If you set the errorCode property of the object, that<br />
will be the errorCode returned over PalmBus, and the errorText will be copied from the message property. Otherwise, errorCode will be -9999 and errorText will be "MojoService: no errorCode supplied "+(reply.errorText||""))<br />
errorCode is nominally an integer, but some system services return a string.<br />
<br />
<br />
While the Command Assistant run() method is called "inside" the future, it's not clear that you can compose the passed future with others.<br />
<br />
<br />
== Reserved errorCode Values ==<br />
The following errorCode value should not be used by your service, because they are used by the PalmBus itself:<br />
<br />
* -1: missing service<br />
* 504: command timeout<br />
* -9999: no errorCode returned by JS service<br />
<br />
<br />
== Service Initialization ==<br />
If you have common setup which must be done, regardless of which command is called first, define a [https://developer.palm.com/content/api/reference/config/services.json.html Service Assistant] <br />
<br />
If you return a Future from the [https://developer.palm.com/content/api/dev-guide/js-services/services-faq.html#setup Service Assistant's setup method]<br />
your Command Assistant will not be called until that Future is resolved. If that Future fails, your Command Assistant will never be called, and the service call will eventually time out. So, ensure the Future always succeeds (storing an error if necessary):<br />
<br />
<code><pre><br />
MyServiceAssistant.prototype.setup = function () {<br />
return this.myAsyncMethod().then(function (f) {<br />
console.log("MyServiceAssistant.setup overall success", f.result);<br />
return f.result = f.result;<br />
}, function (f) {<br />
console.error("MyServiceAssistant.setup overall failure", f.exception);<br />
f.result = {foo: "bar"};<br />
});<br />
};<br />
</pre></code></div>Reeder.29http://wiki.webos-internals.org/index.php?title=JavaScript_Services&diff=22013JavaScript Services2014-10-14T18:28:22Z<p>Reeder.29: ref to LG docs</p>
<hr />
<div>'''Some notes to flesh out the [https://developer.palm.com/content/api/dev-guide/js-services/overview.html old primary documentation]''' and the [http://developer.lge.com/webOSTV/develop/js-services/ new primary documentation]<br />
<br />
== Node versions ==<br />
* webOS 1.x: node not present<br />
* webOS 2.x: node v0.2.3<br />
* webOS 3.0: node v0.4.12<br />
* webOS TV: ?<br />
* LuneOS (webOS 3.5): node v0.10.25<br />
<br />
<br />
== Values returned over the PalmBus ==<br />
To return a success, set future.result to an object with the desired properties (where future is the future passed to the Command Assistant).<br />
<br />
To return a failure, set future.exception to an object (often some kind of Error). Best practice is to set both '''message''' and '''errorCode''' properties.<br />
<br />
(If you set the errorCode property of the object, that<br />
will be the errorCode returned over PalmBus, and the errorText will be copied from the message property. Otherwise, errorCode will be -9999 and errorText will be "MojoService: no errorCode supplied "+(reply.errorText||""))<br />
<br />
<br />
While the Command Assistant run() method is called "inside" the future, it's not clear that you can compose the passed future with others.<br />
<br />
<br />
== Service Initialization ==<br />
If you have common setup which must be done, regardless of which command is called first, define a [https://developer.palm.com/content/api/reference/config/services.json.html Service Assistant] <br />
<br />
If you return a Future from the [https://developer.palm.com/content/api/dev-guide/js-services/services-faq.html#setup Service Assistant's setup method]<br />
your Command Assistant will not be called until that Future is resolved. If that Future fails, your Command Assistant will never be called, and the service call will eventually time out. So, ensure the Future always succeeds (storing an error if necessary):<br />
<br />
<code><pre><br />
MyServiceAssistant.prototype.setup = function () {<br />
return this.myAsyncMethod().then(function (f) {<br />
console.log("MyServiceAssistant.setup overall success", f.result);<br />
return f.result = f.result;<br />
}, function (f) {<br />
console.error("MyServiceAssistant.setup overall failure", f.exception);<br />
f.result = {foo: "bar"};<br />
});<br />
};<br />
</pre></code></div>Reeder.29http://wiki.webos-internals.org/index.php?title=JavaScript_Services&diff=22011JavaScript Services2014-10-14T18:20:08Z<p>Reeder.29: Service Initialization</p>
<hr />
<div>'''Some notes to flesh out the [https://developer.palm.com/content/api/dev-guide/js-services/overview.html primary documentation]'''<br />
<br />
== Node versions ==<br />
* webOS 1.x: node not present<br />
* webOS 2.x: node v0.2.3<br />
* webOS 3.0: node v0.4.12<br />
* webOS TV: ?<br />
* LuneOS (webOS 3.5): node v0.10.25<br />
<br />
<br />
== Values returned over the PalmBus ==<br />
To return a success, set future.result to an object with the desired properties (where future is the future passed to the Command Assistant).<br />
<br />
To return a failure, set future.exception to an object (often some kind of Error). Best practice is to set both '''message''' and '''errorCode''' properties.<br />
<br />
(If you set the errorCode property of the object, that<br />
will be the errorCode returned over PalmBus, and the errorText will be copied from the message property. Otherwise, errorCode will be -9999 and errorText will be "MojoService: no errorCode supplied "+(reply.errorText||""))<br />
<br />
<br />
While the Command Assistant run() method is called "inside" the future, it's not clear that you can compose the passed future with others.<br />
<br />
<br />
== Service Initialization ==<br />
If you have common setup which must be done, regardless of which command is called first, define a [https://developer.palm.com/content/api/reference/config/services.json.html Service Assistant] <br />
<br />
If you return a Future from the [https://developer.palm.com/content/api/dev-guide/js-services/services-faq.html#setup Service Assistant's setup method]<br />
your Command Assistant will not be called until that Future is resolved. If that Future fails, your Command Assistant will never be called, and the service call will eventually time out. So, ensure the Future always succeeds (storing an error if necessary):<br />
<br />
<code><pre><br />
MyServiceAssistant.prototype.setup = function () {<br />
return this.myAsyncMethod().then(function (f) {<br />
console.log("MyServiceAssistant.setup overall success", f.result);<br />
return f.result = f.result;<br />
}, function (f) {<br />
console.error("MyServiceAssistant.setup overall failure", f.exception);<br />
f.result = {foo: "bar"};<br />
});<br />
};<br />
</pre></code></div>Reeder.29http://wiki.webos-internals.org/index.php?title=JavaScript_Services&diff=22009JavaScript Services2014-10-13T14:45:40Z<p>Reeder.29: </p>
<hr />
<div>'''Some notes to flesh out the [https://developer.palm.com/content/api/dev-guide/js-services/overview.html primary documentation]'''<br />
<br />
== Node versions ==<br />
* webOS 1.x: node not present<br />
* webOS 2.x: node v0.2.3<br />
* webOS 3.0: node v0.4.12<br />
* webOS TV: ?<br />
* LuneOS (webOS 3.5): node v0.10.25<br />
<br />
<br />
== Values returned over the PalmBus ==<br />
To return a success, set future.result to an object with the desired properties (where future is the future passed to the Command Assistant).<br />
<br />
To return a failure, set future.exception to an object (often some kind of Error). Best practice is to set both '''message''' and '''errorCode''' properties.<br />
<br />
(If you set the errorCode property of the object, that<br />
will be the errorCode returned over PalmBus, and the errorText will be copied from the message property. Otherwise, errorCode will be -9999 and errorText will be "MojoService: no errorCode supplied "+(reply.errorText||""))<br />
<br />
<br />
While the Command Assistant run() method is called "inside" the future, it's not clear that you can compose the passed future with others.</div>Reeder.29http://wiki.webos-internals.org/index.php?title=JavaScript_Services&diff=22007JavaScript Services2014-10-13T03:00:09Z<p>Reeder.29: </p>
<hr />
<div>'''Some notes to flesh out the [https://developer.palm.com/content/api/dev-guide/js-services/overview.html primary documentation]'''<br />
<br />
== Node versions ==<br />
* webOS 2: node v0.2.3<br />
* webOS 3.0: node v0.4.12<br />
* webOS TV: ?<br />
* LuneOS (webOS 3.5): node v0.10.?<br />
<br />
<br />
== Values returned over the PalmBus ==<br />
To return a success, set future.result to an object with the desired properties (where future is the future passed to the Command Assistant).<br />
<br />
To return a failure, set future.exception to an object (typically some kind of Error). If you set the errorCode property of the object, that<br />
will be the errorCode returned over PalmBus, and the errorText will be copied from the message property. Otherwise, errorCode will be -9999 and errorText will be "MojoService: no errorCode supplied "+(reply.errorText||"")<br />
<br />
<br />
While the Command Assistant run() method is called "inside" the future, it's not clear that you can compose the passed future with others.</div>Reeder.29http://wiki.webos-internals.org/index.php?title=JavaScript_Services&diff=22005JavaScript Services2014-10-12T03:21:16Z<p>Reeder.29: returning values</p>
<hr />
<div><br />
'''Some notes to flesh out the [https://developer.palm.com/content/api/dev-guide/js-services/overview.html primary documentation] =='''<br />
<br />
== Node versions<br />
* webOS 2: node v0.2.3<br />
* webOS 3.0: node v0.4.12<br />
* webOS TV: ?<br />
* LuneOS (webOS 3.5): node v0.10.?<br />
<br />
<br />
== Values returned over the PalmBus<br />
To return a success, set future.result to an object with the desired properties (where future is the future passed to the Command Assistant).<br />
<br />
To return a failure, set future.exception to an object (typically some kind of Error). If you set the errorCode property of the object, that<br />
will be the errorCode returned over PalmBus, and the errorText will be copied from the message property. Otherwise, errorCode will be -9999 and errorText will be "MojoService: no errorCode supplied "+(reply.errorText||"")<br />
<br />
<br />
While the Command Assistant run() method is called "inside" the future, it's not clear that you can compose the passed future with others.</div>Reeder.29http://wiki.webos-internals.org/index.php?title=JavaScript_Services&diff=22003JavaScript Services2014-10-11T20:18:37Z<p>Reeder.29: Initial creation</p>
<hr />
<div><br />
== Some notes to flesh out the [https://developer.palm.com/content/api/dev-guide/js-services/overview.html primary documentation] ==<br />
<br />
=== Node versions<br />
* webOS 2: node v0.2.3<br />
* webOS 3.0: node v0.4.12<br />
* webOS TV: ?<br />
* LuneOS (webOS 3.5): node v0.10.?</div>Reeder.29http://wiki.webos-internals.org/index.php?title=Netbook&diff=21325Netbook2012-01-08T19:06:15Z<p>Reeder.29: /* Possible */</p>
<hr />
<div>=Porting webOS to a touchscreen ARM netbook (or convertible tablet)=<br />
<br />
== Motivation ==<br />
webOS is designed for users to search data and create new data, by means of a keyboard built in to each phone. <br />
Typedown filter lists allow users to quickly find an item amid thousands.<br />
Netbooks marry the high-input-bandwidth of a keyboard to the high (for a mobile device) output bandwidth output of a display.<br />
Netbooks running a desktop OS have stalled, because mobile design is different than desktop design.<br />
Netbooks running webOS will combine the ease-of-use of webOS with high-bandwidth input, making it ideal for mobile search and mobile content creation.<br />
Netbooks are ideal for command-line use.<br />
<br />
== Goals ==<br />
* normal use of standard webOS apps on a netbook<br />
* packaging open-source webOS to make installing it as easy as it can be.<br />
<br />
==Hardware==<br />
First priority is to identify suitable hardware, with a multitouch screen. We need to find an initial target platform that is currently available.<br />
<br />
<br />
What kind of graphics chips can be made to work?<br />
<br />
<br />
===Possible===<br />
[https://www.alwaysinnovating.com/products/touchbook.htm Always Innovating Touch Book Netbook v2 ]<br />
The company is all about open hardware and varying OSs.<br />
* CPU board: http://www.alwaysinnovating.com/wiki/index.php/MID_board without the Smart Book components<br />
* Tablet module: http://www.alwaysinnovating.com/wiki/index.php/Smart_Book_specs without the Mini Book<br />
* install another (ARM-based) OS page: http://www.alwaysinnovating.com/wiki/index.php/Install_another_OS<br />
<br />
<br />
[http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#specifications Asus EEE Pad Transformer]<br />
<br />
[http://allstar-ch.ecrater.com/p/11193522/8inch-freescale-mx515-arm-cortex SG-TPC TPC0801]<br />
Can't find mfg page, which would make it a poor initial target.<br />
<br />
[http://www.amazon.co.uk/Toshiba-AC100-10U-Netbook-nVidia-Android/dp/B003VYB2KO/ref=sr_1_1?ie=UTF8&qid=1313925045&sr=8-1 Toshiba AC 100]<br />
Toshiba's site doesn't acknowledge this, so it may have been discontinued.<br />
<br />
{| border="1" cellspacing="0"<br />
|+ Specs<br />
! !! HP Touchpad !! Pre2 !! AlwaysInnovating TouchBook 2 !! Eee Pad Transformer TF101<br />
|- <br />
|SOC || Qualcomm Snapdragon APQ8060 || OMAP 3630 || TI ? OMAP3530 || NVIDIA Tegra 2<br />
|-<br />
| processor core || Scorpion (similar to ARM Cortex A8) || ARM Cortex-A8 || ARM Cortex-A8 || ARM Cortex-A9 (lacks NEON)<br />
|-<br />
| cores || 2 || 1 || 1 || 2<br />
|- <br />
| instruction set || ARMv7 || || ARMv7, Thumb-2 || ARMv7<br />
|-<br />
| ordering || || || In-order dual instruction issue || <br />
|-<br />
| L2 cache || 512 kB || || 256 KB || shared 1MB<br />
|-<br />
| Graphics || Qualcomm Adreno 220 core || PowerVR SGX530 || || ULP GeForce 333 MHz<br />
|-<br />
| display || 1024x768 || 320x480 || 1024x600 8.9" capacitive touchscreen ? [http://www.gblcd.com/datacenter/au/B089AW01_V0.pdf AU Optronics B089AW01 V0] || 1280x800 "10 finger multi-touch support"<br />
|-<br />
| accelerometer || || || [http://www.freescale.com/files/sensors/doc/data_sheet/MMA7455L.pdf?WT_TYPE=Data%20Sheets&WT_VENDOR=FREESCALE&WT_FILE_FORMAT=pdf&WT_ASSET=Documentation Freescale MMA7455L] || "G-Sensor", "Gyroscope"<br />
|}<br />
<br />
===Not Possible===<br />
chromebooks (no touchscreen)<br />
<br />
==Areas of Concern==<br />
* low-level touch screen driver<br />
* gstreamer; what codecs are already available?<br />
<br />
==Tools==<br />
* OpenEmbedded and Debian build systems</div>Reeder.29http://wiki.webos-internals.org/index.php?title=Netbook&diff=21323Netbook2012-01-08T19:04:08Z<p>Reeder.29: /* Porting webOS to a touchscreen ARM netbook */</p>
<hr />
<div>=Porting webOS to a touchscreen ARM netbook (or convertible tablet)=<br />
<br />
== Motivation ==<br />
webOS is designed for users to search data and create new data, by means of a keyboard built in to each phone. <br />
Typedown filter lists allow users to quickly find an item amid thousands.<br />
Netbooks marry the high-input-bandwidth of a keyboard to the high (for a mobile device) output bandwidth output of a display.<br />
Netbooks running a desktop OS have stalled, because mobile design is different than desktop design.<br />
Netbooks running webOS will combine the ease-of-use of webOS with high-bandwidth input, making it ideal for mobile search and mobile content creation.<br />
Netbooks are ideal for command-line use.<br />
<br />
== Goals ==<br />
* normal use of standard webOS apps on a netbook<br />
* packaging open-source webOS to make installing it as easy as it can be.<br />
<br />
==Hardware==<br />
First priority is to identify suitable hardware, with a multitouch screen. We need to find an initial target platform that is currently available.<br />
<br />
<br />
What kind of graphics chips can be made to work?<br />
<br />
<br />
===Possible===<br />
[https://www.alwaysinnovating.com/products/touchbook.htm Always Innovating Touch Book Netbook v2 ]<br />
The company is all about open hardware and varying OSs.<br />
* CPU board: http://www.alwaysinnovating.com/wiki/index.php/MID_board without the Smart Book components<br />
* Tablet module: http://www.alwaysinnovating.com/wiki/index.php/Smart_Book_specs without the Mini Book<br />
* install another (ARM-based) OS page: http://www.alwaysinnovating.com/wiki/index.php/Install_another_OS<br />
<br />
<br />
[http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#specifications Asus EEE Pad Transformer]<br />
<br />
[http://allstar-ch.ecrater.com/p/11193522/8inch-freescale-mx515-arm-cortex SG-TPC TPC0801]<br />
Can't find mfg page, which would make it a poor initial target.<br />
<br />
[http://www.amazon.co.uk/Toshiba-AC100-10U-Netbook-nVidia-Android/dp/B003VYB2KO/ref=sr_1_1?ie=UTF8&qid=1313925045&sr=8-1 Toshiba AC 100]<br />
Toshiba's site doesn't acknowledge this, so it may have been discontinued.<br />
<br />
{| border="1" cellspacing="0"<br />
|+ Specs<br />
! !! HP Touchpad !! Pre2 !! AlwaysInnovating TouchBook 2 !! Eee Pad Transformer TF101<br />
|- <br />
|SOC || Qualcomm Snapdragon APQ8060 || OMAP 3630 || TI ? OMAP3530 || NVIDIA Tegra 2<br />
|-<br />
| processor core || Scorpion (similar to ARM Cortex A8) || ARM Cortex-A8 || ARM Cortex-A8 || ARM Cortex-A9 (lacks NEON)<br />
|-<br />
| cores || 2 || 1 || 1 || 2<br />
|- <br />
| instruction set || ARMv7 || || ARMv7, Thumb-2 || ARMv7<br />
|-<br />
| ordering || || || In-order dual instruction issue || <br />
|-<br />
| L2 cache || 512 kB || || 256 KB || shared 1MB<br />
|-<br />
| Graphics || Qualcomm Adreno 220 core || PowerVR SGX530 || || ULP GeForce 333 MHz<br />
|-<br />
| display || || || 1024x600 8.9" capacitive touchscreen ? [http://www.gblcd.com/datacenter/au/B089AW01_V0.pdf AU Optronics B089AW01 V0] || 1280x800 "10 finger multi-touch support"<br />
|-<br />
| accelerometer || || || [http://www.freescale.com/files/sensors/doc/data_sheet/MMA7455L.pdf?WT_TYPE=Data%20Sheets&WT_VENDOR=FREESCALE&WT_FILE_FORMAT=pdf&WT_ASSET=Documentation Freescale MMA7455L] || "G-Sensor", "Gyroscope"<br />
|}<br />
<br />
===Not Possible===<br />
chromebooks (no touchscreen)<br />
<br />
==Areas of Concern==<br />
* low-level touch screen driver<br />
* gstreamer; what codecs are already available?<br />
<br />
==Tools==<br />
* OpenEmbedded and Debian build systems</div>Reeder.29http://wiki.webos-internals.org/index.php?title=Netbook&diff=21321Netbook2012-01-08T19:01:39Z<p>Reeder.29: /* Possible */ added Eee Pad Transformer TF101</p>
<hr />
<div>=Porting webOS to a touchscreen ARM netbook=<br />
<br />
== Motivation ==<br />
webOS is designed for users to search data and create new data, by means of a keyboard built in to each phone. <br />
Typedown filter lists allow users to quickly find an item amid thousands.<br />
Netbooks marry the high-input-bandwidth of a keyboard to the high (for a mobile device) output bandwidth output of a display.<br />
Netbooks running a desktop OS have stalled, because mobile design is different than desktop design.<br />
Netbooks running webOS will combine the ease-of-use of webOS with high-bandwidth input, making it ideal for mobile search and mobile content creation.<br />
Netbooks are ideal for command-line use.<br />
<br />
== Goals ==<br />
* normal use of standard webOS apps on a netbook<br />
* packaging open-source webOS to make installing it as easy as it can be.<br />
<br />
==Hardware==<br />
First priority is to identify suitable hardware, with a multitouch screen. We need to find an initial target platform that is currently available.<br />
<br />
<br />
What kind of graphics chips can be made to work?<br />
<br />
<br />
===Possible===<br />
[https://www.alwaysinnovating.com/products/touchbook.htm Always Innovating Touch Book Netbook v2 ]<br />
The company is all about open hardware and varying OSs.<br />
* CPU board: http://www.alwaysinnovating.com/wiki/index.php/MID_board without the Smart Book components<br />
* Tablet module: http://www.alwaysinnovating.com/wiki/index.php/Smart_Book_specs without the Mini Book<br />
* install another (ARM-based) OS page: http://www.alwaysinnovating.com/wiki/index.php/Install_another_OS<br />
<br />
<br />
[http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#specifications Asus EEE Pad Transformer]<br />
<br />
[http://allstar-ch.ecrater.com/p/11193522/8inch-freescale-mx515-arm-cortex SG-TPC TPC0801]<br />
Can't find mfg page, which would make it a poor initial target.<br />
<br />
[http://www.amazon.co.uk/Toshiba-AC100-10U-Netbook-nVidia-Android/dp/B003VYB2KO/ref=sr_1_1?ie=UTF8&qid=1313925045&sr=8-1 Toshiba AC 100]<br />
Toshiba's site doesn't acknowledge this, so it may have been discontinued.<br />
<br />
{| border="1" cellspacing="0"<br />
|+ Specs<br />
! !! HP Touchpad !! Pre2 !! AlwaysInnovating TouchBook 2 !! Eee Pad Transformer TF101<br />
|- <br />
|SOC || Qualcomm Snapdragon APQ8060 || OMAP 3630 || TI ? OMAP3530 || NVIDIA Tegra 2<br />
|-<br />
| processor core || Scorpion (similar to ARM Cortex A8) || ARM Cortex-A8 || ARM Cortex-A8 || ARM Cortex-A9 (lacks NEON)<br />
|-<br />
| cores || 2 || 1 || 1 || 2<br />
|- <br />
| instruction set || ARMv7 || || ARMv7, Thumb-2 || ARMv7<br />
|-<br />
| ordering || || || In-order dual instruction issue || <br />
|-<br />
| L2 cache || 512 kB || || 256 KB || shared 1MB<br />
|-<br />
| Graphics || Qualcomm Adreno 220 core || PowerVR SGX530 || || ULP GeForce 333 MHz<br />
|-<br />
| display || || || 1024x600 8.9" capacitive touchscreen ? [http://www.gblcd.com/datacenter/au/B089AW01_V0.pdf AU Optronics B089AW01 V0] || 1280x800 "10 finger multi-touch support"<br />
|-<br />
| accelerometer || || || [http://www.freescale.com/files/sensors/doc/data_sheet/MMA7455L.pdf?WT_TYPE=Data%20Sheets&WT_VENDOR=FREESCALE&WT_FILE_FORMAT=pdf&WT_ASSET=Documentation Freescale MMA7455L] || "G-Sensor", "Gyroscope"<br />
|}<br />
<br />
===Not Possible===<br />
chromebooks (no touchscreen)<br />
<br />
==Areas of Concern==<br />
* low-level touch screen driver<br />
* gstreamer; what codecs are already available?<br />
<br />
==Tools==<br />
* OpenEmbedded and Debian build systems</div>Reeder.29http://wiki.webos-internals.org/index.php?title=Netbook&diff=20513Netbook2011-12-13T03:59:13Z<p>Reeder.29: /* Possible */</p>
<hr />
<div>=Porting webOS to a touchscreen ARM netbook=<br />
<br />
== Motivation ==<br />
webOS is designed for users to search data and create new data, by means of a keyboard built in to each phone. <br />
Typedown filter lists allow users to quickly find an item amid thousands.<br />
Netbooks marry the high-input-bandwidth of a keyboard to the high (for a mobile device) output bandwidth output of a display.<br />
Netbooks running a desktop OS have stalled, because mobile design is different than desktop design.<br />
Netbooks running webOS will combine the ease-of-use of webOS with high-bandwidth input, making it ideal for mobile search and mobile content creation.<br />
Netbooks are ideal for command-line use.<br />
<br />
== Goals ==<br />
* normal use of standard webOS apps on a netbook<br />
* packaging open-source webOS to make installing it as easy as it can be.<br />
<br />
==Hardware==<br />
First priority is to identify suitable hardware, with a multitouch screen. We need to find an initial target platform that is currently available.<br />
<br />
<br />
What kind of graphics chips can be made to work?<br />
<br />
<br />
===Possible===<br />
[https://www.alwaysinnovating.com/products/touchbook.htm Always Innovating Touch Book Netbook v2 ]<br />
The company is all about open hardware and varying OSs.<br />
* CPU board: http://www.alwaysinnovating.com/wiki/index.php/MID_board without the Smart Book components<br />
* Tablet module: http://www.alwaysinnovating.com/wiki/index.php/Smart_Book_specs without the Mini Book<br />
* install another (ARM-based) OS page: http://www.alwaysinnovating.com/wiki/index.php/Install_another_OS<br />
<br />
<br />
[http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#specifications Asus EEE Pad Transformer]<br />
<br />
[http://allstar-ch.ecrater.com/p/11193522/8inch-freescale-mx515-arm-cortex SG-TPC TPC0801]<br />
Can't find mfg page, which would make it a poor initial target.<br />
<br />
[http://www.amazon.co.uk/Toshiba-AC100-10U-Netbook-nVidia-Android/dp/B003VYB2KO/ref=sr_1_1?ie=UTF8&qid=1313925045&sr=8-1 Toshiba AC 100]<br />
Toshiba's site doesn't acknowledge this, so it may have been discontinued.<br />
<br />
{| border="1" cellspacing="0"<br />
|+ Specs<br />
! !! HP Touchpad !! Pre2 !! AlwaysInnovating TouchBook 2<br />
|- <br />
|SOC || Qualcomm Snapdragon APQ8060 || OMAP 3630 || TI ? OMAP3530<br />
|-<br />
| processor core || Scorpion (similar to ARM Cortex A8) || ARM Cortex-A8 || ARM Cortex-A8<br />
|-<br />
| cores || 2 || 1 || 1<br />
|- <br />
| instruction set || ARMv7 || || ARMv7, Thumb-2<br />
|-<br />
| ordering || || || In-order dual instruction issue<br />
|-<br />
| L2 cache || 512 kB || || 256 KB<br />
|-<br />
| Graphics || Qualcomm Adreno 220 core || PowerVR SGX530 ||<br />
|-<br />
| display || || || 1024x600 8.9" capacitive touchscreen ? [http://www.gblcd.com/datacenter/au/B089AW01_V0.pdf AU Optronics B089AW01 V0]<br />
|-<br />
| accelerometer || || || [http://www.freescale.com/files/sensors/doc/data_sheet/MMA7455L.pdf?WT_TYPE=Data%20Sheets&WT_VENDOR=FREESCALE&WT_FILE_FORMAT=pdf&WT_ASSET=Documentation Freescale MMA7455L]<br />
|}<br />
<br />
===Not Possible===<br />
chromebooks (no touchscreen)<br />
<br />
==Areas of Concern==<br />
* low-level touch screen driver<br />
* gstreamer; what codecs are already available?<br />
<br />
==Tools==<br />
* OpenEmbedded and Debian build systems</div>Reeder.29http://wiki.webos-internals.org/index.php?title=Netbook&diff=20511Netbook2011-12-13T03:52:55Z<p>Reeder.29: /* Possible */ added Specs table</p>
<hr />
<div>=Porting webOS to a touchscreen ARM netbook=<br />
<br />
== Motivation ==<br />
webOS is designed for users to search data and create new data, by means of a keyboard built in to each phone. <br />
Typedown filter lists allow users to quickly find an item amid thousands.<br />
Netbooks marry the high-input-bandwidth of a keyboard to the high (for a mobile device) output bandwidth output of a display.<br />
Netbooks running a desktop OS have stalled, because mobile design is different than desktop design.<br />
Netbooks running webOS will combine the ease-of-use of webOS with high-bandwidth input, making it ideal for mobile search and mobile content creation.<br />
Netbooks are ideal for command-line use.<br />
<br />
== Goals ==<br />
* normal use of standard webOS apps on a netbook<br />
* packaging open-source webOS to make installing it as easy as it can be.<br />
<br />
==Hardware==<br />
First priority is to identify suitable hardware, with a multitouch screen. We need to find an initial target platform that is currently available.<br />
<br />
<br />
What kind of graphics chips can be made to work?<br />
<br />
<br />
===Possible===<br />
[https://www.alwaysinnovating.com/products/touchbook.htm Always Innovating Touch Book Netbook v2 ]<br />
The company is all about open hardware and varying OSs.<br />
* CPU board: http://www.alwaysinnovating.com/wiki/index.php/MID_board without the Smart Book components<br />
* Tablet module: http://www.alwaysinnovating.com/wiki/index.php/Smart_Book_specs without the Mini Book<br />
* install another (ARM-based) OS page: http://www.alwaysinnovating.com/wiki/index.php/Install_another_OS<br />
<br />
<br />
[http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#specifications Asus EEE Pad Transformer]<br />
<br />
[http://allstar-ch.ecrater.com/p/11193522/8inch-freescale-mx515-arm-cortex SG-TPC TPC0801]<br />
Can't find mfg page, which would make it a poor initial target.<br />
<br />
[http://www.amazon.co.uk/Toshiba-AC100-10U-Netbook-nVidia-Android/dp/B003VYB2KO/ref=sr_1_1?ie=UTF8&qid=1313925045&sr=8-1 Toshiba AC 100]<br />
Toshiba's site doesn't acknowledge this, so it may have been discontinued.<br />
<br />
{| border="1" cellspacing="0"<br />
|+ Specs<br />
! !! HP Touchpad !! Pre2 !! AlwaysInnovating TouchBook 2<br />
|- <br />
|SOC || Qualcomm Snapdragon APQ8060 || OMAP 3630 || TI ? OMAP3530<br />
|-<br />
| processor core || Scorpion (similar to ARM Cortex A8) || ARM Cortex-A8 || ARM Cortex-A8<br />
|-<br />
| cores || 2 || 1 || 1<br />
|- <br />
| instruction set || ARMv7 || || ARMv7, Thumb-2<br />
|-<br />
| ordering || || || In-order dual instruction issue<br />
|-<br />
| L2 cache || 512 kB || || 256 KB<br />
|-<br />
| Graphics || Qualcomm Adreno 220 core || ||<br />
|-<br />
| display || || || 1024x600 8.9" capacitive touchscreen ? [http://www.gblcd.com/datacenter/au/B089AW01_V0.pdf AU Optronics B089AW01 V0]<br />
|-<br />
| accelerometer || || || [http://www.freescale.com/files/sensors/doc/data_sheet/MMA7455L.pdf?WT_TYPE=Data%20Sheets&WT_VENDOR=FREESCALE&WT_FILE_FORMAT=pdf&WT_ASSET=Documentation Freescale MMA7455L]<br />
|}<br />
<br />
===Not Possible===<br />
chromebooks (no touchscreen)<br />
<br />
==Areas of Concern==<br />
* low-level touch screen driver<br />
* gstreamer; what codecs are already available?<br />
<br />
==Tools==<br />
* OpenEmbedded and Debian build systems</div>Reeder.29http://wiki.webos-internals.org/index.php?title=Netbook&diff=20509Netbook2011-12-13T03:36:09Z<p>Reeder.29: /* Possible */</p>
<hr />
<div>=Porting webOS to a touchscreen ARM netbook=<br />
<br />
== Motivation ==<br />
webOS is designed for users to search data and create new data, by means of a keyboard built in to each phone. <br />
Typedown filter lists allow users to quickly find an item amid thousands.<br />
Netbooks marry the high-input-bandwidth of a keyboard to the high (for a mobile device) output bandwidth output of a display.<br />
Netbooks running a desktop OS have stalled, because mobile design is different than desktop design.<br />
Netbooks running webOS will combine the ease-of-use of webOS with high-bandwidth input, making it ideal for mobile search and mobile content creation.<br />
Netbooks are ideal for command-line use.<br />
<br />
== Goals ==<br />
* normal use of standard webOS apps on a netbook<br />
* packaging open-source webOS to make installing it as easy as it can be.<br />
<br />
==Hardware==<br />
First priority is to identify suitable hardware, with a multitouch screen. We need to find an initial target platform that is currently available.<br />
<br />
<br />
What kind of graphics chips can be made to work?<br />
<br />
<br />
===Possible===<br />
[https://www.alwaysinnovating.com/products/touchbook.htm Always Innovating Touch Book Netbook v2 ]<br />
The company is all about open hardware and varying OSs.<br />
* CPU board: http://www.alwaysinnovating.com/wiki/index.php/MID_board without the Smart Book components<br />
* Tablet module: http://www.alwaysinnovating.com/wiki/index.php/Smart_Book_specs without the Mini Book<br />
* install another (ARM-based) OS page: http://www.alwaysinnovating.com/wiki/index.php/Install_another_OS<br />
<br />
<br />
[http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#specifications Asus EEE Pad Transformer]<br />
<br />
[http://allstar-ch.ecrater.com/p/11193522/8inch-freescale-mx515-arm-cortex SG-TPC TPC0801]<br />
Can't find mfg page, which would make it a poor initial target.<br />
<br />
[http://www.amazon.co.uk/Toshiba-AC100-10U-Netbook-nVidia-Android/dp/B003VYB2KO/ref=sr_1_1?ie=UTF8&qid=1313925045&sr=8-1 Toshiba AC 100]<br />
Toshiba's site doesn't acknowledge this, so it may have been discontinued.<br />
<br />
{| border="1" cellspacing="0"<br />
|+ Specs<br />
! !! HP Touchpad !! AlwaysInnovating TouchBook 2<br />
|- <br />
|SOC || Qualcomm Snapdragon APQ8060 || ? OMAP3530<br />
|-<br />
| processor core || Scorpion (similar to ARM Cortex A8) || TI Cortex-A8<br />
|-<br />
| cores || 2 || 1<br />
|- <br />
| instruction set || ARMv7 || ARMv7, Thumb-2<br />
|-<br />
| ordering || || In-order dual instruction issue<br />
|-<br />
| L2 cache || 512 kB || 256 KB<br />
|-<br />
| Graphics || Qualcomm Adreno 220 core ||<br />
|-<br />
| display || || 1024x600 8.9" capacitive touchscreen ? [http://www.gblcd.com/datacenter/au/B089AW01_V0.pdf AU Optronics B089AW01 V0]<br />
|-<br />
| accelerometer || || [http://www.freescale.com/files/sensors/doc/data_sheet/MMA7455L.pdf?WT_TYPE=Data%20Sheets&WT_VENDOR=FREESCALE&WT_FILE_FORMAT=pdf&WT_ASSET=Documentation Freescale MMA7455L]<br />
|}<br />
<br />
===Not Possible===<br />
chromebooks (no touchscreen)<br />
<br />
==Areas of Concern==<br />
* low-level touch screen driver<br />
* gstreamer; what codecs are already available?<br />
<br />
==Tools==<br />
* OpenEmbedded and Debian build systems</div>Reeder.29http://wiki.webos-internals.org/index.php?title=Netbook&diff=20507Netbook2011-12-13T03:09:44Z<p>Reeder.29: /* Possible */</p>
<hr />
<div>=Porting webOS to a touchscreen ARM netbook=<br />
<br />
== Motivation ==<br />
webOS is designed for users to search data and create new data, by means of a keyboard built in to each phone. <br />
Typedown filter lists allow users to quickly find an item amid thousands.<br />
Netbooks marry the high-input-bandwidth of a keyboard to the high (for a mobile device) output bandwidth output of a display.<br />
Netbooks running a desktop OS have stalled, because mobile design is different than desktop design.<br />
Netbooks running webOS will combine the ease-of-use of webOS with high-bandwidth input, making it ideal for mobile search and mobile content creation.<br />
Netbooks are ideal for command-line use.<br />
<br />
== Goals ==<br />
* normal use of standard webOS apps on a netbook<br />
* packaging open-source webOS to make installing it as easy as it can be.<br />
<br />
==Hardware==<br />
First priority is to identify suitable hardware, with a multitouch screen. We need to find an initial target platform that is currently available.<br />
<br />
<br />
What kind of graphics chips can be made to work?<br />
<br />
<br />
===Possible===<br />
[https://www.alwaysinnovating.com/products/touchbook.htm Always Innovating Touch Book Netbook v2 ]<br />
The company is all about open hardware and varying OSs.<br />
* CPU board: http://www.alwaysinnovating.com/wiki/index.php/MID_board without the Smart Book components<br />
* Tablet module: http://www.alwaysinnovating.com/wiki/index.php/Smart_Book_specs without the Mini Book<br />
* install another (ARM-based) OS page: http://www.alwaysinnovating.com/wiki/index.php/Install_another_OS<br />
<br />
<br />
[http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#specifications Asus EEE Pad Transformer]<br />
<br />
[http://allstar-ch.ecrater.com/p/11193522/8inch-freescale-mx515-arm-cortex SG-TPC TPC0801]<br />
Can't find mfg page, which would make it a poor initial target.<br />
<br />
[http://www.amazon.co.uk/Toshiba-AC100-10U-Netbook-nVidia-Android/dp/B003VYB2KO/ref=sr_1_1?ie=UTF8&qid=1313925045&sr=8-1 Toshiba AC 100]<br />
Toshiba's site doesn't acknowledge this, so it may have been discontinued.<br />
<br />
{| border="1" cellspacing="0"<br />
|+ Specs<br />
! !! HP Touchpad !! AlwaysInnovating TouchBook 2<br />
|- <br />
|SOC || Qualcomm Snapdragon APQ8060 || b<br />
|-<br />
| processor core || Scorpion (similar to ARM Cortex A8) || TI Cortex-A8<br />
|-<br />
| cores || 2 || <br />
|- <br />
| instruction set || ARMv7 || ARMv7, Thumb-2<br />
|-<br />
| ordering || || In-order dual instruction issue<br />
|-<br />
| L2 cache || 512 kB || 256 KB<br />
|-<br />
| Graphics || Qualcomm Adreno 220 core ||<br />
|-<br />
| display || || 1024x600 8.9" capacitive touchscreen<br />
|}<br />
<br />
===Not Possible===<br />
chromebooks (no touchscreen)<br />
<br />
==Areas of Concern==<br />
* low-level touch screen driver<br />
* gstreamer; what codecs are already available?<br />
<br />
==Tools==<br />
* OpenEmbedded and Debian build systems</div>Reeder.29http://wiki.webos-internals.org/index.php?title=Netbook&diff=20479Netbook2011-12-10T19:56:58Z<p>Reeder.29: added Areas of Concern & Tools</p>
<hr />
<div>=Porting webOS to a touchscreen ARM netbook=<br />
<br />
== Motivation ==<br />
webOS is designed for users to search data and create new data, by means of a keyboard built in to each phone. <br />
Typedown filter lists allow users to quickly find an item amid thousands.<br />
Netbooks marry the high-input-bandwidth of a keyboard to the high (for a mobile device) output bandwidth output of a display.<br />
Netbooks running a desktop OS have stalled, because mobile design is different than desktop design.<br />
Netbooks running webOS will combine the ease-of-use of webOS with high-bandwidth input, making it ideal for mobile search and mobile content creation.<br />
Netbooks are ideal for command-line use.<br />
<br />
== Goals ==<br />
* normal use of standard webOS apps on a netbook<br />
* packaging open-source webOS to make installing it as easy as it can be.<br />
<br />
==Hardware==<br />
First priority is to identify suitable hardware, with a multitouch screen. We need to find an initial target platform that is currently available.<br />
<br />
<br />
What kind of graphics chips can be made to work?<br />
<br />
<br />
===Possible===<br />
[https://www.alwaysinnovating.com/products/touchbook.htm Always Innovating Touch Book Netbook v2 ]<br />
The company is all about open hardware and varying OSs.<br />
* CPU board: http://www.alwaysinnovating.com/wiki/index.php/MID_board without the Smart Book components<br />
* Tablet module: http://www.alwaysinnovating.com/wiki/index.php/Smart_Book_specs without the Mini Book<br />
* install another (ARM-based) OS page: http://www.alwaysinnovating.com/wiki/index.php/Install_another_OS<br />
<br />
<br />
[http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#specifications Asus EEE Pad Transformer]<br />
<br />
[http://allstar-ch.ecrater.com/p/11193522/8inch-freescale-mx515-arm-cortex SG-TPC TPC0801]<br />
Can't find mfg page, which would make it a poor initial target.<br />
<br />
[http://www.amazon.co.uk/Toshiba-AC100-10U-Netbook-nVidia-Android/dp/B003VYB2KO/ref=sr_1_1?ie=UTF8&qid=1313925045&sr=8-1 Toshiba AC 100]<br />
Toshiba's site doesn't acknowledge this, so it may have been discontinued.<br />
<br />
===Not Possible===<br />
chromebooks (no touchscreen)<br />
<br />
==Areas of Concern==<br />
* low-level touch screen driver<br />
* gstreamer; what codecs are already available?<br />
<br />
==Tools==<br />
* OpenEmbedded and Debian build systems</div>Reeder.29http://wiki.webos-internals.org/index.php?title=Netbook&diff=20477Netbook2011-12-10T19:44:31Z<p>Reeder.29: /* Motivation */</p>
<hr />
<div>=Porting webOS to a touchscreen ARM netbook=<br />
<br />
== Motivation ==<br />
webOS is designed for users to search data and create new data, by means of a keyboard built in to each phone. <br />
Typedown filter lists allow users to quickly find an item amid thousands.<br />
Netbooks marry the high-input-bandwidth of a keyboard to the high (for a mobile device) output bandwidth output of a display.<br />
Netbooks running a desktop OS have stalled, because mobile design is different than desktop design.<br />
Netbooks running webOS will combine the ease-of-use of webOS with high-bandwidth input, making it ideal for mobile search and mobile content creation.<br />
Netbooks are ideal for command-line use.<br />
<br />
== Goals ==<br />
* Demonstration of standard webOS apps running on a netbook<br />
* packaging open-source webOS to make installing it as easy as it can be.<br />
<br />
==Hardware==<br />
First priority is to identify suitable hardware, with a multitouch screen. We need to find an initial target platform that is currently available.<br />
<br />
<br />
What kind of graphics chips can be made to work?<br />
<br />
<br />
===Possible===<br />
[https://www.alwaysinnovating.com/products/touchbook.htm Always Innovating Touch Book Netbook v2 ]<br />
The company is all about open hardware and varying OSs.<br />
* CPU board: http://www.alwaysinnovating.com/wiki/index.php/MID_board without the Smart Book components<br />
* Tablet module: http://www.alwaysinnovating.com/wiki/index.php/Smart_Book_specs without the Mini Book<br />
* install another OS page: http://www.alwaysinnovating.com/wiki/index.php/Install_another_OS<br />
<br />
<br />
[http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#specifications Asus EEE Pad Transformer]<br />
<br />
[http://allstar-ch.ecrater.com/p/11193522/8inch-freescale-mx515-arm-cortex SG-TPC TPC0801]<br />
Can't find mfg page, which would make it a poor initial target.<br />
<br />
[http://www.amazon.co.uk/Toshiba-AC100-10U-Netbook-nVidia-Android/dp/B003VYB2KO/ref=sr_1_1?ie=UTF8&qid=1313925045&sr=8-1 Toshiba AC 100]<br />
Toshiba's site doesn't acknowledge this, so it may have been discontinued.<br />
<br />
===Not Possible===<br />
chromebooks (no touchscreen)</div>Reeder.29http://wiki.webos-internals.org/index.php?title=Netbook&diff=20475Netbook2011-12-10T19:42:34Z<p>Reeder.29: /* Possible */ added links to Touch Book</p>
<hr />
<div>=Porting webOS to a touchscreen ARM netbook=<br />
<br />
== Motivation ==<br />
webOS is designed for users to search data and create new data, by means of a keyboard built in to each phone. <br />
Typedown filter lists allow users to quickly find an item amid thousands.<br />
Netbooks marry the high-input-bandwidth of a keyboard to the high (for a mobile device) output bandwidth output of a display.<br />
Netbooks running a desktop OS failed, because mobile design is different than desktop design.<br />
Netbooks running webOS will combine the ease-of-use of webOS with high-bandwidth input, making it ideal for mobile serch and mobile content creation.<br />
<br />
== Goals ==<br />
* Demonstration of standard webOS apps running on a netbook<br />
* packaging open-source webOS to make installing it as easy as it can be.<br />
<br />
==Hardware==<br />
First priority is to identify suitable hardware, with a multitouch screen. We need to find an initial target platform that is currently available.<br />
<br />
<br />
What kind of graphics chips can be made to work?<br />
<br />
<br />
===Possible===<br />
[https://www.alwaysinnovating.com/products/touchbook.htm Always Innovating Touch Book Netbook v2 ]<br />
The company is all about open hardware and varying OSs.<br />
* CPU board: http://www.alwaysinnovating.com/wiki/index.php/MID_board without the Smart Book components<br />
* Tablet module: http://www.alwaysinnovating.com/wiki/index.php/Smart_Book_specs without the Mini Book<br />
* install another OS page: http://www.alwaysinnovating.com/wiki/index.php/Install_another_OS<br />
<br />
<br />
[http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#specifications Asus EEE Pad Transformer]<br />
<br />
[http://allstar-ch.ecrater.com/p/11193522/8inch-freescale-mx515-arm-cortex SG-TPC TPC0801]<br />
Can't find mfg page, which would make it a poor initial target.<br />
<br />
[http://www.amazon.co.uk/Toshiba-AC100-10U-Netbook-nVidia-Android/dp/B003VYB2KO/ref=sr_1_1?ie=UTF8&qid=1313925045&sr=8-1 Toshiba AC 100]<br />
Toshiba's site doesn't acknowledge this, so it may have been discontinued.<br />
<br />
===Not Possible===<br />
chromebooks (no touchscreen)</div>Reeder.29http://wiki.webos-internals.org/index.php?title=Netbook&diff=20473Netbook2011-12-10T18:30:19Z<p>Reeder.29: /* Possible */ SG-TPC TPC0801</p>
<hr />
<div>=Porting webOS to a touchscreen ARM netbook=<br />
<br />
== Motivation ==<br />
webOS is designed for users to search data and create new data, by means of a keyboard built in to each phone. <br />
Typedown filter lists allow users to quickly find an item amid thousands.<br />
Netbooks marry the high-input-bandwidth of a keyboard to the high (for a mobile device) output bandwidth output of a display.<br />
Netbooks running a desktop OS failed, because mobile design is different than desktop design.<br />
Netbooks running webOS will combine the ease-of-use of webOS with high-bandwidth input, making it ideal for mobile serch and mobile content creation.<br />
<br />
== Goals ==<br />
* Demonstration of standard webOS apps running on a netbook<br />
* packaging open-source webOS to make installing it as easy as it can be.<br />
<br />
==Hardware==<br />
First priority is to identify suitable hardware, with a multitouch screen. We need to find an initial target platform that is currently available.<br />
<br />
<br />
What kind of graphics chips can be made to work?<br />
<br />
<br />
===Possible===<br />
[https://www.alwaysinnovating.com/products/touchbook.htm Always Innovating Touch Book Netbook v2 ]<br />
The company is all about open hardware and varying OSs.<br />
<br />
[http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#specifications Asus EEE Pad Transformer]<br />
<br />
[http://allstar-ch.ecrater.com/p/11193522/8inch-freescale-mx515-arm-cortex SG-TPC TPC0801]<br />
Can't find mfg page, which would make it a poor initial target.<br />
<br />
[http://www.amazon.co.uk/Toshiba-AC100-10U-Netbook-nVidia-Android/dp/B003VYB2KO/ref=sr_1_1?ie=UTF8&qid=1313925045&sr=8-1 Toshiba AC 100]<br />
Toshiba's site doesn't acknowledge this, so it may have been discontinued.<br />
<br />
===Not Possible===<br />
chromebooks (no touchscreen)</div>Reeder.29http://wiki.webos-internals.org/index.php?title=Netbook&diff=20471Netbook2011-12-09T21:37:16Z<p>Reeder.29: added motivation</p>
<hr />
<div>=Porting webOS to a touchscreen ARM netbook=<br />
<br />
== Motivation ==<br />
webOS is designed for users to search data and create new data, by means of a keyboard built in to each phone. <br />
Typedown filter lists allow users to quickly find an item amid thousands.<br />
Netbooks marry the high-input-bandwidth of a keyboard to the high (for a mobile device) output bandwidth output of a display.<br />
Netbooks running a desktop OS failed, because mobile design is different than desktop design.<br />
Netbooks running webOS will combine the ease-of-use of webOS with high-bandwidth input, making it ideal for mobile serch and mobile content creation.<br />
<br />
== Goals ==<br />
* Demonstration of standard webOS apps running on a netbook<br />
* packaging open-source webOS to make installing it as easy as it can be.<br />
<br />
==Hardware==<br />
First priority is to identify suitable hardware, with a multitouch screen. We need to find an initial target platform that is currently available.<br />
<br />
<br />
What kind of graphics chips can be made to work?<br />
<br />
<br />
===Possible===<br />
[https://www.alwaysinnovating.com/products/touchbook.htm Always Innovating Touch Book Netbook v2 ]<br />
The company appears open to varying OSs.<br />
<br />
[http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#specifications Asus EEE Pad Transformer]<br />
<br />
[http://www.amazon.co.uk/Toshiba-AC100-10U-Netbook-nVidia-Android/dp/B003VYB2KO/ref=sr_1_1?ie=UTF8&qid=1313925045&sr=8-1 Toshiba AC 100]<br />
Toshiba's site doesn't acknowledge this, so it may have been discontinued.<br />
<br />
===Not Possible===<br />
chromebooks (no touchscreen)</div>Reeder.29http://wiki.webos-internals.org/index.php?title=Netbook&diff=20469Netbook2011-12-09T21:20:46Z<p>Reeder.29: /* Possible */</p>
<hr />
<div>=Porting webOS to a touchscreen ARM netbook=<br />
<br />
==Hardware==<br />
First priority is to identify suitable hardware, with a multitouch screen. We need to find an initial target platform that is currently available.<br />
<br />
<br />
What kind of graphics chips can be made to work?<br />
<br />
<br />
===Possible===<br />
[https://www.alwaysinnovating.com/products/touchbook.htm Always Innovating Touch Book Netbook v2 ]<br />
The company appears open to varying OSs.<br />
<br />
[http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#specifications Asus EEE Pad Transformer]<br />
<br />
[http://www.amazon.co.uk/Toshiba-AC100-10U-Netbook-nVidia-Android/dp/B003VYB2KO/ref=sr_1_1?ie=UTF8&qid=1313925045&sr=8-1 Toshiba AC 100]<br />
Toshiba's site doesn't acknowledge this, so it may have been discontinued.<br />
<br />
===Not Possible===<br />
chromebooks (no touchscreen)</div>Reeder.29http://wiki.webos-internals.org/index.php?title=Netbook&diff=20467Netbook2011-12-09T20:52:48Z<p>Reeder.29: /* Hardware */</p>
<hr />
<div>=Porting webOS to a touchscreen ARM netbook=<br />
<br />
==Hardware==<br />
First priority is to identify suitable hardware, with a multitouch screen. We need to find an initial target platform that is currently available.<br />
<br />
<br />
What kind of graphics chips can be made to work?<br />
<br />
<br />
===Possible===<br />
[https://www.alwaysinnovating.com/products/touchbook.htm Always Innovating Touch Book Netbook v2 ]<br />
<br />
[http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#specifications Asus EEE Pad Transformer]<br />
<br />
[http://www.amazon.co.uk/Toshiba-AC100-10U-Netbook-nVidia-Android/dp/B003VYB2KO/ref=sr_1_1?ie=UTF8&qid=1313925045&sr=8-1 Toshiba AC 100]<br />
Toshiba's site doesn't acknowledge this, so it may have been discontinued.<br />
<br />
===Not Possible===<br />
chromebooks (no touchscreen)</div>Reeder.29http://wiki.webos-internals.org/index.php?title=Netbook&diff=20465Netbook2011-12-09T20:46:07Z<p>Reeder.29: added Asus EEE Pad Transformer</p>
<hr />
<div>=Porting webOS to a touchscreen ARM netbook=<br />
<br />
==Hardware==<br />
First priority is to identify suitable hardware. We need to find an initial target platform that is currently available.<br />
What kind of graphics chips will work?<br />
<br />
<br />
===Possible===<br />
[https://www.alwaysinnovating.com/products/touchbook.htm Always Innovating Touch Book Netbook v2 ]<br />
<br />
[http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#specifications Asus EEE Pad Transformer]<br />
<br />
[http://www.amazon.co.uk/Toshiba-AC100-10U-Netbook-nVidia-Android/dp/B003VYB2KO/ref=sr_1_1?ie=UTF8&qid=1313925045&sr=8-1 Toshiba AC 100]<br />
Toshiba's site doesn't acknowledge this, so it may have been discontinued.<br />
<br />
===Not Possible===<br />
chromebooks (no touchscreen)</div>Reeder.29http://wiki.webos-internals.org/index.php?title=Portal:Hardware&diff=20463Portal:Hardware2011-12-09T20:37:33Z<p>Reeder.29: typo</p>
<hr />
<div>__notoc__<br />
{{portal-header|<br />
Just list everything related to the hardware. <br><br />
Title pages: '''Hardware [description]'''<br />
}}<br />
'''[[:Category:Hardware|All pages in Category:Hardware]]'''<br />
<br />
* [[Move a Pre- to a Pre+ on Sprint]]<br />
* [[External Battery Pack]]<br />
* [[A2dp]]<br />
* [[Accelerometer]]<br />
* [[Ambient Light Sensor]]<br />
* [[Bluetooth Research]]<br />
* [[GPS]]<br />
* [[Hardware]]<br />
* [[Hardware issues]]<br />
* [[IR Proximity Sensor]]<br />
* [[Controlling LEDs from the Shell|LEDS: Control from the shell]]<br />
* [[More on Leds|LEDS: More information]] <br />
* [[OMAP vibration device|OMAP vibration device]] <br />
* [[Torch/Flash|Torch/Flash]] <br />
* [[USB]]<br />
* [[WLAN|WLAN / WIFI]]<br />
* [[Touchscreen]]<br />
* [[Temperature Sensor]]<br />
* [[Camera]]<br />
* [[Battery]]<br />
* [[PalmPre2HardwareAndDriversInformations| Hardware and drivers used in the palm-pre 2, and how different it is from the palm-pre]]<br />
* [[Debug-Testpads]]<br />
* [[LCD]]<br />
* [[HP TP Key mapping]]<br />
* [[netbook|porting webOS to a Touchscreen ARM netbook]]</div>Reeder.29http://wiki.webos-internals.org/index.php?title=Portal:Hardware&diff=20461Portal:Hardware2011-12-09T20:35:39Z<p>Reeder.29: added link to netbook port</p>
<hr />
<div>__notoc__<br />
{{portal-header|<br />
Just list everything related to the hardware. <br><br />
Title pages: '''Hardware [description]'''<br />
}}<br />
'''[[:Category:Hardware|All pages in Category:Hardware]]'''<br />
<br />
* [[Move a Pre- to a Pre+ on Sprint]]<br />
* [[External Battery Pack]]<br />
* [[A2dp]]<br />
* [[Accelerometer]]<br />
* [[Ambient Light Sensor]]<br />
* [[Bluetooth Research]]<br />
* [[GPS]]<br />
* [[Hardware]]<br />
* [[Hardware issues]]<br />
* [[IR Proximity Sensor]]<br />
* [[Controlling LEDs from the Shell|LEDS: Control from the shell]]<br />
* [[More on Leds|LEDS: More information]] <br />
* [[OMAP vibration device|OMAP vibration device]] <br />
* [[Torch/Flash|Torch/Flash]] <br />
* [[USB]]<br />
* [[WLAN|WLAN / WIFI]]<br />
* [[Touchscreen]]<br />
* [[Temperature Sensor]]<br />
* [[Camera]]<br />
* [[Battery]]<br />
* [[PalmPre2HardwareAndDriversInformations| Hardware and drivers used in the palm-pre 2, and how different it is from the palm-pre]]<br />
* [[Debug-Testpads]]<br />
* [[LCD]]<br />
* [[HP TP Key mapping]]<br />
* [[netbook porting webOS to a Touchscreen ARM netbook]]</div>Reeder.29http://wiki.webos-internals.org/index.php?title=Netbook&diff=20459Netbook2011-12-09T20:33:58Z<p>Reeder.29: Initial sketch</p>
<hr />
<div>=Porting webOS to a touchscreen ARM netbook=<br />
<br />
==Hardware==<br />
First priority is to identify suitable hardware. We need to find an initial target platform that is currently available.<br />
What kind of graphics chips will work?<br />
<br />
<br />
===Possible===<br />
[https://www.alwaysinnovating.com/products/touchbook.htm Always Innovating Touch Book Netbook v2 ]<br />
<br />
[http://www.amazon.co.uk/Toshiba-AC100-10U-Netbook-nVidia-Android/dp/B003VYB2KO/ref=sr_1_1?ie=UTF8&qid=1313925045&sr=8-1 Toshiba AC 100]<br />
Toshiba's site doesn't acknowledge this, so it may have been discontinued.<br />
<br />
===Not Possible===<br />
chromebooks (no touchscreen)</div>Reeder.29http://wiki.webos-internals.org/index.php?title=Application:Preware&diff=14841Application:Preware2011-03-30T03:26:32Z<p>Reeder.29: /* Installing Preware on webOS 2.0 */ added note about command-line method</p>
<hr />
<div>[[Category:Application]]<br />
This page is currently available in four languages:<br />
:[[Image:Australia.png]] [[Image:USA.png]] [[Application:Preware]]<br />
:[[Image:France.png]] [[Application:Preware-FR]]<br />
:[[Image:Germany.png]] [[Application:Preware-DE]]<br />
:[[Image:China.png]] [[Application:Preware-ZH]]<br />
<br />
{{application<br />
|name=Preware<br />
|type=webOS<br />
|version=Version: 1.5.0 (17 Dec 2010)<br />
|tag=Utilities<br />
|screenshot=Preware_ss1.png<br />
|description=<br />
}}<br />
<br />
<BR><br />
=Summary=<br />
<!--{{icon|Icon_Preware.png|float:right;}}--><br />
[[image:Icon_Preware.png|frameless|left]]<br />
Preware is a package management application for the Palm Pre and the Palm Pixi. Preware allows the user to install any package from any of the open standard package repositories on preware.org (or any other location that hosts an open standard package repository). Preware relies on a custom written service developed from community research which allows the mojo app to talk to the built-in ipkg tool.<br />
<br />
'''Preware requires webOS 1.4.0 or later to function. Do not try to install it on earlier webOS versions, it will not work.'''<br />
<br />
This application was the result of extensive community-based design in [[IPKG Service]] and [[Preware Design]].<br />
<br />
For application management, Preware can access more applications, and has more features, than any other on-device package installer.<br />
<br />
And since it is open source, and has a completely open development process supported by a team of world-class WebOS Internals developers, it will continue to get better much faster than any other package management application.<br />
<br />
Preware is the open application installer that has been written specifically to support a homebrew ecosystem where any developer can upload any application to any submission site, and that application can then be installed by any user. Developers no longer need to upload their applications to multiple submission sites, and users are no longer excluded from accessing applications from any open standard package repository.<br />
<br />
<BR><br />
===Key Features===<br />
Install / Remove / Update:<br />
*Homebrew Applications including advanced applications with special requirements. <br />
*WebOS Themes<br />
*Patches<br />
*webOS Kernels<br />
*Palm App Catalog Applications<br />
*Support for installation of signed packages<br />
<br />
<BR><br />
===Status===<br />
Preware has been upgraded to release status, and is no longer considered beta. <br />
<br />
Some milestones worth mentioning in Preware's history include:<br />
<br />
* Since 27 August 2009 it is the only over-the-air installer for the palm capable of installing advanced palm applications such as the [[On_Screen_Keyboard|On Screen Keyboard]] or the terminal application.<br />
* Since 27 August 2009 it is the only application supporting installation from all existing palm homebrew feeds. <br />
* Since 17 September 2009 it also supports installation of themes. <br />
* Since 8 October 2009 it also supports installation of webOS patches.<br />
* Since 12 Jan 2010 it also supports all Palm App Catalog feeds.<br />
* Since 3 May 2010 it also supports installation of webOS custom kernels.<br />
* Since 20 July 2010 it also supports installation of packages from URLs and local files.<br />
* Since 24 July 2010 is also supports blacklisting packages and authors.<br />
<br />
<BR><br />
===License===<br />
Please be aware that org.webosinternals.preware is licensed under the [http://www.gnu.org/licenses/gpl-2.0.html GPLv2].<br />
<br />
Code from Preware cannot be used by a closed source application. If you want to use them in a non-GPLv2 but otherwise open source application, please contact the [mailto:support@webos-internals.org authors].<br />
<br />
<BR><br />
=Installing Preware=<br />
<br />
There are three supported methods for installing Preware: WebOS Quick Install, Stand Alone Installers, and Command Line. <br />
<br />
You do not need to access the Linux command line or "root your Pre" to install or use Preware.<br />
<br />
You ''cannot'' use fileCoaster, or PreLoad, or PreUpdate to install or update Preware. Those tools are unable to operate correctly on advanced homebrew packages.<br />
<br />
If you are a developer who uses the Palm emulator, you should know that Preware works just as well on the Emulator as it does on a real device, and is installed in exactly the same way.<br />
<br />
<BR><br />
===Installing Preware on webOS 2.0===<br />
<br />
To install Preware on a webOS 2.0 device, the following procedure (or the command-line method) is recommended until WebOS Quick Install and other installation methods have been upgraded to support webOS 2.0:<br />
<br />
# Install the official Palm webOS 1.4.5 SDK<br />
# '''Disconnect your device''' (I repeat, do not have your device connected, no cables in the device, device not even anywhere near the computer), and run the webOS 2.0 Doctor to install or upgrade your Novacom drivers<br />
# Close the doctor<br />
# Your phone should remain disconnected<br />
# Download the latest Preware package onto your computer from http://get.preware.org/<br />
## To install Preware on a phone, download the 'arm' .ipk file<br />
## To install Preware on an emulator, download the 'i686' .ipk file<br />
# Typing webos20090606, select the developer mode icon that will appears, and verify that your phone is in developer mode<br />
# Connect your device to your computers USB port, and select 'Just Charge'<br />
# Use palm-install to install the package you downloaded<br />
## Typically you can simply get a command line, navigate to the directory with the Preware package you downloaded, then type palm-install and.the.package.arm.name.ipk<br />
<br />
<BR><br />
<br />
===Installing Preware with WebOS Quick Install===<br />
You can use version 3.14 or later of [http://forums.precentral.net/canuck-software/228310-webos-quick-install-v3-14-a.html WebOS Quick Install] to install Preware directly from the WebOS Internals feed.<br />
<br />
'''Latest Version of WebOS Quick Install available here: [http://forums.precentral.net/canuck-software/228310-webos-quick-install-v3-14-a.html WebOS Quick Install v3.14]'''<br />
<br />
# Install the required Software<br />
## [http://www.java.com/en/download/installed.jsp?detect=jre&try=1 Click here] to verify that you have the latest java installed on your computer and update if needed<br />
## [http://images.precentral.net/sites/precentral.net/files/webos-homebrew-apps/wosqi/WebOSQuickInstall.jar Click Here] to download the latest version of WebOS Quick Install<br />
## Optionally, [http://www.webos-internals.org/wiki/Webos_Doctor_Versions Click here] to download the current webOS Doctor for your carrier and phone in a subdirectory your will remember (maybe "Palm"?) and the same one in which WebOSQuickInstall will execute. If you already have it, skip this step.<br />
##* You do not need to download webOS Doctor separately unless you wish to do so, as WebOSQuickInstall will download it itself if not found. <br />
##* '''Do not run the webOS Doctor'''<br />
# Put your device in [[Getting started|Developer Mode]]<br />
# Connect your device to your computer with the USB cable, and select "Just Charge" (do not select USB Drive)<br />
# Run WebOS Quick Install. If webOS Doctor is not present, you will be asked if you wish to download it prior to execution.<br />
# Click the third button on the right (Blue Down Arrow)<br />
# Choose WebOS Internals Feed (Pre) or WebOS Internals Feed (Pixi) from the drop-down list at the top. <br />
# Select ''Preware'' from the list. <br />
# Click Download.<br />
# Click Close.<br />
# Click Install.<br />
<br />
<BR><br />
===Installing Preware with the Standalone Installer===<br />
Preware installers can be downloaded here: [http://get.preware.org Preware Standalone Installers]. These instructions are currently only for Mac and PC users.<br />
<br />
# Install the required software.<br />
## [http://www.java.com/en/download/installed.jsp?detect=jre&try=1 Click here] to verify that you have the latest version of Java installed on your computer and update it if needed.<br />
## [http://www.webos-internals.org/wiki/Webos_Doctor_Versions Click here] to download the current webOS Doctor for your carrier and phone in a subdirectory you will remember (maybe "Palm"?). If you already have it, skip this step.<br />
##* '''Do not run the webOS Doctor.'''<br />
# Put your device into [[Getting started|Developer Mode]].<br />
#* '''Windows users:''' When connecting your device to the computer for the first time, you will be prompted to install new hardware. Click Next to start the device installation. You may get a message regarding Novacom drivers not being installed. If so, you can disregard it. Once your device is installed, proceed with the Preware installation.<br />
# Download the [http://get.preware.org/ Preware Standalone Installer] (you should choose the latest file name PrewareInstaller-X.Y.Z.jar) and place it in the same directory as the webOS Doctor .jar file.<br />
# Run the Preware Installer.<br />
# Click on the Tools menu and choose Install Drivers. This will install the Palm Novacom drivers for webOS devices.<br />
# Once the drivers have finished installing, click on Install Preware. After Preware is installed, your device will be unresponsive for a few seconds while Luna restarts.<br />
<br />
<BR><br />
===Installing Preware from the Commandline===<br />
If you have access to the command line of your webOS Device or emulator using Terminal, Novaterm, the "Linux Commandline" in WebOS Quick Install, or other techniques, you can install Preware by typing three lines. This technique is always the shortest and in many ways the simplest, but if you are in any way unsure of operating at the Linux command line, please use either of the methods described above. <br />
<br />
<source lang="bash"><br />
cd /tmp<br />
wget http://bit.ly/preware-bootstrap<br />
sh preware-bootstrap</source><br />
<br />
<BR><br />
===Updating Preware===<br />
To update Preware, just run Preware and select "Package Updates" from the main scene. If an update to Preware is available, it will appear in the list. Then select the "Update" button. Preware will close automatically after the update is complete.<br />
<br />
Note that you cannot use fileCoaster, or PreLoad, or PreUpdate to install or update Preware. Those tools are unable to operate correctly on advanced homebrew packages.<br />
<br />
<BR><br />
<br />
===Removing Preware===<br />
''Why would you ever want to remove Preware?''<br />
<br />
To remove Preware, hold the Orange button on your keypad and choose Preware from the Launcher. Choose Delete.<br />
<br />
<BR><br />
=Usage=<br />
<br />
===Preferences===<br />
{| Width="70%" VAlign="top"<br />
|valign="top"|[[image:Preferences.png|160px|frameless|left|text-top]]<br />
|valign="top"|You can select preferences in the top left corner of the Pre to bring up the preferences screen. On the Preferences screen you can specify the look of the application, the frequency that feeds are updated, and what Preware will show you by default.<br />
<BR><br />
{| style="color:black; background-color:#F9F9F9;border:1px outset;" cellpadding="3" cellspacing="0"<br />
|TIP:<br />
|-<br />
|To make it easier to find things, set "Show Available Types" to yes. This will show separate categories (Applications/Themes/Patches/etc.) rather than show everything in one long list.<br />
|}<br />
|}<br />
<BR><br />
<br />
===Feed Management===<br />
{| Width="70%" VAlign="top"<br />
|valign="top"|[[image:Preware_feeds.png|160px|frameless|left|text-top]]<br />
|valign="top"|In the preferences section on the top bar on the right side is a button that takes you to the feeds screen. On the feeds screen you can select which feeds are loaded and which ones are not. Simply select the on or off button for that feed. (If you are not interested in themes you can disable the two feeds for themes to speed up the updating of feeds) Preware comes with the following feeds by default (some are disabled by default, but are easily enabled if desired). <br />
<br />
{| style="color:black; background-color:#FFFFE0;" cellpadding="3" cellspacing="0" Border="1"<br />
|align="center" colspan="4" | '''Default Feeds'''<br />
|-<br />
|align="center" | [http://ipkg.preware.org/feeds/palm-beta/ Palm Beta]<br />
|align="center" | [http://ipkg.preware.org/feeds/palm-beta-updates Palm Beta Updates]<br />
|align="center" | [http://ipkg.preware.org/feeds/palm-catalog/ Palm Catalog]<br />
|align="center" | [http://ipkg.preware.org/feeds/palm-catalog-updates/ Palm Catalog Updates]<br />
|-<br />
|align="center" | [http://ipkg.preware.org/feeds/palm-web-updates/ Palm Web]<br />
|align="center" | [http://ipkg.preware.org/feeds/palm-web-updates/ Palm Web Updates]<br />
|align="center" | [http://ipkg.preware.org/feeds/precentral/ PreCentral]<br />
|align="center" | [http://ipkg.preware.org/feeds/precentral-themes/ PreCentral Themes]<br />
|-<br />
|align="center" | [http://ipkg.preware.org/feeds/webos-internals/ WebOS Internals]<br />
|align="center" | [http://ipkg.preware.org/feeds/optware/ Optware]<br />
|align="center" | [http://ipkg.preware.org/feeds/webos-patches/ WebOS Patches]<br />
|align="center" | [http://ipkg.preware.org/feeds/webos-kernels/ WebOS Kernels]<br />
|-<br />
|}<br />
|}<br />
<br />
<br />
{| style="color:black; background-color:#F9F9F9;border:1px outset;" VAlign="middle" cellpadding="3" cellspacing="0" Width="70%"<br />
|align="center" | See [[Testing Feeds]] for detailed instructions on adding custom feeds.<br />
|}<br />
<BR><br />
<br />
===Package Updates===<br />
{| Width="70%" VAlign="top"<br />
|valign="top"|[[image:UpdateFeeds.png|160px|frameless|left|text-top]]<br />
|valign="top"|To update feeds, simply select "Update Feeds" from the Application Menu. Preware will download the package list information from your enabled feeds. After processing the data, you will be back at the main list of available items.<br />
|}<br />
<BR><br />
<br />
===Installing Packages===<br />
{| Width="70%" VAlign="top"<br />
|valign="top"|[[image:SelectApp.png|160px|frameless|left|text-top]]<br />
|valign="top"|There are a few ways to select and install a "package" (application/patch/theme/etc.). Using "List of Everything" would be the simplest.<br />
#Find the package you want to install either by scrolling and tapping on it, or just start typing<br />
#Tap the "Install" button that the bottom of the package's page to install.<br />
|}<br />
<BR><br />
<br />
===Removing Packages===<br />
{| Width="70%" VAlign="top"<br />
|valign="top"|[[image:RemoveAppTap.png|160px|frameless|left|text-top]]<br />
|valign="top"|Removing a package is just as easy.<br />
#On the main screen, tap "Installed Packages", then the category of the package you want to remove<br />
#Tap the Package you want to remove<br />
#Tap the "Remove" button that the bottom of the package's page.<br />
|}<br />
<BR><br />
<br />
===Blacklist (Category Filters)===<br />
{| Width="70%" VAlign="top"<br />
[[File:preware_2011-09-03_165038.png]]''' '''[[File:preware_2011-09-03_165049.png]]<br />
|valign="top"|The Preware "Blacklist" is a tool used to hide packages (applications, patches, etc) that you do not want to see, such as mass-produced book apps or real estate apps. This tool can also be used to hide unavailable packages, such as patches that are not compatible with your current webOS version. Got to Preferences in Preware and scroll to the Blacklist section. You can add whatever filters you like to customize your Preware experience. To hide all apps from a particular Maintainer, choose a "Maintainer" filter with the package maintainer in the search field. To hide unavailable packages, choose a "Category" filter, with "Unavailable" in the search field.<br />
<BR><br />
<br />
<br />
<br />
{| style="color:black; background-color:#F9F9F9;border:1px outset;" cellpadding="3" cellspacing="0"<br />
<br />
<!--<br />
=== Applications ===<br />
=== Themes ===<br />
=== Patches ===<br />
=== Installed Packages ===<br />
=== List of Everything ===<br />
=== Saved Package List ===<br />
--><br />
<br />
= Operating notes =<br />
<br />
===Limitations===<br />
No known limitations.<br />
<br />
<BR><br />
===Known bugs===<br />
*When selecting a patch with dependencies, if you view those dependencies then install them, when Preware returns you to the original patch's screen it will still have the 'install' button showing even though it is installed successfully. Swiping back and returning will show the correct status.<br />
<br />
*The Update All button can get confused if there are patches with complex dependencies. This will be fixed in a future version.<br />
<br />
*If updates to App Catalog applications are pending, they will be silently skipped when using the Update All button.<br />
<br />
*The Updates feature from the regular Palm Launcher, may claim that application updates are needed, and then when the user clicks Show Updates shows the App Catalog's installed applications, there are none shown that need updating. This isn't as expected. This is because an app that was previously only in Preware has now migrated to the Palm Catalog. Don't worry, your apps are up to date (with the possible exception of the one with the conflict.) This is not a bug in Preware per se' but an app version conflict because the app is in both the Palm Catalog and also in Homebrew. Notice that you don't need to remove Preware to install the app from the official catalog, but simply disable the feed in Preware then "update feeds" to refresh the list then it should install fine from the official app catalog.<br />
<br />
<BR><br />
=Changelog=<br />
<BR><br />
For those interested, the full Changelog can be [http://git.webos-internals.org/?p=applications/preware.git;a=tags found here]. Listed below is the Changelog since the 1.0 milestone.<br />
<BR><BR><br />
<br />
;1.5.0:<br />
* You must upgrade to this version for full webOS 2.0 compatibility.<br />
<br />
;1.4.9:<br />
* Better compatibility with unknown future webOS versions.<br />
<br />
;1.4.8:<br />
<br />
* Now calls the correct software manager updates screen on webOS 2.0.<br />
<br />
; 1.4.7:<br />
* Fixed update, install and remove status messages on webOS 2.0.<br />
<br />
;1.4.6:<br />
* New "App Catalog" theme preferences thanks to Garrett92C.<br />
* Added support for "MaxWebOSVersion" in the feeds.<br />
<br />
;1.4.5:<br />
* Added support for identifying when running on a Pre 2 device.<br />
<br />
;1.4.4: <br />
* Updated the version check to support future webOS versions.<br />
<br />
;1.4.2:<br />
* Added Category as a blacklist option.<br />
<br />
;1.4.1:<br />
* Added a Changelog button to the Help scene.<br />
<br />
;1.4.0:<br />
* Added help to preferences scene.<br />
* Fixed swipe-to-delete bug in blacklist.<br />
* Updated Italian translations (courtesy of Darkmagister).<br />
* Added "Get Info" button to package install scene.<br />
* Added "Send" button to ipkg log scene.<br />
* Fixed bug when loading large package descriptions.<br />
<br />
;1.3.8:<br />
* Updated French translations (courtesy of Yannick LE NY).<br />
<br />
;1.3.6:<br />
* Preware now supports installation of application package files (.ipk files) directly from URLs, email attachments, and local files.<br />
* Also supported are Send to Preware links on homebrew application gallery and news websites (this requires the Neato! application to also be installed).<br />
* If Preware continually asks you about file associations on every single launch, even after you have answered Yes to the questions it asks, then you may have a damaged file association table and will need to run the Emergency MimeTable Reset tool and then reboot to repair it.<br />
<br />
;1.3.5:<br />
* Updated German translations.<br />
<br />
;1.3.3:<br />
* Always ask the user before modifying the file association list.<br />
* Updated French translations. <br />
<br />
;1.3.1:<br />
* Check whether Preware is the default application for handling packages, and advise the user if it is not.<br />
<br />
;1.3.0:<br />
* Added Preware to the Default Applications list to allow for installing packages from email messages and the browser.<br />
<br />
;1.2.9:<br />
* Fixed the Saved Package List swipe to delete bug.<br />
<br />
;1.2.8:<br />
* Open the My Applications app catalog screen when multiple app catalog applications need updating.<br />
<br />
;1.2.7<br />
* Fixed the Install Package problem when running on the emulator.<br />
<br />
;1.2.6<br />
* Remove most of the curl download progress messages from the ipkg log (this fixes a buffer overrun crash).<br />
<br />
;1.2.5<br />
* Added Ask At Launch option to update preference.<br />
* Added Blacklist support.<br />
* German Translation updates.<br />
* Fixed update banner problem.<br />
* Fixed package with too many dependent packages problem.<br />
<br />
;1.2.4<br />
* Added support for MinWebOSVersion, DeviceCompatibility and PreActionMessage package attributes.<br />
<br />
;1.2.3<br />
* Enable the Install Package feature to also work for incorrectly formatted filenames.<br />
<br />
;1.2.1<br />
* Robustified the Install Package feature - will now run post-install scripts for all correctly formatted filenames (packageid_version_arch.ipk).<br />
<br />
;1.2.0<br />
* Added Install Package functionality, allowing installation of packages from URLs and local files.<br />
* Moved Saved Package List from the main screen to the app menu.<br />
<br />
;1.1.7<br />
* Added support for Kernel Modules.<br />
<br />
;1.1.5<br />
* Use a gentler reboot procedure to allow open files to be flushed to disk.<br />
<br />
;1.1.4<br />
* Fixed hang on package download failures.<br />
<br />
;1.1.2 <br />
*Added support for the ENABLE_TESTING_FEEDS Meta-Doctor feature.<br />
*Removed the tag line about eventually reaching 1.0.<br />
*Minor French translation updates, courtesy of Yannick LE NY.<br />
<br />
;1.1.1<br />
*Added languages field in package descriptions. <br />
*Added preference to only show packages with English descriptions.<br />
<br />
;1.1.0<br />
*Now defaults (selectable by a preference option) to using an alternative installation method to avoid the webOS 1.4 rescan bug which closes and stops notifications from your phone, email and messaging applications. <br />
*Updated German and French translations.<br />
*Fixed deletion of disabled feeds. <br />
*Added service version number to the ipkgservice API. Robustified the service upgrade process.<br />
<br />
;1.0.0<br />
*The Package Manager Service has been rewritten in C and incorporated into this single Preware package.<br />
*Installing Preware 1.0.0 will remove the Package Manager Service as the last step of the upgrade process.<br />
<br />
<BR><br />
=Repository=<br />
Preware and the Package Manager Service are housed in the applications/preware git repository at http://git.webos-internals.org/<br />
<br />
For more information getting your application published in the WebOS Internals Source Code Repositories, please see the [[WebOS Internals Source Code Repositories]] page. For commit permission to the open source project, contact rwhitby on #webos-internals or email [mailto:support@webos-internals.org support@webos-internals.org]</div>Reeder.29http://wiki.webos-internals.org/index.php?title=Comparison_of_Editors&diff=7765Comparison of Editors2009-12-10T18:29:06Z<p>Reeder.29: added Miller's JavaScript Lint</p>
<hr />
<div>This page is mostly used for developers to extend the editors so that they compete with one another and that all editors get new features for webOS development.<br />
<br />
Please help fill in the question marks('''?''').<br />
<br />
<table cellpadding="2" cellspacing="0" width="100%" style="text-align:left;border:1px solid #d4d4d4;"><br />
<tr style="background-color:#F1F1F1;"><br />
<th style="border-bottom:1px dotted #d4d4d4;">Feature</th><br />
<th colspan="5" style="text-align:center;border-bottom:1px dotted #d4d4d4;">Editor</th><br />
<tr><br />
<tr style="background-color:#F1F1F1;"><br />
<th style="border-bottom:1px solid #d4d4d4;">-</th><br />
<th style="border-bottom:1px solid #d4d4d4;">[[Komodo|Komodo Edit]]</th><br />
<th style="border-bottom:1px solid #d4d4d4;">Eclipse</th><br />
<th style="border-bottom:1px solid #d4d4d4;">TextMate</th><br />
<th style="border-bottom:1px solid #d4d4d4;">VIM</th><br />
<th style="border-bottom:1px solid #d4d4d4;">Emacs</th><br />
<tr><br />
<tr><br />
<td style="background-color:#F1F1F1;" colspan="6">'''Base'''</td><br />
</tr><br />
<tr><br />
<td>Cross Platform</td><br />
<td style="background-color:#CEF2E0;">✔ Windows, Linux, Macintosh</td><br />
<td style="background-color:#CEF2E0;">✔ Windows, Linux, Macintosh</td><br />
<td>✘ Macintosh Only</td><br />
<td style="background-color:#CEF2E0;">✔ Windows, Linux, Macintosh</td><br />
<td style="background-color:#CEF2E0;">✔ Windows, Linux, Macintosh</td><br />
</tr><br />
<tr><br />
<td>Price</td><br />
<td style="background-color:#CEF2E0;">✔ Free Download</td><br />
<td style="background-color:#CEF2E0;">✔ Free Download</td><br />
<td>'''?'''</td><br />
<td style="background-color:#CEF2E0;">✔ Free Download</td><br />
<td style="background-color:#CEF2E0;">✔ Free Download</td><br />
</tr><br />
<tr><br />
<td>Multiple Projects</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
<td>'''?'''</td><br />
<td>'''-'''</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
</tr><br />
<tr><br />
<td>JavaScript Code Completion</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
<td>'''?'''</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
</tr><br />
<tr><br />
<td>Other Key Bindings</td><br />
<td>Vi, Emacs</td><br />
<td>Vi via plugin</td><br />
<td>'''?'''</td><br />
<td></td><br />
<td>vi via viper-mode</td><br />
</tr><br />
<tr><br />
<td style="background-color:#F1F1F1;" colspan="6">'''Basics'''</td><br />
</tr><br />
<tr><br />
<td>Mojo Code Completion</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
</tr><br />
<tr><br />
<td>New webOS Project</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
</tr><br />
<tr><br />
<td>New Scene</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
</tr><br />
<tr><br />
<td colspan="6" style="background-color:#F1F1F1;">'''Add-on / Plugin / Scripts'''</td><br />
</tr><br />
<tr><br />
<td>Key Bindings</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
</tr><br />
<tr><br />
<td>One Action Task - Emulator</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
</tr><br />
<tr><br />
<td>➔ Package, Install, Launch</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
</tr><br />
<tr><br />
<td>➔ Package, Install, Inspect</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
</tr><br />
<tr><br />
<td>➔ Remove Application</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
</tr><br />
<tr><br />
<td>➔ Launch Application</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
</tr><br />
<tr><br />
<td>➔ Close Application</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
</tr><br />
<tr><br />
<td>➔ Hard Reset</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
</tr><br />
<tr><br />
<td>One Action Task - Device</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
</tr><br />
<tr><br />
<td>➔ Package, Install, Launch</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
</tr><br />
<tr><br />
<td>➔ Remove Application</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
</tr><br />
<tr><br />
<td>➔ Launch Application</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
</tr><br />
<tr><br />
<td>➔ Close Application</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
</tr><br />
<br />
<tr><br />
<td style="background-color:#F1F1F1;" colspan="6">'''Quickly switch to related files'''</td><br />
</tr><br />
<tr><br />
<td>Main view ➔ Assistant</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
</tr><br />
<tr><br />
<td>Assistant ➔ main view</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
</tr><br />
<tr><br />
<td>Any view ➔ next view in scene</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
</tr><br />
<tr><br />
<td>Any view ➔ assistant</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
</tr><br />
<tr><br />
<td>Any file ➔ appinfo.json</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
</tr><br />
<tr><br />
<td>Any file ➔ sources.json</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
</tr><br />
<tr><br />
<td>Any file ➔ main stylesheet</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
</tr><br />
<tr><br />
<td>Any file ➔ index.html</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
</tr><br />
<br />
<tr><br />
<td style="background-color:#F1F1F1;" colspan="6">'''Manage framework_config.json'''</td><br />
</tr><br />
<tr><br />
<td>Display values<br/>(logLevel, debuggingEnabled, etc)</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
</tr><br />
<tr><br />
<td>Change values<br/>(logLevel, debuggingEnabled, etc)</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td style="background-color:#CEF2E0;">✔</td><br />
</tr><br />
<br />
<tr><br />
<td style="background-color:#F1F1F1;" colspan="6">'''Other'''</td><br />
</tr><br />
<tr><br />
<td>JSLint</td><br />
<td style="background-color:#CEF2E0;">✔ Included in Add-on</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td style="background-color:#CEF2E0;">[http://github.com/hallettj/jslint.vim/tree/master ✔ via plugin]</td><br />
<td style="background-color:#CEF2E0;">✔ via plugin</td><br />
</tr><br />
<tr><br />
<td>[http://www.javascriptlint.com/ JavaScript Lint]</td><br />
<td>'''?'''</td><br />
<td style="background-color:#CEF2E0;">✔ as External Tool</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
</tr><br />
<tr><br />
<td>Task Manager</td><br />
<td style="background-color:#CEF2E0;">✔ Included in Add-on</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
<td>'''?'''</td><br />
</tr><br />
</table></div>Reeder.29http://wiki.webos-internals.org/index.php?title=Mojo_Identify_Device&diff=7764Mojo Identify Device2009-12-10T18:13:27Z<p>Reeder.29: </p>
<hr />
<div>To tell if you are running on a Pre or a Pixie or some other future WebOS device use this call: <br />
<br />
<br />
''Mojo.Environment.DeviceInfo'' <br />
<br />
It should give you back an object something along the lines of this:<br />
<br />
<pre>{ "modelName": "Pr?", <br />
"modelNameAscii": "Pre",<br />
"platformVersion": "1.3.1", <br />
"platformVersionMajor": 1,<br />
"platformVersionMinor": 3,<br />
"platformVersionDot": 1,<br />
"carrierName": "Sprint", <br />
"serialNumber": "Unknown", <br />
"screenWidth": 320, <br />
"screenHeight": 480, <br />
"minimumCardWidth": 320, <br />
"minimumCardHeight": 188, <br />
"maximumCardWidth": 320, <br />
"maximumCardHeight": 424, <br />
"keyboardAvailable": true, <br />
"touchableRows": 8,<br />
"keyboardAvailable": true<br />
"keyboardSlider": true, <br />
"keyboardType": "QWERTY", <br />
"wifiAvailable": true, <br />
"bluetoothAvailable": true,<br />
"coreNaviButton": true }<br />
</pre><br />
<br />
The documented values (as of 2009/12/10) are<br />
<pre>{"screenWidth": INT (px), <br />
"screenHeight": INT (px), <br />
"minimumCardWidth": INT (px), <br />
"minimumCardHeight": INT (px), <br />
"maximumCardWidth": INT (px), <br />
"maximumCardHeight": INT (px), <br />
"keyboardType": STRING, <br />
"touchableRows": INT} <br />
</pre><br />
I would guess that the other fields probably won't go away or change in weird ways, but one can't be certain.<br />
<br />
<br />
Mojo.Environment.build holds a number like 200.47 (for a Sprint Pre, 1.3.1).</div>Reeder.29http://wiki.webos-internals.org/index.php?title=Mojo_Identify_Device&diff=7763Mojo Identify Device2009-12-10T18:05:02Z<p>Reeder.29: Added list of documented fields.</p>
<hr />
<div>To tell if you are running on a Pre or a Pixie or some other future WebOS device use this call: <br />
<br />
<br />
''Mojo.Environment.DeviceInfo'' <br />
<br />
It should give you back an object something along the lines of this:<br />
<br />
<pre>{ "modelName": "Pr?", <br />
"platformVersion": "1.0.2", <br />
"carrierName": "Sprint", <br />
"serialNumber": "Unknown", <br />
"screenWidth": 320, <br />
"screenHeight": 480, <br />
"minimumCardWidth": 320, <br />
"minimumCardHeight": 188, <br />
"maximumCardWidth": 320, <br />
"maximumCardHeight": 424, <br />
"keyboardAvailable": true, <br />
"keyboardSlider": true, <br />
"keyboardType": "QWERTY", <br />
"wifiAvailable": true, <br />
"bluetoothAvailable": true }<br />
</pre><br />
<br />
The documented values (as of 2009/12/10) are<br />
<pre>{"screenWidth": INT (px), <br />
"screenHeight": INT (px), <br />
"minimumCardWidth": INT (px), <br />
"minimumCardHeight": INT (px), <br />
"maximumCardWidth": INT (px), <br />
"maximumCardHeight": INT (px), <br />
"keyboardType": STRING, <br />
"touchableRows": INT} <br />
</pre><br />
I would guess that the other fields probably won't go away or change in weird ways, but one can't be certain.</div>Reeder.29