Editing Actman

Warning: You are not logged in. Your IP address will be recorded in this page's edit history.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Learn more about Contributing to the wiki.

Desktop Activity Manager, or D-A-M, or DAM, or actman, is a command line tool and a status menu widget that allows saving and restoring of the desktop. There can be multiple saved desktops so it is possible to have different activities (desktop profiles) and switch between them by saving the current one and loading another.

For discussion about actman visit [http://talk.maemo.org/showthread.php?t=47373 this thread].

== Status menu widget ==
The status menu widget is a front-end to the command line tool. While it doesn't have all its features it is easier to use and handles all common user actions.

[[Image:actman-screenshot1.png|thumb|300px|alt=Screenshot of Actman main page|Main page]]

The main page includes the following actions:
* Select: Saves the current activity and switches to the selected (highlighted) activity.
* New: Create a new activity that is a duplicate of the current one
* Rename: Renames the selected activity
* Delete: Deletes the selected activity. It is not possible to delete the current activity
* More: Shows more actions

[[Image:actman-ss-more.png|thumb|300px|alt=Screenshot of Actman more actions|More actions]]

When clicking "more", some more actions are shown:

* Store current: Saves the current activity without switching to a new one
* Reload current: Reloads the current activity
{{clear}}

== Command line tool ==
The command line tool is named "activity" and is installed in <code>/usr/bin</code>. It should be run as user (and not as root!) and it includes a help screen:

<pre>
~ $ /usr/bin/activity help  
Activity manager 1.1

Available commands:

change DEST		Store current activity and load DEST.
  clone ACT1 ACT2	Create activity ACT2 as a clone of ACT1. Current
  			activity will not be changed.
  create ACTIVITY	Create a new (empty) activity.
  current		Print the current activity name.
  delete [-f] ACTIVITY	Same as remove.
  help			This help.
  list			List available activities.
  load [-f] SRC		Load activity SRC. If -f is used then it will be
  			allowed to re-load the current activity.
  new ACTIVITY		Same as create.
  reload		Reload current activity without storing first.
  remove [-f] ACTIVITY	Remove activity ACTIVITY. If -f is used then there
  			will be no questions asked.
  rename ACT1 ACT2	Rename activity ACT1 to ACT2.
  runstart [ACTIVITY]	Run scripts of entering an activity
  runend [ACTIVITY]	Run scripts of ending an activity
  store DEST		Store current activity as DEST.
  version		Print the version
</pre>

Activities are stored under <code>/home/user/.activities</code>

To get a list of available activities use "list":

<pre>
~ $ /usr/bin/activity list 
car
clean
empty
main
main2
main3
Tei
Test
test2
</pre>

To save the current activity and switch to a new one use "change", etc.

== How it works ==
Actman (Activity Manager) works by:

- dumping (on store) and restoring gconf entries for each activity.

- copying (on store) and pasting (on switching/restore)the contents of $HOME/.config/hildon-desktop/home.plugins.

- copying (on store) and pasting (on switching/restore) the contents of $HOME/.bookmarks/home-thumbnails.

- killing hildon-home whenever the user decides to change their activities.

Such gconf that are dumped and restored are:
- appletbase (widgets and shortcuts for each home screen and their positions)

- viewsbase (the amount of home screens the user has and the background images 
for each home screens)

- hildon-home (bookmarks and shortcuts the user has for this particular activity)

- contacts (contacts that the user has placed on the home screens)

Individual files and directories are copied and pasted such as:

- homeplugins (widgets used)

- thumbnails (bookmarks to web pages the user has for this particular activity)

In addition to what it does above, actman allows users to place scripts to be executed before and/or after the switch across to this activity, it also allows cloning of activities, restoring without saving changes, renaming as well as listing of the activities already stored.

These activies are usually stored in ~/.activities/activities/<name_of_activity_the_user_chooses_to_name>/. The only exception is the root user and in almost all cases ~ would be /home/user (unless one decides to login through another username for instance).

== Running user scripts ==
Since versions 1.1, actman has the ability to run user scripts.

The scripts are stored under <code>/home/user/.activities/scripts</code> (which does not exist by default).

There are two kind of scripts:
* Scripts that are associated with an activity (kindA)
* Scripts that are not associated with an activity (kindB)

There are two kind of script invocations "start" and "stop":
* start: is used when entering the corresponding activity
* end: is used when leaving the corresponding activity

The rationale behind this is to have initscript-like scripts that may start or stop services (kindA) or save/restore a widgets configuration (kindB).

=== Scripts associated with an activity ===
Those scripts are installed in a directory named as the activity. For example, for the activity 'main' one can place scripts in <code>/home/user/.activities/scripts/main</code>. They will be ran when switching to or from that activity.

=== Scripts not associated with an activity ===
They are installed in <code>/home/user/.activities/scripts/always</code> and are ran whenever an activity is switched.

=== Invocation ===
Scripts are ran with the parameter "start" or "stop" depending on the invocation type. For example it is possible to create a script that connects/disconnects from the Internet when entering/leaving an activity:

<source lang="bash">
#!/bin/sh

if [ "$1" = "start" ] ; then
  # Commands to connect to the internet
elif [ "$1" = "stop" ] ; then
  # Commands to disconnect from the internet
fi
</source>

Putting the above in <code>/home/user/.activities/scripts/internet</code> and having an activity named "internet" (watch for the case) will result in auto connecting/disconnecting to/from the Internet when entering/leaving that activity.

For desktop widgets that want to implement per-activity settings and are not already handled by actman it is possible to put a script in <code>/home/user/.activities/scripts/always</code> like this:

<source lang="bash">
#!/bin/sh

# This is where actman stores the settings of the activities
# ACTMAN_ACTIVITY contains the name of the corresponding activity and it is
# set by actman
DEST=/home/user/.activities/$ACTMAN_ACTIVITY

if [ "$1" = "start" ] ; then
  OLDSETTINGS="$DEST/myapp.tar"
  if [ -e "$OLDSETTINGS" ] ; then
    ( cd /home/user
      rm -rf .mywidget
      mkdir .mywidget
      tar -xf $OLDSETTINGS )
  fi
elif [ "$1" = "stop" ] ; then
  ( cd /home/user;
    tar -cf $DEST/myapp.tar .mywidget
    rm -rf .mywidget
  )
fi
</source>

The idea is to store the configuration files in the same location where actman stores each activity's settings (<code>/home/user/.activities/<activity name>/</code>) as a tar (or even better as a tgz). <code>$ACTMAN_ACTIVITY</code> will always have the name of the current activity and can be used as such.

[[Category:Software]]

Please note that all contributions to maemo.org wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see maemo.org wiki:Copyrights for details). Do not submit copyrighted work without permission!

Summary:

Cancel | Editing help (opens in new window)

Templates used on this page:

Template:Clear (edit)

Retrieved from "https://wiki.maemo.org/Actman"

Personal tools

Navigation

Views

Editing Actman

@@ Line 116: / Line 116: @@
 * end: is used when leaving the corresponding activity
-The rationale behind this is to have initscript-like scripts that may start or stop services (kindA) or save/restore a widget's configuration (kindB).
+The rationale behind this is to have initscript-like scripts that may start or stop services (kindA) or save/restore a widgets configuration (kindB).
 === Scripts associated with an activity ===