New Windows library + WIPI
I'm writing a new Windows library, that will do what Win32Lib does now. Why?
First, because it's a challenge to start such a project. Also, because I think
Win32Lib is still running from the original design. A lot has changed, a lot has
been added. But there's still a lot of backward compatibility that makes the
library unnecessarily large and complex. It also has so much different routines,
some of which do the same thing. And there are different naming conventions for
constants and routines, that doesn't really make it look nice. I think it would
be nice, if Win32Lib (and also IDE) would be totally rewritten from scratch.
The new Windows library will be designed to be very modular, extensible, and
easy to use, both in code and with an IDE. I got the idea from my previous
projects (EuControls, LayoutPanels, Win32Dib, ...) which will become part of the
core functionality.
This means I won't be able to work on WIPI: Win32Lib IDE PlugIns. This would be
a plugin-mechanism for IDE. Looking at the code of IDE, and what I want to
achieve with WIPI, I conclude that IDE isn't designed to provide the necessary
functionality/extensibility for WIPI. Perhaps a limited plugin-mechanism could be
implemented, but not WIPI as I have it in my head. That was also one of the
reasons I decided to start the new Windows library. If the library is designed
(from the start) to support an IDE, and a plugin mechanism, I think a new IDE
will be a lot easier to write.
I appologize to Judith, for having to quit the WIPI-project, and I ask if there
is anybody who would consider taking it over, and would invest its time in a
project that is really necessary for IDE to grow stronger.
--
tommy online: http://users.telenet.be/tommycarlier
tommy.blog: http://tommycarlier.blogspot.com
Euphoria Message Board: http://uboard.proboards32.com
|
Not Categorized, Please Help
|
|
