1. Re: Splitting Win32Lib
Irv wondered:
>I was wondering, however: would it help if someone divided the
> Win32Lib into pieces that could be worked on independently?
> It's already big, and will get bigger. Breaking it up would make
> it possible to add lots of comments and documentation, and
> perhaps simplify maintenance later on.
I'm not sure that the "core" of Win32Lib needs to be split up - if people
just tell me what API to call, or send me the function, I can easily add it
to Win32Lib (yeah, I know - I'm way behind on this, too...).
I had wanted to keep the "core" of Win32Lib fairly small - a sort of basic
API, if you will. I'm not against extending Win32Lib - I'd just like to have
a basic "solid" set of functions, which it does not yet have.
I'll look into redesigning the inner event loop so that it can be extended
with data strutures and call_routine(). That way, new features such as
button bars could be added just by including the files. Currently, the
common dialogs and perhaps the menus could be given this treatment.
So perhaps I *should* try splitting it up.
I've also been promising myself to replace my Win32Lib calls with Jacques'
library calls, and now seems to be a good time as any to explore that as
well.
-- David Cuny
