Hi,
looks good to me. Thanks. We (I :)) will need some way to make the taglist and
tasklist look the way I want though... Anyway, I'm leaving for the trip
tomorrow and am too busy.
But I like it.
cheers
lukash
-BEGIN PGP SIGNED MESSAGE-
At 27.11.2009 10:18:42, Julien Danjou jul...@danjou.info wrote:
There's a way, but I don't see why we would need it.
awesome just knows about its basic objects, it does need to call any
other method that you may have added to the basic class, or to a
subclass of a basic class.
...it does need
At 27.11.2009 14:34:29 Uli Schlachter psyc...@znc.in wrote:
I think it would be best to keep the awesome core objects as userdata the
way
they are. You can just write your own class inheritance model in lua and use
your own tables for most of the stuff, can't you?
Yes, what I meant is that
At 27.11.2009 14:37:09 Julien Danjou jul...@danjou.info wrote:
Not sure I understand your question.
If you mean Do __index metatable fields have the same effect on
userdata and on table, yes, they are.
What I wanted to ask is whether I can operate with metatables on userdata
at all. Seems I
At 27.10.2009 09:42:25 Julien Danjou jul...@danjou.info wrote:
The reason is the same I already explained: proxied table.
Problem is that the wtable system has a problem: when you used table.*,
they do raw access (rawset/rawget) to the table, so does not trigger the
metatable __index and
At 12.10.2009 23:15:53 Julien Danjou jul...@danjou.info wrote:
That property is called margin.
This one is only used to organize widget with a layout, not to render them,
so is not used by C code, not does not belong here.
Ok, I get your point. And this is probably how our opinions on this
At 13.10.2009 14:12:10 Julien Danjou jul...@danjou.info wrote:
I am a default configuration user since awesome 3, because I don't have
time to code and tweak my own configuration, unfortunately. :)
Yeah, its pretty timeconsuming with the API changing every time you
upgrade :D
Yes, but
At 12.10.2009 10:26:20, Julien Danjou jul...@danjou.info wrote:
Also, the layouts currently use an awful.widget.layout.margins table to
specify margins for the widgets and/or tables with widgets. This has 2
drawbacks: 1. if margins are set for some dynamically created
widgets/tables in
At 06.10.2009 10:07:03 Julien Danjou jul...@danjou.info wrote:
I'll try, I just imagine it does not take the full height. But that's
not the layout work to try to resize widgets.
You're right :) And for one, the flex layout does resize them (can't help that).
Thats how my layouts behave if
At 05.10.2009 15:24:14, Julien Danjou jul...@danjou.info wrote:
At 1254693163 time_t, lukash wrote:
I tried to put something like
lua_getglobal(L, awful.widget.layout.default); to the C function that
handles the layout, but to na avail (it just pushed nil on the stack).
What's the
At 05.10.2009 16:54:56, Julien Danjou jul...@danjou.info wrote:
I see 2 question here:
- you need to get, awful, widget, then layout, then default.. to make
this works
- This is not possible, awful is not required to be loaded by awesome.
You can write your own alternative to awful.
On 18.9.2009 10:24:33 Julien Danjou wrote:
which
handles the geometry of the parent wibox,
?
It does nothing at all.
Ok, this one does nothing, the rest do.. I was just trying to make clear
the difference between the 2 kinds of layouts.
Yes, but not if the client is fullscreen or
On Thu, 17 Sep 2009 10:15:33 +0200 (CEST) Julien Danjou wrote:
There can be no layout (floating is no layout at all) so you can't
rely on the layout to resize things. This is what things like fullscreen
and all were handled totally C side.
It seems to me you are talking about
On 15.9.2009 10:47:47 Julien Danjou jul...@danjou.info wrote:
It'd be nice if your MUA can wrap lines at ~72 chars. :)
Yes, I'll try :) I'm sorry
Having layout written in C is just more limiting than having them in Lua
and brings nothings but less extendability (is this a word?).
Except for
On 08.9.2009 10:29:07 Julien Danjou jul...@danjou.info wrote:
This needs much more works than we think. Because all operations doable
on clients should be then doable on a managed-wibox.
That means tagging it, that means setting it maximized, etc.
The whole things sounds like a big API
15 matches
Mail list logo
