On 02.12.2013 23:39, Stanislav Ochotnicky wrote:
> Quoting Uli Schlachter (2013-12-02 22:57:58)
[...]
>> I hope this clears up the current state. Feel free to come up with
>> suggestions
>> on how to improve this.
>
> Thanks for quick reply. I don't think it makes sense to complicate core
> awesome
> codebase by introducing custom X property. It *would* be nice if completely
> full
> dynamic tagging would be easily possible but that's not really a discussion
> for
> this thread :-)
I just thought about adding a "blob" property which contains just a random
string that is completely uninterpreted by awesome, but could be accessed by
lua. This blob would however need a better name than just "blob", of course.
This isn't much work on the C side and shifts the problem into lua-land (aka "no
longer my problem" ;-) ).
If it were called "blob", I would save it in "AWESOME_BLOB" and have it
accessible as c.blob. There are some obvious problems like "who controls the
blob" where different modules both would want to save stuff in there. If this
should be solved, then "blob" would not only need a way better name, but would
also need to be a table. And I would have to think about how to serialize a lua
table into an X11 property...
What do you guys think?
Uli
--
"Do you know that books smell like nutmeg or some spice from a foreign land?"
-- Faber in Fahrenheit 451
--
To unsubscribe, send mail to [email protected].
