[FreeNX-kNX] Does anyone else want Xinerama support in nx?

[Florian Schmidt]

Hi,

We have at our company a lot of users which would benefit from such a Xinerama support. For this I would prefer the first (clean) solution. I think this would get a better acceptance by the users working with nx and don't bother with IT related stuff. Also I often switch the resolution during working with the same screen resolution. Adding a external monitor with higher res, using a beamer, ...

So I would prefer auto detecting the current resolution at reconnect. The only thing which should be checked is the panel of the window manager in the NX session, gnome-panel sometimes crashes during resizing the resolution (At least uses 100% CPU and doesn't change anything).

Just my two cents :)

Cheers,
Florian
-------- Original-Nachricht --------
> Datum: Fri, 23 Jan 2009 00:41:35 +1300
> Von: Mario Becroft <mb at gem.win.co.nz>
> An: FreeNX-kNX at kde.org
> Betreff: [FreeNX-kNX] Does anyone else want Xinerama support in nx?

> We have a need for Xinerama support in nx. Meaning, if the user running
> nxclient has Xinerama, then when you create an nxagent session with a
> virtual desktop, the nxagent will provide the Xinerama extension and
> pass the xinerama info to clients. (This enables a window manager
> running on the nxagent display to do user friendly things such as
> placing new windows within a single screen, instead of placing them
> across the boundary of two screens, for example.)
> 
> I enquired with nomachine, but it is unclear when they will support
> this.
> 
> It would be relatively easy to get the functionality we need if we did
> not use the virtual desktop feature, but this feature is helpful for
> other reasons so we want to keep using it.
> 
> I have considered two possible approaches to this.
> 
> The most complete way of doing it is for nxagent to get the Xinerama
> info from its display, store this internally, and provide it to
> clients. It may be possible to use the XRandR extension to detect and
> propagate changes in screen geometry that occur when the user suspends
> and restores the nxagent session on a different display.
> 
> That sounds like a bit of work, and I am not sure that you would want
> the screen geometry info to change every time you resume the session.
> 
> An alternative approach that is sufficient for most of our needs, and
> sounds a bit easier to implement, involves letting the user configure
> their screen geometries manually when invoking nxagent, and nxagent
> simply provides this info to clients, irrespective of its current
> display (if any). This works because most of our users who require this
> feature always use the same screen configuration. It might be a bit
> weird though if you resized your nxagent screen so that it no longer
> matches the xinerama info. I will have to think about this.
> 
> It looks fairly easy to hack together a fake Xinerama extension that
> does something along these lines.
> 
> Is there any interest in this? Comments? Does anyone want to help?
> 
> -- 
> Mario Becroft <mb at gem.win.co.nz>
> ________________________________________________________________
>      Were you helped on this list with your FreeNX problem?
>     Then please write up the solution in the FreeNX Wiki/FAQ:
> 
> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>   
>          Don't forget to check the NX Knowledge Base:
>                  http://www.nomachine.com/kb/ 
> 
> ________________________________________________________________
>        FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
>       https://mail.kde.org/mailman/listinfo/freenx-knx
> ________________________________________________________________

-- 
NUR NOCH BIS 31.01.! GMX FreeDSL - Telefonanschluss + DSL 
für nur 16,37 EURO/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K11308T4569a