Thread
:
[ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
View Single Post
SPARTAN563
2011-07-14 , 18:42
Posts: 92 | Thanked: 92 times | Joined on May 2011 @ Stellenbosch, South Africa
#
99
Update
Just uploaded v0.3.1 to the autobuilder and my website, about time the autobuilder started working again
I
think
everything is working out of the box in this version. I have clean-installed it a few times on my phone and it all seems to work. Just a few things to take note of since they have changed in this version when compared to v0.3.0 or have yet to be finished
Any apps that are locked/unlocked which use DBus monitors require the daemon to be restarted for changes to take effect. This can be done from the menu
Closing the daemon through DBus (e.g. using the Apply Changes menu item) will lock the phone. Figured this was a good idea otherwise a simple DBus call would close the daemon
You don't need to start the daemon before launching the UI anymore, it will be launched automatically
The settings.db file has been moved to /home/user/.applock/settings.db to fix some problems RE permissions
You should
NEVER
run the daemon as root otherwise the UI will
STOP
locking/unlocking apps on any permanent basis
Running
applock
from the terminal will no longer display command line usage, it will launch the UI. Run
applock --help
instead.
In this version you should
avoid using the terminal commands
. I haven't had the chance to update them to support the new changes to how everything works and I don't think some of them will work correctly. You are likely to add items to the database that cannot be removed without deleting the database.
Descriptions for applications that make use of localisation are
NOT YET WORKING
. So if you see a random thing like "ap_app_something_desc" under an app name, don't worry, it is just the localised string for the description and doesn't mean your phone has teleported into your living room to eat your new kitten. (Though it may have hacked your N9 and clocked it to 12GHz to fry its CPU :P)
Sorry that it has taken so long to get this version out the door, I have had to completely rewrite much of the codebase to get stuff working nicely. With any luck though this version will be a lot easier to use and you guys can start finding less obvious bugs
Anyway, enjoy and I await problem reports
__________________
Sierra Softworks
Quote & Reply
|
The Following 3 Users Say Thank You to SPARTAN563 For This Useful Post:
Estel
,
warhawk007
,
x61
SPARTAN563
View Public Profile
Send a private message to SPARTAN563
Visit SPARTAN563's homepage!
Find all posts by SPARTAN563