View Single Post
Posts: 96 | Thanked: 51 times | Joined on Jul 2010 @ India
#17
Originally Posted by SPARTAN563 View Post
Just pushed v0.2.1 to the build que, fixes a few small issues (looks like the daemon wasn't starting up properly). Also, added some new commands which should prove useful and added a README file which has a whole ton of useful material in it for debugging.

As for a GUI, that is the plan. Though I haven't used a ListView in Qt before so that will be interesting
Also, with any luck the lack of a GUI for the moment will keep away those who don't know how to use a terminal (and hence, those who don't know how to fix stuff if it breaks).

A quick list of some useful commands you may want for testing it:

Disabling the current daemon:
Code:
    initctl emit AppLockStopDaemon
Re-enabling the daemon
Code:
    initctl emit AppLockStartDaemon
Listen to events triggered by AppLock
Code:
dbus-monitor "type='method_call',sender='com.sierrasoftworks.AppLock.Daemon'"
Get the current status of AppLock
Code:
dbus-send --print-reply --dest=com.sierrasoftworks.AppLock /com/sierrasoftworks/AppLock com.sierrasoftworks.AppLock.Daemon.GetStatus
Just a note, the last DBus call will ONLY work with v0.2.1 so rather don't try it on v0.2.0
I suggest you update the frontpage with the usage instructions and the important commands till we see a GUI. It would make it easier for people who would want to test it.

Cheers!