-- Guido Schimmels <__guido__@...> wrote
(on Tuesday, 27 April 2004, 06:31 AM +0200):
> Am 27.04.2004 03:34:57 schrieb(en) Matthew Weier OPhinney:
> > Do you have plans to implement an SF project for OroboROX? The reason
> > I ask is that it might be useful to have:
> > a) CVS
> > b) Downloads (though I understand that Jonatan is hosting the project
> > now on his site)
> > c) Bug Tracker
> > d) Requests Tracker
> > I personally would like (d)... as I have a request! I tried out
> > OroboROX
> The rox lists should do for now with respect to (d).
> Thomas said, he'd make OroboROX the default WM in ROX-Session.
> Maybe we could invite users to discuss OroboROX on the ROX-Wiki then.
The reason I suggested it was to have an easy place to look and see if
requests/bugs had already been submitted, rather than looking through
the archives. However, a few wiki pages would also do well. Perhaps I'll
throw some up later.
> > last week, but there were a couple show stoppers for me: I'm very
> > accustomed to switching workspaces using my mouse wheel (buttons 4
> That should be easy to add. (Now that workspace-switching works :) )
Excellent! I look forward to it!
> > 5), and I also have grown accustomed to dragging windows from one
> > workspace to the next using edge wrapping. Both of these are features
> You can drag windows across workspace borders now.
> What is edge wrapping?
Okay, I guess I missed that. Actually, what I recall now is that I
couldn't move windows at all, so I assumed I wouldn't be able to drag
between workspaces. I suspect I'll need to recompile and try again.
> > I also want to re-iterate that you may want to look at the code for
> > keylaunch for your keybindings, as that's incredibly stable. I also
> > think it would be useful to be able to extend the WM keybindings
> > beyond the WM -- to opening applications, etc -- so that this duty
> > doesn't need to be relegated to yet another program. Either that, or
> > bundle a keylauncher with OroboROX to handle both duties.
> The things is ROX already does keybindings for pinboard/panel items. I
> don't want to have a second keyboard-grabber who doesn't know anything
> about the keys taken by ROX. It has to be integrated.
I hadn't considered using ROX keybindings... However, that's not a great
solution in some instances. As an example, I have a 'multimedia'
keyboard that has keys named XF86HomePage, XF86Mail, XF86VolumeUp,
XF86VolumeDown, etc. I have mapped the volume keys to do alsactl actions
-- which aren't necessarily things I want on my desktop or panel. These
are also things that I cannot do trivially with ROX as I cannot give
arguments to scripts when setting icons; instead, I would need to setup
shell scripts for each action.
I agree it should be integrated; I guess what I'd like is some sort of
keygrabber integrated with ROX and/or OroboROX.
> Thomas, your suggestion? How do we tackle that?
> > I also like the idea of a root menu... maybe something could be done
> > with ROX-Menu or somesuch to bind it to a mouse and/or key press?
> ROX has a root menu. I'm against OroboROX offering an option to
> override the ROX root-menu.
I'm not suggesting overriding the ROX root menu; button 2 is currently
unassigned by ROX, and could be used to spawn an applications menu. I
inquired about this a couple years ago when using blackbox as both
blackbox and ROX were wanting to use button 3 for their root menu.
Thomas, at that time, indicated that the freedesktop.org specs suggest
button 2 being for window manager root menus (and, more specifically,
for managing windows) and button 3 for desktop context menus, which was
why he had setup ROX the way he had.
> But like you said, you could assign a key to ROX-Menu. You can already
> do that. Just put ROX-Menu on the panel and assign it a key. With
> regards to mouse-control, the only option I see is the middle-button
> for such things.
I'll need to check out ROX-Menu again; I haven't looked at it since one
of the initial releases, and at the time it wasn't terribly sufficient
for my needs as it only handled AppDir items (I understand it handles
other items at this point). As far as mouse control of it, I was
assuming middle-button for it (as outlined above; I currently have
deskmenu grabbing button-2 as it is.) I'm assuming ROX would have to
grab the mouse event, in which case it might make sense to be able to
configure, in ROX, a program to launch on button-2 events.
Matthew Weier O'Phinney