Thanks for the feedback Kevin. How will v2 affect the current framework API? Do you feel some major adjustments will need to be made or will you try to minimize that sort of impact?
There are many useful features (I've already implemented my fair share with Expression Player), but the key ones are:
1) Playlists. Not necessarily processing ASX files or other formats, but keep it simple like Expression Player were you simply provide the data structures for submitting playlists to the player. Among the normal playback handling, events should also be dispatched
from the framework as playlist items are triggered.
2) Advertisements are a big thing, but they are also very specialized in how they get implemented. VAST, which was listed on the front page, is a good starting point for preparing the data structures, though it's wise not to tightly couple the code to the
VAST protocol. That could be left as a plugin.
While not major features, commenting your code and providing API documentation (you can auto generate one using Doxygen) would make the framework more professional. I know it can be difficult at times, but Visual Studio does make it easy. Just put in three
slashes and fill in the blanks :) Grouping code into directories would also make the framework more organized, You could also label your classes with the license agreement or at least copyright at the top. This way if people do make modifications, it will
be clearly identifying which parts are yours vs there's.