OESF Portables Forum
Everything Else => Model Specific Forums => Distros, Development, and Model Specific Forums => Archived Forums => SIMpad forum => Topic started by: Art Navsegda on September 06, 2005, 10:48:00 pm
-
I've found them there:
http://devernay.free.fr/hacks/opensimpad/2...rnel2.4/images/ (http://devernay.free.fr/hacks/opensimpad/20050831-kernel2.4/images/)
Does anybody wants to test them ?
-
I did these, and I'm testing them right now. Give it a try. I just put a more recent build there (20050907)
I only tested the GPE image so far, and let me tell you: it's really worth a try!
GPE is really great, and even includes several browsers (dillo2, gpe-mini-browser and minimo - but I couldn't build minimo)
Don't forget to read the README.
Fred
I've found them there:
http://devernay.free.fr/hacks/opensimpad/2...rnel2.4/images/ (http://devernay.free.fr/hacks/opensimpad/20050831-kernel2.4/images/)
Does anybody wants to test them ?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=94769\"][{POST_SNAPBACK}][/a][/div]
-
Yo Fred,
tried the gpe and it looked great, was even able to build Minimo (from the http://www.openzaurus.org/official/unstable/3.5.3/feed/x11) (http://www.openzaurus.org/official/unstable/3.5.3/feed/x11)), but my simpad has only 32mB (and 32 mB flash) so I don't think gpe suits him (mabye after modding him with a sd-card...). So installed the Opie (large) and that looked even greater; seems like this is the opie 3.5.3 (witch also runs on my collie and i like very much...) and beside some minor grafical hums (some of the images seems to me a bit blury as if the are maded for a smaller screen (the collie perhaps?) ) it looks great. Still everyone is forgetting to put the cf card in de etc/fstab but beside that; great work has been done!
Are you working with the opensimpad.org, and is this a possible 0.9rc2 or are you just 'one your own'?
laurens
-
pittyfull the buttons doesn't seems to work (including the settings).....
-
Try editing /etc/init.d/opie and add
export QWS_KEYBOARD=SIMpad
-
added in /etc/init.d/opie:
root@simpad:~# cat /etc/init.d/opie
#!/bin/sh
#
[ -z $LOGNAME ] && export LOGNAME=root && export HOME=/home/root
[ -z $HOME ] && export HOME=/home/$LOGNAME
export QWS_KEYBOARD=SIMpad
export QTDIR=/opt/QtPalmtop
export OPIEDIR=/opt/QtPalmtop
export QPEDIR=/opt/QtPalmtop
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$OPIEDIR/lib
export PATH=$PATH:$OPIEDIR/bin
but still no buttons to work .....
-
Ah yeah, according to
QWSKeyboardHandler *QWSServer::newKeyboardHandler( const QString &spec )
{
  QWSKeyboardHandler *handler = 0;
  QString device;
  QString type;
  int colon=spec.find(':');
  if ( colon>=0 ) {
    type = spec.left(colon);
    device = spec.mid(colon+1);
  } else {
    type = spec;
  }
  if ( type == "Buttons" ) {
#if defined(QT_QWS_SIMPAD)
    qDebug( "QWSKeyboardHandler: using SIMpad switches handler..." );
    handler = new QWSsimpadButtonsHandler();
#elif defined(QT_QWS_YOPY)
    handler = new QWSyopyButtonsHandler();
#elif defined(QT_QWS_CASSIOPEIA)
    handler = new QWSVr41xxButtonsHandler();
#endif
  } else if ( type == "QVFbKeyboard" ) {
    handler = new QWSVFbKeyboardHandler();
  } else if ( type == "USB" ) {
    handler = new QWSUsbKeyboardHandler(device);
  } else if ( type == "TTY" ) {
    handler = new QWSTtyKeyboardHandler(device);
  }
  else if( type == "Samsung" )  {
    handler = new QWSSamsungKeypadHandler(device);
  }
  else {
    qWarning( "Keyboard type %s:%s unsupported", spec.latin1(), device.latin1() );
  }you may have more luck with QWS_KEYBOARD="Buttons"...
-
Ah yeah, according to
QWSKeyboardHandler *QWSServer::newKeyboardHandler( const QString &spec )
{
QWSKeyboardHandler *handler = 0;
QString device;
QString type;
int colon=spec.find(':');
if ( colon>=0 ) {
type = spec.left(colon);
device = spec.mid(colon+1);
} else {
type = spec;
}
if ( type == "Buttons" ) {
#if defined(QT_QWS_SIMPAD)
qDebug( "QWSKeyboardHandler: using SIMpad switches handler..." );
handler = new QWSsimpadButtonsHandler();
#elif defined(QT_QWS_YOPY)
handler = new QWSyopyButtonsHandler();
#elif defined(QT_QWS_CASSIOPEIA)
handler = new QWSVr41xxButtonsHandler();
#endif
} else if ( type == "QVFbKeyboard" ) {
handler = new QWSVFbKeyboardHandler();
} else if ( type == "USB" ) {
handler = new QWSUsbKeyboardHandler(device);
} else if ( type == "TTY" ) {
handler = new QWSTtyKeyboardHandler(device);
}
else if( type == "Samsung" ) {
handler = new QWSSamsungKeypadHandler(device);
}
else {
qWarning( "Keyboard type %s:%s unsupported", spec.latin1(), device.latin1() );
}you may have more luck with QWS_KEYBOARD="Buttons"...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=95053\"][{POST_SNAPBACK}][/a][/div]
BTW A little problem with that approach : using USB: /dev/input/event1 works fine - until you unplug then replug the keyboard. If you use devfs, with the device gone, OPIE won't find your reintroduced keyboard.
Guylhem
-
Yep changing QWS_KEYBOARD into export QWS_KEYBOARD="Buttons" or even export QWS_KEYBOARD=Buttons fixes the buttons,
thanks laurens