logview 1.0 b6:
  a GP2X Wiz log viewer,
  (c) JustBurn 2009

Audience:
  Developers

Purpose:
  Displays one or several text files,
  which happen to exist and also aren't
  empty. Using this tool is obviously a
  lot quicker than mounting, browsing,
  and finally opening the log files by
  yourself.
  
  Just hand your log files (or just the
  stderr one) to this utility after
  running your application and you'll be
  able see what went wrong without
  further delays, if something did
  indeed went wrong. During development
  this seems to happen rather often.

General usage:
  logview <file1> [file2 ... fileN]

Usage example:
  logview stderr.log stdout.log
  
  (This opens stderr.log first, then
  stdout.log.)

Keys:
  left/right or L/R:
    previous/next file
    
    (Right/R closes the application if
    the last file is currently viewed.)

  up/down:
    goes to the beginning/scrolls down
    
    (If the end of the file was already
    reached [blue "<< EOF"] it goes to
    the next file. If there isn't any it
    quits.)

  menu/select:
    quits

  any other key:
    same as down

Example dev gpe file with one log file:
----------------------------------------
#!/bin/sh
#always sync before you drop the caches
sync
#drop caches
echo 3 > /proc/sys/vm/drop_caches

#run your application
./myapp>myapp.log 2>&1

#show log
#(If it exists and if it's >0 bytes.)
./logview myapp.log

#sync and back to menu
sync
cd /usr/gp2x/
./gp2xmenu
----------------------------------------

Example dev gpe file with two log files:
----------------------------------------
#!/bin/sh
#always sync before you drop the caches
sync
#drop caches
echo 3 > /proc/sys/vm/drop_caches

#run your application
./myapp> stdout.log 2> stderr.log

#show logs
#(Whichever exists and whichever is >0
#bytes. If both exist they are shown in
#the specified order, first stderr then
#stdout.)
./logview stderr.log stdout.log

#sync and back to menu
sync
cd /usr/gp2x/
./gp2xmenu
----------------------------------------
