path: root/HACKING

Notes on unity development: Quicklist desktop file specification: Adding a new quicklist entry requires modifiying the desktop file of the application the quicklist belongs to. You will need to create a new group named Quicklist Entry UID, with UID being a unique id (in the scope of the desktop file). An example follows: [Desktop Entry] ... ... ... [QuickList Entry 1] Name=FooBar Action Exec=foobar --thingone [QuickList Entry 2] Name=FooBar Second Action Exec=foobar --thingtwo [QuickList Entry 3] Name=FooBar Third Action Exec=foobar --thingthree Name and Exec follow standard Desktop file specifications and can be translated in the same mannar as standard desktop files. Bootperformance Logging: To enable boot performance logging, set the environment variable UNITY_BOOTLOG_FILENAME to a path to the log file and make sure unity is built with --enable-testing. eg: UNITY_BOOTLOG_FILENAME=/tmp/unity.log unity -p you can then produce a bootchart with this by running the tools/makebootchart.py script: ./tools/makebootchart.py --input=/tmp/unity.log --output=/tmp/unity.svg Webapp switching: Unity can use two webapp systems, prism and chromium, you can toggle between the two by setting the gconf key "/apps/unity/webapp_use_chromium" on or off Setting unmovable apps: To make a launcher unmovable set the desktop_file gconf key of the app to manditory setting bottom fixed apps: To make a launcher appear at the bottom of the launchers and fixed in place, set the key "fixed" (bool) to true in the launchers gconf directory