The docs for EWL make it seem to be a container based toolkit instead of
pixel based. Still, I am finding myself having to specify exact pixel
sizes for many of the widgets that I am using (and even then, some don't
want to behave right.) Are there known bugs in this area, or am I just
abusing the library again?
It is container based and you really shouldn't have to specify the size of widgets unless there is an exact size that you want as a requirement. Maybe a piece of sample code or screenshot could help clarify what you are trying to accomplish.
What is the relative maturity of EWL? Should I be basing a production
application on it yet?
That's a pretty difficult assessment to give you. If you can't afford to maintain the code against slightly changing API's, then no I would not use it for a production application. If that is not a problem, and you can achieve your layout needs, then I don't see a compelling reason that it couldn't be used. Just remember this is development code still (like all of the EFL, though some parts are more static now) and can have drastic changes in CVS on occassion.
