headers
Oskar Nordquist | 6 Apr 2009 22:57
Picon

Attach client to several workspaces

Hi,

I'm wondering how hard it would be to implement support for having clients
visible in more than one workspace, e.g it could work like the tagging feature
for moving windows, only clients could be attached to several frames and/or
workspaces.

If anyone know of a script with similar features, please let me know.

Regards,

Oskar N
Permalink | Reply | 7 comments |
headers
Tuomo Valkonen | 7 Apr 2009 12:14
Picon
Picon
Favicon

Re: Attach client to several workspaces

On 2009-04-06, Oskar Nordquist <oskar.nordquist@...> wrote:
> I'm wondering how hard it would be to implement support for having clients
> visible in more than one workspace, e.g it could work like the tagging feature
> for moving windows, only clients could be attached to several frames and/or
> workspaces.

A basic version shouldn't be too difficult. Just a script that attaches 
to one of the hooks that signal workspace change, and then moves the 
window around.

What's more work is remembering where exactly the window was on each
workspace... for that, there's the placeholder mechanism, but it
isn't exported to the Lua side ATM.

--

-- 
"[Fashion] is usually a form of ugliness so intolerable that we have
 to alter it every six months." -- Oscar Wilde
"The computer industry is the only industry that is more fashion-driven
 than women's fashion." -- RMS
Permalink | Reply | 5 comments |
headers
Oskar Nordquist | 7 Apr 2009 13:40
Picon

Re: Attach client to several workspaces

2009/4/7 Tuomo Valkonen <tuomov@...>:
> On 2009-04-06, Oskar Nordquist <oskar.nordquist@...> wrote:
>> I'm wondering how hard it would be to implement support for having clients
>> visible in more than one workspace, e.g it could work like the tagging feature
>> for moving windows, only clients could be attached to several frames and/or
>> workspaces.
>
> A basic version shouldn't be too difficult. Just a script that attaches
> to one of the hooks that signal workspace change, and then moves the
> window around.
>

Would it not be easier to just duplicate the client to refer to the same X
window? I don't even know if that is possible, but if it is, that's how I'd
prefer to do it.
Permalink | Reply | 4 comments |
headers
Tuomo Valkonen | 7 Apr 2009 15:50
Picon
Picon
Favicon

Re: Attach client to several workspaces

On 2009-04-07, Oskar Nordquist <oskar.nordquist@...> wrote:
> Would it not be easier to just duplicate the client to refer to the same X
> window? I don't even know if that is possible, but if it is, that's how I'd
> prefer to do it.

Ummm... I don't know what you really mean. The client always refers to
the same window it initially created. You can move it around in Ion's
window management hierarchy (cf. Mod1+A, Mod1+T & Mod1+K A, tab drag),
also to follow you around. Obviously you can automate this by attaching
a script to suitable hooks. 

The difficult part is that it would always appear at the same index in
a frame etc.; this demands exporting the placeholders to Lua side.

--

-- 
"[Fashion] is usually a form of ugliness so intolerable that we have
 to alter it every six months." -- Oscar Wilde
"The computer industry is the only industry that is more fashion-driven
 than women's fashion." -- RMS
Permalink | Reply | 3 comments |
headers
Aron Griffis | 7 Apr 2009 16:47
Favicon
Gravatar

Re: Attach client to several workspaces

Oskar Nordquist wrote:  [Mon Apr 06 2009, 04:57:47PM EDT]
>I'm wondering how hard it would be to implement support for
>having clients visible in more than one workspace, e.g it could
>work like the tagging feature for moving windows, only clients
>could be attached to several frames and/or workspaces.

This would be really nice to have in ion3.  Something I miss from
sawfish.

Aron
Permalink | Reply | 0 comments |
headers
Oskar Nordquist | 7 Apr 2009 18:22
Picon

Re: Attach client to several workspaces

2009/4/7 Tuomo Valkonen <tuomov@...>:
> On 2009-04-07, Oskar Nordquist <oskar.nordquist@...> wrote:
>> Would it not be easier to just duplicate the client to refer to the same X
>> window? I don't even know if that is possible, but if it is, that's how I'd
>> prefer to do it.
>
> Ummm... I don't know what you really mean. The client always refers to
> the same window it initially created. You can move it around in Ion's
> window management hierarchy (cf. Mod1+A, Mod1+T & Mod1+K A, tab drag),
> also to follow you around. Obviously you can automate this by attaching
> a script to suitable hooks.
>

I'm not sure how X works, but I'm guessing there is some kind of handle that
an Ion client refers to to draw the window. Would it not be possible to
use this same handle in a new Ion client, which would essentially render the
same window?

Excuse my ignorance.
Permalink | Reply | 2 comments |
headers
Matthieu Moy | 7 Apr 2009 19:03
Picon
Picon
Favicon

Re: Attach client to several workspaces

Oskar Nordquist <oskar.nordquist@...> writes:

> 2009/4/7 Tuomo Valkonen <tuomov@...>:
>> On 2009-04-07, Oskar Nordquist <oskar.nordquist@...> wrote:
>>> Would it not be easier to just duplicate the client to refer to the same X
>>> window? I don't even know if that is possible, but if it is, that's how I'd
>>> prefer to do it.
>>
>> Ummm... I don't know what you really mean. The client always refers to
>> the same window it initially created. You can move it around in Ion's
>> window management hierarchy (cf. Mod1+A, Mod1+T & Mod1+K A, tab drag),
>> also to follow you around. Obviously you can automate this by attaching
>> a script to suitable hooks.
>>
>
> I'm not sure how X works, but I'm guessing there is some kind of handle that
> an Ion client refers to to draw the window. Would it not be possible to
> use this same handle in a new Ion client, which would essentially render the
> same window?

You cannot have the same application actually running in different
frames without application support. At least one problem is that
different frames can have different sizes, and the application will
draw its content based on the size.

With application support, you can do such kind of things (like Emacs
"make new frame" for example), but they will still be two distinct
frames.

What you can do (and what wmii, awesome and other do) is that the
(Continue reading)

Permalink | Reply | 1 comment |
headers
Deepanjan Kesh | 9 Apr 2009 00:34
Picon

cannot type in run dialog

i have installed ion3 in ubuntu 8.10. but i am not able to type in the
run dialog though tab completion works.
any help would be really appreciated
Permalink | Reply | 3 comments |
headers
Tuomo Valkonen | 9 Apr 2009 08:59
Picon
Picon
Favicon

Re: cannot type in run dialog

On 2009-04-08, Deepanjan Kesh <deepkesh@...> wrote:
> i have installed ion3 in ubuntu 8.10. but i am not able to type in the
> run dialog though tab completion works.
> any help would be really appreciated

Fix your locales settings. You need the .encoding (e.g. fi_FI.UTF-8)
part in LC_CTYPE (or LANG), because Xlib is broken.

--

-- 
Stop Gnomes and other pests! Purchase Windows today!
Permalink | Reply | 2 comments |
headers
Jasbir Khehra | 9 Apr 2009 11:41
Picon

Re: cannot type in run dialog

On Thu, Apr 9, 2009 at 12:29 PM, Tuomo Valkonen <tuomov@...> wrote:
> On 2009-04-08, Deepanjan Kesh <deepkesh@...> wrote:
>> i have installed ion3 in ubuntu 8.10. but i am not able to type in the
>> run dialog though tab completion works.
>> any help would be really appreciated
>
> Fix your locales settings. You need the .encoding (e.g. fi_FI.UTF-8)
> part in LC_CTYPE (or LANG), because Xlib is broken.
Hi Deepanjan,
To change the locales setting you need to modify /etc/default/locales
and reboot.
Check the output with locale command.
Permalink | Reply | 1 comment |

Gmane