- last login name is saved

- wait image should be displayed right now
- the qApp object is destroyed before the launcher is started -- this
  should prevent some semaphore permission problems
- added a (very basic) crash handler
- added a simple "respawned too fast" detection in case of qt/e fb problems
- if opie-login is started with -a <user> or --autologin <user> it doesn't
  prompt for a username/password - instead it loads qpe directly using the
  specified user account
  So even if you are not running multiuser, you should now start qpe with:
  opie-login --autologin=root

1 files changed, 40 insertions, 0 deletions

diff --git a/core/opie-login/loginapplication.h b/core/opie-login/loginapplication.h
new file mode 100644
index 0000000..a709c5b
--- a/dev/null
+++ b/core/opie-login/loginapplication.h
@@ -0,0 +1,40 @@
+#ifndef __OPIE_LOGINAPPLICATION_H__
+#define __OPIE_LOGINAPPLICATION_H__
+
+#include <qstringlist.h>
+
+#include <qpe/qpeapplication.h>
+
+#ifdef USEPAM
+struct pam_message;
+struct pam_response;
+#endif
+
+class LoginApplication : public QPEApplication {
+public:
+	LoginApplication ( int &argc, char **argv );
+
+	static bool checkPassword ( const char *user, const char *password );
+
+	static const char *loginAs ( );
+	static void setLoginAs ( const char *user );
+
+	static bool changeIdentity ( );
+	static bool login ( );
+
+	static QStringList allUsers ( );
+
+	void quitToConsole ( );
+
+private:
+	static const char *s_username;
+
+#ifdef USEPAM
+	static int pam_helper ( int num_msg, const struct pam_message **msg, struct pam_response **resp, void * );
+	static const char *s_pam_password;
+#endif
+};
+
+extern LoginApplication *lApp;
+
+#endif