darcs patch: Add Layout.FloatLayout the start of a floating layout

Hi,
this is the start of a floating layout, something like the floating
layout in ion3.
It is just a start, meaning that there are no decoration or fancy
stuff. But you can move and resize windows with the keyboard (see
$usage for setting up the needed key bindings).
Now, the main job of a floating layout is to decide where to place the
newly created windows. This new module *doesn't* address this problem.
Indeed, I implemented it as a layout modifier. I though that this way
it should be possible to use alternate floating layouts. In this
scenario this module would just be the layer for interacting with the
windows.
Right now layouts do not work well with this module. They usually
place the new windows always in the same place, and move the
previously created windows accordingly. Instead we would need layouts
that do not touch old windows, but place the *new* one somewhere.
Probably I'll try to come up with something in the next days.
Anyway, I would like to have some feedback before pushing this patch.
I'm not really interested in having this patch included in the xmc
tree, so if you think there should be better ways to achieve this
goal, please let me know... we can throw this code away a start with a
new, more promising approach.
Cheers,
Andrea
Thu Jan 17 18:51:51 CET 2008 Andrea Rossato

On Jan 17, 2008 1:12 PM, Andrea Rossato
Hi,
this is the start of a floating layout, something like the floating layout in ion3.
It is just a start, meaning that there are no decoration or fancy stuff. But you can move and resize windows with the keyboard (see $usage for setting up the needed key bindings).
Now, the main job of a floating layout is to decide where to place the newly created windows. This new module *doesn't* address this problem. Indeed, I implemented it as a layout modifier. I though that this way it should be possible to use alternate floating layouts. In this scenario this module would just be the layer for interacting with the windows.
Right now layouts do not work well with this module. They usually place the new windows always in the same place, and move the previously created windows accordingly. Instead we would need layouts that do not touch old windows, but place the *new* one somewhere. Probably I'll try to come up with something in the next days.
Anyway, I would like to have some feedback before pushing this patch. I'm not really interested in having this patch included in the xmc tree, so if you think there should be better ways to achieve this goal, please let me know... we can throw this code away a start with a new, more promising approach.
Cheers, Andrea
Thu Jan 17 18:51:51 CET 2008 Andrea Rossato
* Add Layout.FloatLayout the start of a floating layout
I haven't looked at this patch yet, but seeing how floating support is probably going to change dramatically in the near future (so says sjanssen), it might be advisable to wait for that to happen before tackling a floating layout. Such a module is probably just going to have to be completely rewritten soon anyway. -Brent

On Thu, Jan 17, 2008 at 01:27:49PM -0500, Brent Yorgey wrote:
I haven't looked at this patch yet, but seeing how floating support is probably going to change dramatically in the near future (so says sjanssen), it might be advisable to wait for that to happen before tackling a floating layout. Such a module is probably just going to have to be completely rewritten soon anyway.
Possibly. But the nice thing about this approach is that is doesn't actually use the floating layer, so it allows us to experiment with the floating UI without completely ripping apart the core. -- David Roundy Department of Physics Oregon State University

On Thu, Jan 17, 2008 at 01:44:06PM -0500, David Roundy wrote:
Possibly. But the nice thing about this approach is that is doesn't actually use the floating layer, so it allows us to experiment with the floating UI without completely ripping apart the core.
That's the idea, indeed. Moreover I'm quite sure there's been some discussion about having a real floating layout like this. Now I'm going to add decorations and a mouse interface - code that can be reused at a later time anyhow. I did not understand where the layout layer is going to go, and I did not follow the nested stacks discussion enough to understand how the two facts may be related. If someone could get me up to date I'd appreciate. Cheers, Andrea
participants (3)
-
Andrea Rossato
-
Brent Yorgey
-
David Roundy