|
From: Thomas L. <ta...@ec...> - 2004-03-26 14:43:48
|
On Thu, Mar 25, 2004 at 10:32:53PM +0100, Jonatan Liljedahl wrote: > On Thu, 25 Mar 2004 12:16:56 +0200 > Guido Schimmels <gu...@ar...> wrote: > > > Please try OroboROX and tell me what you think! > > It would give us the chance to offer a complete package like Gnome > > and Xfce do. Or inform me if you don't have such ambitions! > > How is it supposed to be started by ROX-Session? > (Entering the full path to the AppRun script in the WM combobox works, > but it's kind of ugly...) ROX-Session should handle AppDirs and DnD to > choose WM, and maybe a button to open your favorite editor on the file > that lists the WM's shown in the combobox... DnD (and editor windows) are difficult to use if you haven't got a window manager running, though. The easy solution is to just add /uri/0install/rox.sourceforge.net/apps/OroboROX to the ROX-Session menu though. For a complete 'ROX desktop' bundle, you'd just default it to that, of course, and the user wouldn't even see the box at first login. I think a pre-configured bundle is a great idea, as long as other people are free to make other bundles. One of the aims for the zero install stuff is to make this easy: have a session script which sticks /uri/0install/my.site/config in XDG_CONFIG_DIRS and runs ROX-Session and everything gets the setup that my.site wanted, complete with default panels, etc. > What are the plans on making the options available in a GUI? Long term? Store the options with: http://www.freedesktop.org/Standards/config-spec Use ROX-Lib's OptionsBox for the GUI. Eventually, I'd remove the C versions of the options box from the filer and ROX-Session and get them to call Python sub-programs to edit the options. The non-session-specific options in ROX-Session (Display, Mouse, etc) would become a set of separate applications entirely. -- Thomas Leonard http://rox.sourceforge.net tal00r at ecs.soton.ac.uk tal197 at users.sourceforge.net GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 |