Hi Blackheart,
Thanks for you comments.
Quote:
Originally Posted by blackheart42  I read the documents and have a couple of questions.
In the architecture overview you show a nice modular structure. Will there be APIs defining the interaction between modules? While APIs do take time and effort to create and maintain I believe that they improve stability by isolating the modules from each other. Like DricuS I was going to try my hand at contributing to MP, but when I found out that there wasn't even an API between the core and the skin I backed off. |
There are defined interfaces between all modules. We will document all the interfaces and interactions between the modules. The documentation is still being written, as is the code. Some things have changed in the last week and will continue to change. We hope to have the core complete and all the interfaces stable and documented for the next release.
I will post new pages as they are available.
Quote:
|
In the 'Compiling' document it says that Visual C# Express is a prerequisite but is unsupported. Is there a technical reason to not support C# Express? Or is this perhaps a way to ensure that anyone who wants to develop for MP has a certain level of proficiency (assuming that anyone who pays significant money for the full package will likely have more skill than someone who just downloads the freebie). Please don't misunderstand me - establishing a minimum requirement for developers isn't necessarily a bad idea, but it will certainly reduce the number of developers. A middle ground might be to require Visual Studio for the core, but support C# Express for plugins.
|
VS C# Express is not currently supported, because no one on the team uses it and secondly with the amount of changes still happening maintaining multiple solution files is too much work.
I cannot promise a team supported VS express solution file any time soon.
VS Express can be used to compile the core (if you create your own solution file) and can definitely be used for plugin development. The problem is that we use solution folders which are not supported by VS Express. These need to be flattened out in a VS Express solution.
We are certainly not trying to exclude any developers and welcome comments and feedback, but please bear with us, because the MediaPortal II project is still in an early stage of development.
Regards,
/James