First of all, I'd like to compliment the developers with the work sofar! I think the new skin engine is a big improvement over the old one from a users standpoint, just because it 'feels' like it's performing a lot better.
A simple suggestion concerning the configuration menu's inside the MP-II GUI:
Just create 1 setting in the external configuration application which allows you to enable/disable configuration inside the MP-II GUI. This would take away the need to manually remove all configuration options from all menu's.
Another issue about the code:
I'm a developer with quite a bit of experience (10 years+). Still, with MP-I I found it quite hard to understand the source code, not just because of the huge amount of it, but also because it's not very well documented and because I couldn't find something like a design. I'd very much like to participate in developing MP, but the lack of documentation for me was the reason not to.
I hoped that that would change with MP-II. However, when browsing through the code I got the impression that this didn't improve.
So a suggestion to encourage new developers to participate in development:
It would be very nice to have some sort of a design document which describes the architecture of MP. I'm not expecting extensive UML models with use-cases, class-diagrams, sequence-diagrams, etc, but a high-level description of the component architecture of MP would be very helpful to get an initial overview of how MP is designed.
Keep up the good work!
Dirk |