WebOS Internals - User contributions [en]

Nintendo

2009-11-30T18:29:56Z

Enormous: /* Launching from within Webos */ - added info on "More Standby Times" patch

[[Image:Nintendo.png|right]]

NOTE: As of 2009/9/17 Directfb 1.2, SDL 1.2 and FCEUX 2.1.1 have ipks that can be installed using Preware! [[User:PuffTheMagic|PuffTheMagic]] 16:09, 17 September 2009 (UTC)

Nintendo emulation is now possible without having to run "Classic" for WebOS. Simply compile [http://fceux.com/web/htdocs/download.php FCEUltra] from within a Debian chroot.

= Demos=
* [http://www.youtube.com/watch?v=lYxAEEHsmeE Video of game being played]
* [http://www.youtube.com/watch?v=agBx8PHzW-k Video of games being played. Launched from Webos]
* [http://i40.tinypic.com/157fc45.png Unmodified version of image @ right]

= Installation=

1. Type the following in a [[Debian]] chroot, as root:

<pre><nowiki>
apt-get install bzip2 gcc g++ scons libsdl1.2-dev libsdl1.2debian-esd liblua5.1-dev zlib1g-dev zenity
</nowiki></pre>

2. Extract the bz2 using bunzip2, then extract the tar by typing the following:

<pre><nowiki>
bunzip2 fceux-2.1.0a.src.tar.bz2
tar xvf fceux-2.1.0a.src.tar
</nowiki></pre>

3. Switch to the source path:

<pre><nowiki>
cd /fceu
</nowiki></pre>

4. Compile the program from source by typing the following:

<pre><nowiki>
scons install
</nowiki></pre>

When done compiling, the program is copied to /usr/local/bin. When you first load the application, a configuration directory is created in your $HOME path. Modify this file as needed.
Using the instructions [[directfb | here]], install and configure directfb. Some program specific notes about the directfbrc config file:

<pre><nowiki>
mode=320x480
scaled=320x480 #Insert this line to run games at full screen at the sacrifice of framerate.
primary-layer=00
pixelformat=ARGB
no-vt
no-cursor
bg-color=00000000
hardware
</nowiki></pre>

6. Run the following command:

<pre><nowiki>
export SDL_VIDEODRIVER='directfb'
</nowiki></pre>

7. Run the following command to configure the key mappings:

<pre><nowiki>
fceux --inputcfg gamepad /usr/games/<insert favorite nes.rom>
</nowiki></pre>

8. Outside the Debian chroot, type the following command to shutdown the LunaSysMgr:

<pre><nowiki>
/sbin/initctl stop LunaSysMgr #NOTE: THIS WILL KILL THE WEBOS GUI.
</nowiki></pre>

9. Play your favorite games by typing the following command:

<pre><nowiki>
fceux --sound 0 --bpp 8 --frameskip 2 /usr/games/<insert favorite nes.rom>
</nowiki></pre>

10. When finished playing, you can re-enable the LunaSysMgr by typing the following outside the Debian chroot:

<pre><nowiki>
/sbin/initctl start LunaSysMgr
</nowiki></pre>

= Launching from within Webos =

The emulator can be launched from the Mojo Webos [[Application:Terminal|Terminal]] app, which can be downloaded from [[Preware|Preware]]. The emulator even works with Luna on, meaning you can launch it from the Webos Terminal, and receive calls even when playing a game. To exit games when playing like this, press the orange button to return to normal Webos function.

However, with Luna on, the Webos GUI functions will turn off the screen and go into sleep mode after a period of time, which causes the emulator to crash. This period of time is defined in the Webos 'Screen & Lock' application under 'Turn Off After'. A workaround is to either tap the screen periodically before the screen turns off, use the "disable screen timer" functionality in the Webos app "Mytether", or use the "More Standby Times" patch that can also be applied using [[Preware|Preware]] (original patch notes [[Patch_webOS_Changing_the_"Turn_off_after_X"_time| available here]].

EBook-Reader

2009-08-17T17:28:02Z

Enormous: /* Features Wish List */

===Application description from a users perspective ===
Scene 1: Splash image and 3 buttons: [[Image: Scene1.png|thumb|right]]

.. Where I left off ... -- Opens the last book you read at the place you stopped.

.. Bookmarks ... -- opens a list of the books you have bookmarks in and lets you open them to there. -- previews 2 lines above and below bookmark.

... Library ... -- opens a scrollable page of "shelves" Each shelf has a label which is user defined, and each shelf presents the books on it as a coverflow. Books can be moved between shelves by dragging and dropping. Each shelf has a context menu to control order, title, author or user defined. If user defined menu will present shelf as a draggable list instead of a coverflow when you want to re-order books. backswipe returns to coverflow.

in either the bookmarks view, tapping a book takes you to either the bookmark or the title page. upswipe downswipe provide smooth scrolling. Left and right swipe provide page at a time scrolling. Back swipe in gesture offers to bookmark with a dialog and returns to the shelf you came from.

When on a book, top left menu presents presentation options, which can be set book by book or globally. Type face (if I can figure out how), size, leading, justification, colors etc..

Images default to no larger than 1/4 screen, but touch results in lightbox like zoom.

Menu at splash or library offers import, and delete of books. When in a shelf, books can be deleted by dragging them to the recycle.

===Features Wish List===
# on-pc conversion of various formats to pre-compatible format -probably using plucker distiller. Should support
## html
## rde
## doc
## m4b
## pdb (palm-doc)
## pdb (isilo), prc (unencrypted mobipocket)
## prc (encrypted) # lots of people with a ton of fictionwise books want this
## epub [http://en.wikipedia.org/wiki/EPUB]
## plain text
## plucker
## .lit
# on Pre conversion of html and text docs by download from the cloud.
# Library supports user definable catagories for sorting and shelving
#: Shelves can be user defined to hold any collection of books a reader cares to:
#* By author
#* By Genre
#* By Geography
#* By cover color
#* By Series # very useful to group books in a series together
#: The ''user'' should define the sorting catagories. Shelf design can initially be a scroll list like the Contacts app.
# Book display page is minimally invasive making the most space available to read on as possible
# Typography is bifocal friendly. User definable print sizes, and if possible type faces.
# user defined foreground/background colors for text.
## Sepia
## Night mode
## Adjust screen brightness
# multiple bookmarks per doc.
# shallow menus
# smooth scrolling or page-at-a-time scrolling by gestures.
## plucker style button-based scrolling
## swipe gesture based scrolling
## auto-scrolling with user adjustable speed
### Pause auto-scrolling by tapping gesture area
## page turn on screen tap option
# support for covers.
# coverflow view of shelves.
# easy rapid sorting of books onto shelves.
# Change text size
# Possibly be able to add books over Wi-Fi
# Copy & Paste words
## Dictionary search implemented

===Data Structure===

'''Table: Catalog'''
* catalogId: (globally unique ID - a system generated number)
* Title: string
* Author: string
* Genre: string
* catalogType: (B,S - book or series)
* ShelfId:
* CoverImage: Filename
* Encrypted: boolean
* Format: string (book format)

'''Table: BookSeries'''
* bookseriesId: (globally unique ID - a system generated number)
* catSeriesId: (must be present in book table and the catType must be 'S')
* catBookId: (must be present in book table and the catType must be 'B')

'''Table: Bookmarks'''
* bkmkId:
* bookId: (must be present in book table)
* Position: ( an integer, refering to the character in the file at the top of the screen.)

'''Table: BookShelf'''
* shelfId:
* ShelfName:
* ShelfOrder: (A, T, or U) Representing Author, Title or User Set

'''Table ShelfOrder'''
* shelfId:
* bookId:
* position: (integer representing the position of this book on this shelf)

'''Table: BookText'''
* BookId:
* BookText:

====Data Issues====

* This structure does not provide for books stored as chapters. This structure presumes a book is a single document. That document might have internal chapter indicators, but this structure does not divide the book up.
* This structure makes no provision for the internal storage of images.
* Should we actually store the text of the book in the DB or do we leave the book on the file system and just store a link to it?

There is some point, therefore to consider if in booktext, we want to simply store a plucker file, which CAN contain images and text intermingled.

====Book Format Issues====
* Can javascript on the device natively parse/navigate all of the above list formats?
** '''No.'''
* Can javascript on the device effectively parse/navigate the plucker format (if we settle on this one), or do we need our own format?
** '''Perhaps.''' plucker decoding sources in JAVA at http://www.fbreader.org/downloads.php
** Possible ePub since it's basically XHTML?
* Once we settle on a format, will the device be powerful enough to convert other formats to this one, or will we need a PC app to do the converting?
** on pc app
** some scripts found so far:
*** ereader2html -- python app, same as plucker converters.
*** pdbshred -- Binary app for unencrypting secure palm reader pdb's. Sorry.
*** (include others as you find them)
* Has anyone found a free and open source method to unzip files or data streams in javascript??
** all i have found is a page that refers to the huffman compression technique (http://rumkin.com/tools/compression/compress_huff.php), but i don't know if that is how epub files are zipped and i don't know if we can get our hands on the source.
**: note that this page says that compressing 15K takes MINUTES... ooops. :-( Not going to work

EBook-Reader

2009-08-17T17:27:26Z

Enormous: /* Features Wish List */

===Application description from a users perspective ===
Scene 1: Splash image and 3 buttons: [[Image: Scene1.png|thumb|right]]

.. Where I left off ... -- Opens the last book you read at the place you stopped.

.. Bookmarks ... -- opens a list of the books you have bookmarks in and lets you open them to there. -- previews 2 lines above and below bookmark.

... Library ... -- opens a scrollable page of "shelves" Each shelf has a label which is user defined, and each shelf presents the books on it as a coverflow. Books can be moved between shelves by dragging and dropping. Each shelf has a context menu to control order, title, author or user defined. If user defined menu will present shelf as a draggable list instead of a coverflow when you want to re-order books. backswipe returns to coverflow.

in either the bookmarks view, tapping a book takes you to either the bookmark or the title page. upswipe downswipe provide smooth scrolling. Left and right swipe provide page at a time scrolling. Back swipe in gesture offers to bookmark with a dialog and returns to the shelf you came from.

When on a book, top left menu presents presentation options, which can be set book by book or globally. Type face (if I can figure out how), size, leading, justification, colors etc..

Images default to no larger than 1/4 screen, but touch results in lightbox like zoom.

Menu at splash or library offers import, and delete of books. When in a shelf, books can be deleted by dragging them to the recycle.

===Features Wish List===
# on-pc conversion of various formats to pre-compatible format -probably using plucker distiller. Should support
## html
## rde
## doc
## m4b
## pdb (palm-doc)
## pdb (isilo), prc (unencrypted mobipocket)
## prc (encrypted) # lots of people with a ton of fictionwise books want this
## epub [http://en.wikipedia.org/wiki/EPUB]
## plain text
## plucker
## .lit
# on Pre conversion of html and text docs by download from the cloud.
# Library supports user definable catagories for sorting and shelving
#: Shelves can be user defined to hold any collection of books a reader cares to:
#* By author
#* By Genre
#* By Geography
#* By cover color
#* By Series # very useful to group books in a series together
#: The ''user'' should define the sorting catagories. Shelf design can initially be a scroll list like the Contacts app.
# Book display page is minimally invasive making the most space available to read on as possible
# Typography is bifocal friendly. User definable print sizes, and if possible type faces.
# user defined foreground/background colors for text.
## Sepia
## Night mode
## Adjust screen brightness
# multiple bookmarks per doc.
# shallow menus
# smooth scrolling or page-at-a-time scrolling by gestures.
## plucker style button-based scrolling
## swipe gesture based scrolling
## auto-scrolling with user adjustable speed
## page turn on screen tap option
### Pause auto-scrolling by tapping gesture area
# support for covers.
# coverflow view of shelves.
# easy rapid sorting of books onto shelves.
# Change text size
# Possibly be able to add books over Wi-Fi
# Copy & Paste words
## Dictionary search implemented

===Data Structure===

'''Table: Catalog'''
* catalogId: (globally unique ID - a system generated number)
* Title: string
* Author: string
* Genre: string
* catalogType: (B,S - book or series)
* ShelfId:
* CoverImage: Filename
* Encrypted: boolean
* Format: string (book format)

'''Table: BookSeries'''
* bookseriesId: (globally unique ID - a system generated number)
* catSeriesId: (must be present in book table and the catType must be 'S')
* catBookId: (must be present in book table and the catType must be 'B')

'''Table: Bookmarks'''
* bkmkId:
* bookId: (must be present in book table)
* Position: ( an integer, refering to the character in the file at the top of the screen.)

'''Table: BookShelf'''
* shelfId:
* ShelfName:
* ShelfOrder: (A, T, or U) Representing Author, Title or User Set

'''Table ShelfOrder'''
* shelfId:
* bookId:
* position: (integer representing the position of this book on this shelf)

'''Table: BookText'''
* BookId:
* BookText:

====Data Issues====

* This structure does not provide for books stored as chapters. This structure presumes a book is a single document. That document might have internal chapter indicators, but this structure does not divide the book up.
* This structure makes no provision for the internal storage of images.
* Should we actually store the text of the book in the DB or do we leave the book on the file system and just store a link to it?

There is some point, therefore to consider if in booktext, we want to simply store a plucker file, which CAN contain images and text intermingled.

====Book Format Issues====
* Can javascript on the device natively parse/navigate all of the above list formats?
** '''No.'''
* Can javascript on the device effectively parse/navigate the plucker format (if we settle on this one), or do we need our own format?
** '''Perhaps.''' plucker decoding sources in JAVA at http://www.fbreader.org/downloads.php
** Possible ePub since it's basically XHTML?
* Once we settle on a format, will the device be powerful enough to convert other formats to this one, or will we need a PC app to do the converting?
** on pc app
** some scripts found so far:
*** ereader2html -- python app, same as plucker converters.
*** pdbshred -- Binary app for unencrypting secure palm reader pdb's. Sorry.
*** (include others as you find them)
* Has anyone found a free and open source method to unzip files or data streams in javascript??
** all i have found is a page that refers to the huffman compression technique (http://rumkin.com/tools/compression/compress_huff.php), but i don't know if that is how epub files are zipped and i don't know if we can get our hands on the source.
**: note that this page says that compressing 15K takes MINUTES... ooops. :-( Not going to work