-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
lukash wrote:
> We agreed on a class inheritance system that will allow the user to
> make his own classes inheriting from whatever he wants
> (textbox/imagebox/graph/tag/...) with the base model being something
> like this:
> - wibox
> - imagebox
> - progressbar
> - graph
> - textbox
> - wiboxbox (dunno...whats your idea? I'd call the parent widget and
> this one wibox)
> - taglist
> - tasklist
> - screen
> - tag
> - client
>
> Did you think about having these as tables and not userdata? I had a
> look at luaclass.c and I don't understand it too well, but it looks
> like the code implementing class inheritance for userdata. If tables
> were used, none of this would be needed (pushing SLOC under 10k? :D)?
> Or am I missing something (again)?
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?
AFAIK the only problem with metatables were that a wibox' .widgets table lost
the metatables of its members. Since there won't be anything like this in
awesome 4, I think metatables should work as expected.
What would be the gain if the core used tables instead of userdata?
Uli
- --
"Do you know that books smell like nutmeg or some spice from a foreign land?"
-- Faber in Fahrenheit 451
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQEcBAEBCAAGBQJLD9VdAAoJECLkKOvLj8sG/aoH/AjiqjJSt4n1myfTRqjKmAiu
kMhSUhAgbpJ3GYp5GmaNtuniN+10JS2OcThKeh3YYFBHCo7xJInlvSrpsk/uW0FV
qkpLoTzixu/7kktrhbpQ/nS99+rk5DcfhMnuCTQz0ApYJK6/OEj2V4jZoWLKDSzB
u2NAQLJu1C3HznKrA78YGrj4aGhi8r8Uuur+88/tGTvlqGMG7C0z6ZaQJs1QxLWj
z0Mg3GrLe2wm7vytCXCpX2wDEPfBuHn3Ba6LYzfxjsD+rFVsAWV95V+3e0YOFQqz
KEqekIuuT2/N+yO49fstyd6CMd99JZ32/8Dk55Lez8NLb8R3sTP+elmFwcFHFSw=
=1ZPO
-----END PGP SIGNATURE-----
--
To unsubscribe, send mail to [email protected].
