On 08.9.2009 10:29:07 Julien Danjou <[email protected]> wrote: > This needs much more works than we think. Because all operations doable > on clients should be then doable on a managed-wibox. > That means tagging it, that means setting it maximized, etc. > > The whole things sounds like a big API redesign.
Well, I don't know the code too well, so I can't imagine what it would take. I'm not so skilled in C, my C++ instict tells me: Make a predecessor to client and wibox that will have all the attributes from client that will be common to client and wibox alike. Then inherit from it in the client and wibox. Then things should work as before, and wibox should act as a managed window now :) > Maybe wibox should be just clients? Its definately a possibility, it depends on how many attributes they have that are different. If its too many, I think it could become a mess. Also, note that if you make wibox a client, it means you can put it in a client widget. Not necessarily a bad thing, but by design unneeded one and maybe it could cause problems? lukash PS: Sending this from crappy webmail as I'm at work, I hope it will keep the thread intact (if not, ignore this, I'm sorry) -- To unsubscribe, send mail to [email protected].
