THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - TsT (TsT)
Attached to Project - awesome
Summary - capi.lua module for every awesome C API objects
Task Type - Feature Request
Category - Lua libraries
Status - Unconfirmed
Assigned To -
Operating System - All
Severity - Low
Priority - Normal
Reported Version - 3.4.11
Due in Version - Undecided
Due Date - Undecided
Details - Hello,
Awesome provide a lot of lua object in global space (just take a look to the
doc)
My work target to move everything outside the global environment.
The capi.lua (and modutils.lua) modules will not break compatibility.
We must change every modules that use the awesome object before thinking about
removing the compatibility.
I already successfully tried to modify every lua component to clean the global
environment.
But also rewrote lot of thing. For now it's hard to publish clean diff due to
huge number of changes.
My next step is to publish sample of use of the capi module.
And after publish the entire diff of beautiful, naugty and every components of
awful...
To be continue...
More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=977
You are receiving this message because you have requested it from the Flyspray
bugtracking system. If you did not expect this message or don't want to
receive mails in future, you can change your notification settings at the URL
shown above.
--
To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
