At 1242022527 time_t, koniu wrote: > The generated awesome.lua generally broke for me trying to index nil > values while settings descriptions for modules that weren't even > loaded (invaders :P) so I fiddled with the generator and added pulling > global environment + checks for the given module being loaded: > http://git.mercenariesguild.net/?p=awesome.git;a=commitdiff;h=cf3dc8c9849df0b9c44a7ccccb4a05e6a7e21216
Ok, you can merge it with my previous commit adding the doc generator then. > The results (in combination with fresh commit that does line breaking) > are nice: http://omploader.org/vMW5xbg Niiiiiice. :) > Remaining problems with the generator are: > > 1. the capi 'module'. It breaks the generated code by setting stuff like this: > if env then set(env.progressbar.bar_data_add, { ... > progressbar will be always nil and we're trying to index it. > > This is a version where I was trying to make this work (and then > noticed that it won't probably happen like that): > http://git.mercenariesguild.net/?p=awesome.git;a=commitdiff;h=0f6afad8febed553a77818f767065936a0744773 Yeah, C API is a problem. All objects method would be impossible to document I think since they are not exported to Lua as function, but only as methods on objects. We could change that however. I'll give it a try. > 2. i haven't fully investigated but "@class table" kind of docs are > not generated right, we get only keys 'description' and 'comment' but > nothing else (no table with @field's or anything) > > any clues on these? Nop. I think the script generating stuff does things badly. IIRC there's a couple of if for printing module and stuff, I maybe forgot table objects. There's not reason luadoc would not give this information. Cheers, -- Julien Danjou // ᐰ <jul...@danjou.info> http://julien.danjou.info // 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD // When I get sad, I stop being sad and be awesome instead. True story.
signature.asc
Description: Digital signature
