Ben Hodgens | 1 Jun 2009 01:38
Gravatar

Re: Awesome is Cool! (finding client 'class or instance')

Matthias Kirschner wrote:
> Hi Ben,
> 
> * Ben Hodgens <ben <at> hodgens.net> [2009-05-31 14:40:40 -0600]:
> 
>> The only thing I wish it had was a "GUI" way to associate clients with a 
>> tag (for automatic assignment) and to remember the specific predefined 
>> view per tag. It's a little irritating to have to configure, but it works 
>> just the same once you figure it out. :)
> 
> I am using awesome for about a week now. The clients / tag associaten
> works fine. But I haven't had time to look into the "remember predifined
> view per tag" yet. Can you give me a pointer, or the corresponding part
> of your config?
> 
> Thanks,
> Matthias
> 
> 

Which version of Awesome are you using, Matthias? Version 3.2 and 3.3 have 
drastically different configurations (3.3 is all-lua, 3.2 still has some of the 
legacy configuration left). I can't rightly say what 3.3 would look like, but 
here's what 3.2 looks like (3.3 should be similar; I think this part of the 
config is in lua):

-- Applications to be moved to a pre-defined tag by class or instance.
-- Use the screen and tags indices.
apptags =
{
(Continue reading)

Josh Rickmar | 1 Jun 2009 03:04

Titlebars for Tabulous

Hi. Recently, I found out about the uzbl browser[1]. This application is
unique in that it tries to follow the UNIX philosophy as closely as
possible. As a result, it does not provide tabs, but leaves the problem
of multiple pages up to the window manager (which is how I think it
should be done).

First of all, I tried using it by setting the layout to max so that
every client would be maximized. The advantage of this is that the names
of the pages would still appear at the top, so I knew how my "tabs" were
organized. However, this method fails when trying to place another
application on this tag or showing two or more tags at the same time.

So, I started looking at tabulous to see if it would solve this problem.
After searching the web, I added some parts to my rc.lua which used
tabulous to solve this issue.

The problem with using tabulous, though, is that there is no graphical
indication anywhere about the other tabs. Only the current tabulous tab
gets a spot on the top bar.

Basically, I'm looking for a way to have a titlebar (similar to
awful.titlebar) which will list all the tabs in a current tabulous tab
set. I have not used Ion, but from screenshots that I've seen, it seems
to do exactly this. Is there a way to model this behavior in awesome as
well?

Links:
1: http://www.uzbl.org/

--

-- 
(Continue reading)

koniu | 1 Jun 2009 03:31
Picon
Gravatar

Re: Awesome is Cool!

On Sun, May 31, 2009 at 21:40, Ben Hodgens <ben <at> hodgens.net> wrote:
> The only thing I wish it had was a "GUI" way to associate clients with a tag
> (for automatic assignment) and to remember the specific predefined view per
> tag. It's a little irritating to have to configure, but it works just the
> same once you figure it out. :)

Have you tried Shifty extension? One of it's main features is easy
client->tag association and their configuration.

koniu

Ben Hodgens | 1 Jun 2009 05:47
Gravatar

Re: Awesome is Cool!


koniu wrote:
> On Sun, May 31, 2009 at 21:40, Ben Hodgens <ben <at> hodgens.net> wrote:
>> The only thing I wish it had was a "GUI" way to associate clients with a tag
>> (for automatic assignment) and to remember the specific predefined view per
>> tag. It's a little irritating to have to configure, but it works just the
>> same once you figure it out. :)
> 
> Have you tried Shifty extension? One of it's main features is easy
> client->tag association and their configuration.
> 

I haven't, actually. I don't know anything about it. I'll look into it, thanks!

> koniu
> 

--

-- 

Benjamin Hodgens
ben <at> hodgens.net
Home: 605-343-8835
Cell: 605-430-0601

Matthias Kirschner | 1 Jun 2009 11:03
Picon
Gravatar

Re: Awesome is Cool! (finding client 'class or instance')

Hi Ben,

* Ben Hodgens <ben <at> hodgens.net> [2009-05-31 17:38:49 -0600]:

> Which version of Awesome are you using, Matthias? Version 3.2 and 3.3 
> have drastically different configurations (3.3 is all-lua, 3.2 still has 
> some of the legacy configuration left). I can't rightly say what 3.3 
> would look like, but here's what 3.2 looks like (3.3 should be similar; I 
> think this part of the config is in lua):

Sorry about that. I use awesome since a week and currently it is
"awesome v3.3-rc4".

> -- Applications to be moved to a pre-defined tag by class or instance.
> -- Use the screen and tags indices.
> apptags =
> {
>     -- ["Firefox"] = { screen = 1, tag = 2 },
>     -- ["mocp"] = { screen = 2, tag = 4 },
> }

Yes, that was very good documented in rc.lua.

> The "class or instance" part is kinda time consuming, and why I've not 
> gotten around to doing it yet (also due to simply suspending/hibernating 
> instead of shutting down). It's queried from the clients via the xprop 
> and xwininfo tools. Something like this would be useful for finding this 
> info:
>
> #!/bin/bash
(Continue reading)

Matthias Kirschner | 1 Jun 2009 10:40
Picon
Gravatar

Webbrowsing without browser tabs (was: Re: Titlebars for Tabulous)

Hi Josh,

* Josh Rickmar <joshua_rickmar <at> eumx.net> [2009-05-31 21:04:31 -0400]:

> First of all, I tried using it by setting the layout to max so that
> every client would be maximized. The advantage of this is that the names
> of the pages would still appear at the top, so I knew how my "tabs" were
> organized. However, this method fails when trying to place another
> application on this tag or showing two or more tags at the same time.

I am very interested in that. What do you mean with "fail"? Do you mean
that than also other applications apprear as "tabs"? 

Since a few days I have configured all my applications who are able to
display tabs to ignore them and instead open everything in a new window
instead of a new tab. I am not sure if I will keep it, but until now it
feels good to have no switch between awesome window management and the
applications own window management (tabs). Before I had the feeling that
the tabs are limiting me, because I cannot decide how I would like to
view them.

So I give all web-browsers the web tag, because it does not matter for
me, if I visit a page in konqueror, epiphany, arora, elinks, or another
web browsers. And I can switch between all the different views for the
browser. Depending on which machine I am working I can use client max
(like tabbed browsing) on my 12", or for example fairv on huge screens.

The only problem I have at the moment is that I sometimes would like to
have the feature "open in background tab", to open a lot of links in the
background. That is not possible with my current setup. At the moment I
(Continue reading)

Josh Rickmar | 1 Jun 2009 12:50

Re: Webbrowsing without browser tabs (was: Re: Titlebars for Tabulous)

On Mon, 1 Jun 2009, Matthias Kirschner wrote:

> Hi Josh,
>
> * Josh Rickmar <joshua_rickmar <at> eumx.net> [2009-05-31 21:04:31 -0400]:
>
>> First of all, I tried using it by setting the layout to max so that
>> every client would be maximized. The advantage of this is that the names
>> of the pages would still appear at the top, so I knew how my "tabs" were
>> organized. However, this method fails when trying to place another
>> application on this tag or showing two or more tags at the same time.
>
> I am very interested in that. What do you mean with "fail"? Do you mean
> that than also other applications apprear as "tabs"?

If I'm using the max layout, then yes. There is no distinction between a
browser window and any other kind of client, so if I add another client
to that tag, then it would appear as a "tab" as well.

The other thing that can happen is that I show two tags at the same
time. The problem with this is that I lose any kind of tabs and each
previous tab appears as its own client. Using tabulous solves this
problem, but then again, I don't know what other "tabs" there are and
what order they are in.

In my current setup, I increase the size of the master area and then
just shove all the other windows to the side. I can then easily
reorganize them and make any window the master through
Control-MOD4-Enter. This replaces the idea of "tabs" with "previews" and
works very similar to browsers such as Shiira (mac browser) where you
(Continue reading)

Martin Stubenschrott | 1 Jun 2009 14:16
Picon

Re: Titlebars for Tabulous

On 06/01/2009 03:04 AM, Josh Rickmar wrote:

> Hi. Recently, I found out about the uzbl browser[1]. This application is
> unique in that it tries to follow the UNIX philosophy as closely as
> possible. As a result, it does not provide tabs, but leaves the problem
> of multiple pages up to the window manager (which is how I think it
> should be done).

Why should that be done by the window manager which has far less information
about the specific "problem" than the application itself.

I know that some people here just want to be elite for the sake of it, but
how can you do these things when using WM "tabs" instead of browser tabs:

1.) Decide whether to open it in a foreground or background tab.

2.) Show a throbber or something to see if the page is still loading, or already done

3.) Save the session

4.) Group tabs by a window. E.g. sometimes it can be useful to have 2 windows
    with 10 tabs each, grouped by a specific task. In your case you would have
    to open a specific tag for each of these tasks, but how would you assign
    new "tabs" to the correct window?

5.) Color coding of tabs according to which domain the belong to (lots of extensions
    do that, and it's quite useful)

6.) Google chrome opens new tabs next to the originator of where this tab was opened.
    And when you close it, it switches back to the originator. Nifty feature which
(Continue reading)

Gregor Best | 1 Jun 2009 14:25

Re: Awesome is Cool! (finding client 'class or instance')

At Mon, 1 Jun 2009 11:03:29 +0200
Matthias Kirschner wrote:

> [...]
> Hm, either I don't understand the bash script above or I misunderstood
> you in the first place. I thought you have a solution to define that
> when I start awesome on tag 1 the view mode is "max", on tag 2 it is
> "fairv", on tag 3 it is "fairh", ...
> [...]

I have a neat solution for that:

 config = { }
 config.tags = {
     { name = "α", layout = layouts[3] },
     { name = "β", layout = layouts[1], mwfact = 0.8 },
     { name = "γ", layout = layouts[3] },
     { name = "δ", layout = layouts[1] },
     { name = "ε", layout = layouts[1], mwfact = 0.28 },
     { name = "ζ", layout = layouts[6] },
 }
 tags = { }
 for s = 1, screen.count() do
     tags[s] = { }
     for i, v in ipairs(config.tags) do
         tags[s][i] = tag(v.name)
         tags[s][i].screen = s
         awful.tag.setproperty(tags[s][i], "layout", v.layout)
         awful.tag.setproperty(tags[s][i], "mwfact", v.mwfact)
         awful.tag.setproperty(tags[s][i], "nmaster", v.nmaster)
(Continue reading)

Julien Danjou | 1 Jun 2009 14:26
Gravatar

Re: Titlebars for Tabulous

At 1243858591 time_t, Martin Stubenschrott wrote:
> Of course you might not feel the need for having these features, but please tell
> me 10 proper points, why NOT having full control over tabs in your browser makes
> more sense.

Actually, most of your points are usability concerns. Problem is
that tab and all you say, IMHO, is the responsability of the
window manager.

The points you're suggesting should  be solved by hinting the window
manager. Not by doing its job. However, I admit most of the hints
needed are not formalized as of today.

Cheers,
--

-- 
Julien Danjou
// ᐰ <julien <at> danjou.info>   http://julien.danjou.info
// 9A0D 5FD9 EB42 22F6 8974  C95C A462 B51E C2FE E5CD
// Trust me.

Gmane