PDK for our favourite player? Let programming begin!

[intermario_gr]

Since nobody's made a comment on the new build of QMP, I'll take the time to do so :calm: I was very pleased to see an update released yesterday but was much more pleased to see that apart from the minor bug fixes, Paul has also incorporated support for QMP-PDK in build113! It stands for "Plugin Development Kit" I suppose and will allow anyone with programming skills and a good will to develop plugins. Unfortunately, I got the will but I lack the time, for the time being at least :ermm:

I am pretty sure that QMP will improve at a rapid pace, now that the programming-part is not only one man's job! ;)

[Tokelil]

I am pretty sure that QMP will improve at a rapid pace, now that the programming-part is not only one man's job! ;)Well there still need to be someone to write the plug-ins and there aren't many around with the time and skills it seems. Hopefully QMP will bring new blood...

Personally Im quite excited about the new SkinParser interface. (Beside the whole new interface structure for inter plug-in communication) Hopefully it will make it possible to create skinned external windows. (Which I always has wanted for QueueIt, but I never finished my own skinning engine)

[acozz]

Paul, as I was reading through the plugin doc, I made note of some typos that I noticed as I went:

Pg. 3 line 5: vs should be vs.
Pg. 5 line 17 stucture should be structure
Pg. 5 line 22 refelected should be reflected
Pg. 10 line 40 “be call” should be “call”
Pg. 11 line 32 markerend should be italicized
Pg. 16 line 22 no remarks for Output plugin’s SetVolume
Pg. 18 line 11 send should be sent
Pg. 38 line 22 return type is misspelled
Pg. 42 line 33 no creation documentation for IQCDMediaList
Pg. 63 line 17 two spaces between scan and for

[Paul]

Paul, as I was reading through the plugin doc, I made note of some typos that I noticed as I went:

Pg. 3 line 5: vs should be vs.
Pg. 5 line 17 stucture should be structure
Pg. 5 line 22 refelected should be reflected
Pg. 10 line 40 “be call” should be “call”
Pg. 11 line 32 markerend should be italicized
Pg. 16 line 22 no remarks for Output plugin’s SetVolume
Pg. 18 line 11 send should be sent
Pg. 38 line 22 return type is misspelled
Pg. 42 line 33 no creation documentation for IQCDMediaList
Pg. 63 line 17 two spaces between scan and for
Thanks Acozz. How about the comprehension? Any chance someone can grok that doc to make a plug-in?

EDIT: pdk updated with these doc changes

[acozz]

I intend to update a plugin at some point to utilize the possible data exposed from the ML.

I skimmed the ML plugin doc...seemed confusing. If I hit it hard I could figure it out but it seemed like it didn't fully explain the "real-world" impact of the interfaces clearly.

For example: 6. MLView
Views can be considered a window into the Media Library. Views are what the end-user will use to navigate and display the items in their Media Library.

Um, is that the left pane in the typical ML?

In addition, I think a simple example ML plug-in or two would go a long way.

[acozz]

Apparently you read my mind before I even thought it...

[Tropics]

How about the comprehension? Any chance someone can grok that doc to make a plug-in?

fine so far. but i am clueless of what plugin would make sense there. maybe i'm just not the ml type of guy ... :silly:

[Paul]

fine so far. but i am clueless of what plugin would make sense there. maybe i'm just not the ml type of guy ... :silly:
To know if you need to make a ML plugin decide: "does my plugin need to operate on all or any of the user's media, regardless of what is playing?". If the answer is yes then you need to make a ML plugin.

[shaohao]

Hi, Paul:
The synopsis "IQCDTagInfo" should be "3.4 IQCDTagInfo".

BTW:
How about exporting a PDF version?

[shaohao]

the "Complete" module function of Encoder Module.

flags [in] no flags currently defined


But I found that flags==0 on normal complete while flags!=0 on force stop encoding.