10 June, 2005 at 12:12 1 comment

Homepage Features ChangeLog ML

Customizing Evidence


If you built evidence with shelf and icon-view (or download evidence), you may use a ready-made icon-set of your choice.
To build your own iconset, make new folder under /usr/local/share/evidence/icons, copy the desired icons into that folder, and create a file mime.icons telling evidence which of the icons to use for which MIME-type. See other iconsets for examples for the mime.icons map.


If you built evidence with the evas-canvas, you may use a ready-made theme of your choice, or make your own using one of the shipped ones as example.

To create new background-databases for use with the ebg-loader, you will want to also download ebony.

Theme-plugins (“engines”)

Themes tell evidence what fonts, pictures and theme-plugins to use.
Theme-plugins are responsible for loading or creating icons, rubber-bands, scrollbars, and background pictures.
They can do this in any way they like — but whether you like your icon-view minimalistic or convoluted, you’ll only load the plugins you actually use!
If you know the C programming language, you may write your own theme-plugins.


To run evidence with a backend other than the one-size-fits-all default, pass the backend‘s name on the command-line (see manual). To make it the default backend, simply ln -s /usr/local/lib/evidence/backend/MyFunkyNewBackend.so /usr/local/lib/evidence/backend/fsxs.so — I’ll auto that in the future.


Providers are plugins that provide extra info on MP3s, Oggs, images, and other files. The setup file evidence.providers tells evidence which providers to try on what type of file.


Right-clicking on a file brings up a menu with actions that can reasonably be applied to that file. How evidence knows which actions make sense for a given file depends on the backend: the default backend would read its setup file (evidence.menu); the GNOME-VFS2 backend would look it up in the GNOME’s database etc.


When an URL is entered into the typebuffer (“µshell”), evidence will look up the protocol (e.g. “http://”, “ftp://”) in evidence.handler to know which program should handle the URL (Mozilla, lftp, …).


If a program is double-clicked, it is started.
If a data file (or “document”) is double-clicked, evidence will determine the document’s type (e.g. “text/html”, “image/gif”). It will then try to have a suitable application open that document (a text-editor for the HTML, a graphics editor for the GIF etc.).


    Executive summary
    The backend tells evidence about the files on your system.
    The default backend should built/work on any machine. It is fully sufficient for most uses.
    Other backends will be similar in features, but may offer more seamless integration with specific Desktop Environments like KDE or GNOME2.

File-system component
The backend tells evidence about the files on your system. There are a several backends to choose from; for instance, if you are using KDE, the KDE-backend will let evidence use the awesome power of kioslaves. The GNOME-VFS backend does similar things for GNOME-users, the efsd-backend for enlightenment 17 users. If in doubt, use the default “file” backend which does not rely on a specific Desktop Environment and will run anywhere.

Meta-data providers
Plugins that provide extra info on MP3, images, …

Providers a small plugins that are specialists for a certain type of file. The MP3/ID3 provider for instance knows how to read MP3 tags. It enables evidence to show information such as song title, artist’s name, release-date and more even if they are not part of the file’s name. This information will be displayed in tooltips and in the file-info dialog together with the usual data (file’s size, its owner, date of last modification, …).

Most plugins also allow some of the data to be edited; in the case of the MP3/ID3 plugin, you may edit your MP3 tags in the file-info dialog!

Plugins are not part of the main program; this way, you may easily add plugins without having to rebuild the whole program.
This also means that evidence will only load plugins as it needs them; if you have no MP3-files, the MP3/ID3 plugin will not be loaded.

Most plugins rely on other code (“libraries”) that you need to install before you can build or use that plugin:
Plugin     Needs
Ogg Vorbis-tag     libvorbis, libvorbisfile, libogg
MP3-tag (ID3)     libid3 3.8+
image     imlib2 (highly recommended for thumbnailer anyway)
TrueType fonts     freetype2 (required for evas anyway)
PDF, Real, HTML, …    libextractor


Entry filed under: Uncategorized.

Doodle – Desktop Search – Libextractor – References

1 Comment Add your own

  • 1. John E  |  8 November, 2010 at 05:25

    Hello! Interesting site!



Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

Trackback this post  |  Subscribe to the comments via RSS Feed


June 2005
« May   Jul »


%d bloggers like this: