Hi,
I am willing to provide any support in implementing these features that you'd like. I admit to being the lowest common denominator in any group of my peers, but a ready hand is a ready hand.
If you have not already done so, I suggest you download the necessary tools to build Win32-GUI from the source (via the sourceforge site). You wont need to understand the C/XS layer, but once you can build Win32-GUI you'll be to do documentation changes and commit them yourself (the documentation is generated from the source code).
The gathering of descriptions and information on options has already been done (the excel file). I intend to continue this effort on events and methods and option values. This is to provide me with a global picture of what has been implemented in Win32::GUI and to enable me to build an editor based on that. For my own effort, any comments and/or support is more than welcome.
Once thing that is worth mentioning is dont be discouraged by a lack of response or comments - as with any opensource project substance produces more comments that a concept:) That said, as you build this editor you will no doubt find various issues or components missing and you should (hopefully) find these items fixed/added in Win32-GUI as you raise these issues in the tracker.
As for the editor I suggest you focus on the design GUI aspect of the app - not how the "design" will be used within a users Win32-GUI app. Breaking the link between the designer and how the design is used/generated will keep things flexible (for example, I use Loft to design a window, but then generate perl code from the loft file that - the generated perl code creates the window this way I dont need the loft packages at runtime).
Cheers, jez.
