Re: [RFC] widget attribute unification

2009-10-13 Thread Julien Danjou
At 1255460904 time_t, Lukas Hrazky wrote: > Not if they are independent of each other. I see its not your problem though. And what? Tons of project are "independant of each other" and collaborate with common infrastrcture. In our world, never heard of Freedesktop specifications? > Not thousand, j

Re: [RFC] widget attribute unification

2009-10-13 Thread Julien Danjou
At 1255461396 time_t, Lukas Hrazky wrote: > Does this function exist > in some way or would it need to be implemented? Would it work if you > set the margins in the constructor? Not sure which function you are talking about. If you're talking about my bad idea of adding attribute to class via Lua,

Re: [RFC] widget attribute unification

2009-10-13 Thread Lukas Hrazky
On Tue, 13 Oct 2009 18:08:34 +0200 (CEST) Julien Danjou wrote: > OTOH, you can imagine something like: > > add_property_on_class(wibox, "margins") > Then: > mywibox.margins > become an attribute of any sort. > > But I don't think setting blindly > "mywibox.margins = somestuff" > without knowin

Re: [RFC] widget attribute unification

2009-10-13 Thread Lukas Hrazky
On Tue, 13 Oct 2009 18:03:23 +0200 (CEST) Julien Danjou wrote: > At 1255447839 time_t, lukk...@email.cz wrote: > > And besides, you could have 2 modules implementing a widget layout > > system, and will both wanna use the same margins (the difference between > > them being totally unrelated). In

Re: [RFC] widget attribute unification

2009-10-13 Thread Julien Danjou
At 1255449073 time_t, Uli Schlachter wrote: > In lua, (more or less) everything is a table and one can easily add new keys > to > them. Can we somehow make the "kernel" treat the widgets more like a table so > that on can add new keys to them without "registering" them somewhere? Or have > some ki

Re: [RFC] widget attribute unification

2009-10-13 Thread Julien Danjou
At 1255447839 time_t, lukk...@email.cz wrote: > And besides, you could have 2 modules implementing a widget layout > system, and will both wanna use the same margins (the difference between > them being totally unrelated). In which one will you store them? They build a common infrastructure. Not

Re: [RFC] widget attribute unification

2009-10-13 Thread Uli Schlachter
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 lukk...@email.cz wrote: > At 13.10.2009 14:12:10 Julien Danjou wrote: >> Yes, but imagine you have 2 modules implementing both a widget layout >> system. Each will want to use .margins to store margins, but maybe one >> system use a system with pixe

Re: [RFC] widget attribute unification

2009-10-13 Thread lukkash
At 13.10.2009 14:12:10 Julien Danjou 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 imagine you have 2 mod

Re: [RFC] widget attribute unification

2009-10-13 Thread Julien Danjou
At 1255430006 time_t, lukk...@email.cz wrote: > Ok, I get your point. And this is probably how our opinions on this matter > differ: > You want the awesome code to be as clean as possible, to have no code > somewhere where its not needed, while maybe favorizing the C side a bit. > I, OTOH, feel we

Re: [RFC] widget attribute unification

2009-10-13 Thread lukkash
At 12.10.2009 23:15:53 Julien Danjou 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 matter differ

Re: [RFC] widget attribute unification

2009-10-12 Thread Julien Danjou
First of all, let me introduce something I need. From now on in this email and probably everywhere, I'll take about kernel land (awesome C core) and userland (everything that is Lua, awful part of it). Consider awesome as an OS like FreeBSD (oh no, am I writing that?), where awesome is the kernel

Re: [RFC] widget attribute unification

2009-10-12 Thread lukkash
At 12.10.2009 10:26:20, Julien Danjou 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 this way, thei

Re: [RFC] widget attribute unification

2009-10-12 Thread Julien Danjou
Hi, At 1255274554 time_t, lukash 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 this way, their margins are

[RFC] widget attribute unification

2009-10-11 Thread lukash
Hello list, after playing with the layouts and trying to create some more complex panel, I figured the textbox widget is quite highly customizable, while the imagebox is rather lame :) Also, the layouts currently use an awful.widget.layout.margins table to specify margins for the widgets and/or t