Screenlets are tiny, self-created applications that resemble desktop items. They are like little things that sit or stand on your desk.
Screenlets are small owner-drawn applications that provide a virtual representation of things lying or standing around on your desk. These mini-apps are written in Python and offer endless possibilities such as sticknotes, rulers, and clocks. The main goal of the Screenlets-framework is to make it easy to create fully themeable mini-apps that solve basic desktop-work-related needs and enhance the usability and visual appeal of the modern Linux-desktop.
Screenlets adhere to the UNIX-idea of modularity and having one tool for one purpose. They are essentially the modern evolution of that idea, ported from commandline-tools to desktop-apps. One of the main aims of the screenlets is to encourage the creation of visually appealing graphical frontends to common unix-tools to attract the "modern" user while still "keeping it real".
Screenlets are shaped Gtk-Windows that contain a window, a menu and a theme (of type ScreenletTheme). They also offer a simple way of handling and changing settings/options for both the user and developer. Since version 0.0.8, all screenlets can be controlled over DBus and can easily offer customized services.
Installation is easy - extract the archive into a directory, navigate to that directory and, as root-user, run "make install" (Ubuntu users just add a leading "sudo"). Use the "make menu" command (as root) to install .desktop-files for the screenlets, allowing easy adding of screenlets through the Applications-menu or the Alt+F2 dialog.
To generate documentation, run "make pydoc" for default (and ugly) pydoc-documentation or "make doxydoc" for doxygen-documentation (you need to install doxygen first) or "make epydoc" for epydoc-documentation (you need to install python-epydoc first).
Usage is straightforward - since v0.0.8, it is recommended to start the screenlets by launching them directly. Screenlets of the same type always run in the same process. You can run each Screenlet individually with (for example) "/usr/local/share/screenlets/Clock/ClockScreenlet.py". Do not use "screenletsd" for starting screenlets anymore - prefer to use the Applications-menu or the ControlScreenlet for launching new screenlets.
If you want individual screenlets to be launched on startup in GNOME, add them to your session's startup programs. That way they will be started when you log into your gnome-session.
Screenlets adhere to the UNIX-idea of modularity and having one tool for one purpose. They are essentially the modern evolution of that idea, ported from commandline-tools to desktop-apps. One of the main aims of the screenlets is to encourage the creation of visually appealing graphical frontends to common unix-tools to attract the "modern" user while still "keeping it real".
Screenlets are shaped Gtk-Windows that contain a window, a menu and a theme (of type ScreenletTheme). They also offer a simple way of handling and changing settings/options for both the user and developer. Since version 0.0.8, all screenlets can be controlled over DBus and can easily offer customized services.
Installation is easy - extract the archive into a directory, navigate to that directory and, as root-user, run "make install" (Ubuntu users just add a leading "sudo"). Use the "make menu" command (as root) to install .desktop-files for the screenlets, allowing easy adding of screenlets through the Applications-menu or the Alt+F2 dialog.
To generate documentation, run "make pydoc" for default (and ugly) pydoc-documentation or "make doxydoc" for doxygen-documentation (you need to install doxygen first) or "make epydoc" for epydoc-documentation (you need to install python-epydoc first).
Usage is straightforward - since v0.0.8, it is recommended to start the screenlets by launching them directly. Screenlets of the same type always run in the same process. You can run each Screenlet individually with (for example) "/usr/local/share/screenlets/Clock/ClockScreenlet.py". Do not use "screenletsd" for starting screenlets anymore - prefer to use the Applications-menu or the ControlScreenlet for launching new screenlets.
If you want individual screenlets to be launched on startup in GNOME, add them to your session's startup programs. That way they will be started when you log into your gnome-session.
What's New
Version 0.1.2: N/A