The listing below (a copy of the TODO file) should give you some idea of the general direction I'd like to take eboxy in the future. There are certainly plenty of things that could be improved and extended, and suggestions are welcome.
eboxy 0.4.1 todo list ===================== Current: - Listbox: methods to set/retrieve entire list - Set focus to button on SimulateClick() Planned for next release: - Better range/validity checks for property values - aedGUI-based interface plugin - Allow enumeration of widget types - Capslock/numlock for digit input - Allow configuration of digit input key characters - Fix synchronisation on changePage/changeFile - Attempt to fix incompatibilities with Flex 2.5.31 - Attempt to fix autotools problems in Debian - Code tidy-ups - Fix warnings - Tidy up code for OwnerObject/ObjectContainer/Notify - Tidy up any remaining old code (main, pluginmanager, utils) - Remove relative paths from includes? Planned for future releases: - Default templates - Document code - Purge image/font cache - 640x480 version of eBox skin - Validate XML internally - C++ plugin wrapper - Provide "event" object within event scripts to get source etc. - Add "either" alt,ctrl,shift,win (non-modifier) key aliases - Enable use of numlock & capslock as key modifiers - Directional widget navigation (up, down, left, right) - Actions for scrollbar widgets - Additional widgets: progressbar, spinedit? - Make mouse auto-focus optional - Better example skin(s) - Improvements to exechide - more persistent information? - Scrollbar buttons - Plugin communication - Fix framebuffer flickering - Better support for overlapping widgets - Background music and event sounds - Video file browser plugin - TV recording plugin - Web control plugin - Improved error handling/messages for scripts - Proper packaging (RPM, etc.) Possible future features: (email email@example.com if any of these interest you) - Allow config files in /etc/eboxy/ - Python bindings for plugin development - i18n support through GNU gettext - Config file for plugins to access - Flat-colour macros as image substitutes - Default system templates - Page templates - Custom widgets - Tools for verifying/converting/querying skin files - Optionally scale widget positions to screen size, given native resolution of page - Static rectangular border widgets - Optional background image stretching - Other input/control devices - System stats plugins (use uptime, uname, lm_sensors, etc.) - Animated/video backgrounds - In-GUI shell prompt/output - Listen for keypresses in the console as well - Built-in configuration/setup plugins/skins/features - Serialisation - Page editor plugin