1. Re: Win32libEx -- Richedit, common controls and MDI
SR Williamson wrote:
> 1) *Someone* that knows how should integrate Wolfgang Fritz's System Tray
> work into the win32lib (unless it's already there and I just didn't see
> it). It's a common enough feature that at least *I* - and probably quite a
> few others - think it should be part of the de facto standard for
> programming Win under Eu.
I disagree. Most people won't be coding system tray applications. If it works
well as a stand-alone library, it should remain that way. If it requires
changes to Win32Lib, then only the minimal changes should be made to support
it, so it can remain a stand-alone library.
> 2) I know there is a problem with namespaces, but is there *any* way to
> break the lib into at least 2 or 3 logical parts?
No, not until namespaces are resolved. Anything before that is just asking to
break something that's not currently broken.
> Should pixmaps be mixed with text based controls?
Until namespaces are resolved, I think these kinds of questions are a bit moot.
IMNSHO, there's so much interdependance that you don't really gain that much by
trying to break Win32Lib into independant libraries. The issues are:
- API routines (like create, etc) need to know about all the controls
- Win32Lib is large, but not *that* large
Once namespaces are resolved, then a sensible way to break the project up can
be determined. But I don't think that you'll ever get independance without
making serious changes to the high-level routines, putting class-based
routine_id callbacks at the top level, like Llama did. And the cure turns out
to be worse than the disease.
> It can also be daunting for beginners to have to search/scroll
> 70-80 pages to find the correct syntax for a lib call.
The best solution here would be to fix the generated documentation, since that
should be the user's reference documentation - at least, if they are a newbie.
> Finally, can someone give me a nontechnical explanation of namespaces?
Namespaces refers to the scope of a routine - what other routines can see (and
share it), and what routines it is hidden from.
In Euphoria, there are three scopes:
1. Global: Everyone can see it.
2. Local: Everyone in the include file can see it.
3. Routine local: Everyone in the routine can see it.
Other languages, of course, support other options.
-- David Cuny
-------------------------------------------------------
