Difference between revisions of "Netbook"

From WebOS Internals
Jump to navigation Jump to search
(added Areas of Concern & Tools)
Line 10: Line 10:
  
 
== Goals ==
 
== Goals ==
* Demonstration of standard webOS apps running on a netbook
+
* normal use of standard webOS apps on a netbook
 
* packaging open-source webOS to make installing it as easy as it can be.
 
* packaging open-source webOS to make installing it as easy as it can be.
  
Line 25: Line 25:
 
* CPU board: http://www.alwaysinnovating.com/wiki/index.php/MID_board without the Smart Book components
 
* CPU board: http://www.alwaysinnovating.com/wiki/index.php/MID_board without the Smart Book components
 
* Tablet module: http://www.alwaysinnovating.com/wiki/index.php/Smart_Book_specs without the Mini Book
 
* Tablet module: http://www.alwaysinnovating.com/wiki/index.php/Smart_Book_specs without the Mini Book
* install another OS page: http://www.alwaysinnovating.com/wiki/index.php/Install_another_OS
+
* install another (ARM-based) OS page: http://www.alwaysinnovating.com/wiki/index.php/Install_another_OS
  
  
Line 38: Line 38:
 
===Not Possible===
 
===Not Possible===
 
chromebooks (no touchscreen)
 
chromebooks (no touchscreen)
 +
 +
==Areas of Concern==
 +
* low-level touch screen driver
 +
* gstreamer; what codecs are already available?
 +
 +
==Tools==
 +
* OpenEmbedded and Debian build systems

Revision as of 20:56, 10 December 2011

Porting webOS to a touchscreen ARM netbook

Motivation

webOS is designed for users to search data and create new data, by means of a keyboard built in to each phone. Typedown filter lists allow users to quickly find an item amid thousands. Netbooks marry the high-input-bandwidth of a keyboard to the high (for a mobile device) output bandwidth output of a display. Netbooks running a desktop OS have stalled, because mobile design is different than desktop design. 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. Netbooks are ideal for command-line use.

Goals

  • normal use of standard webOS apps on a netbook
  • packaging open-source webOS to make installing it as easy as it can be.

Hardware

First priority is to identify suitable hardware, with a multitouch screen. We need to find an initial target platform that is currently available.


What kind of graphics chips can be made to work?


Possible

Always Innovating Touch Book Netbook v2 The company is all about open hardware and varying OSs.


Asus EEE Pad Transformer

SG-TPC TPC0801 Can't find mfg page, which would make it a poor initial target.

Toshiba AC 100 Toshiba's site doesn't acknowledge this, so it may have been discontinued.

Not Possible

chromebooks (no touchscreen)

Areas of Concern

  • low-level touch screen driver
  • gstreamer; what codecs are already available?

Tools

  • OpenEmbedded and Debian build systems