MediaPortal Forum - View Single Post

fabriceD06 · 2008-01-11, 18:12

Hello,

In context MP2 - TVE3 engine, i have question about plugin development: is it plan to create common API library between MP UI and tve3 engine because some util code are only available in MP front end and not in TVE3,

example: When i need to log some information in my common library i don't would know if my library running on client or server side, i would call Logger.info (...).
Moreover i think it is more easy to create the project references of plugin client and server on common MP library available both side and import only one namespace instead to say i cannot made this reference on server side or client side or it same class but not same namespace.

it is the same for some methods in class Utils (for date, file manipulation, process manipulation, size convertion ....) and GlobalProvider

And about Assembly Loader in MP 1, it doesn't support assembly reference , ex if my process plugin TV VideoConvertor client try to be load in process plugin code and has a reference on Windows plugin TV videoConvertor Core, if the reference is missing the plugin is not loaded. it avoid to manage in client plugin to if the core library or core plugin is present. And if my plugin client depends of TVE3 plugin Client , if the TVE3 plugin client cannot connect to TVE3 server , the status of plugin is "Failed or Degraded" then all depends are not started instead each tve3 plugin need to check if the connection to TVE3 server is good or not.

Moreover if the reference feature exists it is possible to share some code between core plugin - client plugin.

I am not sure it is very clear

but i think some improvement can be made on plugin management framework can made the plugin development more easy

Best Regards
Fabrice

2008-01-11, 18:12	#1 (permalink)
fabriceD06 Portal Member Join Date: Jan 2007 Location: Nice Age: 30 Posts: 123 Thanks: 4 Thanked 12 Times in 3 Posts Country: My System	About new MP2 API Hello, In context MP2 - TVE3 engine, i have question about plugin development: is it plan to create common API library between MP UI and tve3 engine because some util code are only available in MP front end and not in TVE3, example: When i need to log some information in my common library i don't would know if my library running on client or server side, i would call Logger.info (...). Moreover i think it is more easy to create the project references of plugin client and server on common MP library available both side and import only one namespace instead to say i cannot made this reference on server side or client side or it same class but not same namespace. it is the same for some methods in class Utils (for date, file manipulation, process manipulation, size convertion ....) and GlobalProvider And about Assembly Loader in MP 1, it doesn't support assembly reference , ex if my process plugin TV VideoConvertor client try to be load in process plugin code and has a reference on Windows plugin TV videoConvertor Core, if the reference is missing the plugin is not loaded. it avoid to manage in client plugin to if the core library or core plugin is present. And if my plugin client depends of TVE3 plugin Client , if the TVE3 plugin client cannot connect to TVE3 server , the status of plugin is "Failed or Degraded" then all depends are not started instead each tve3 plugin need to check if the connection to TVE3 server is good or not. Moreover if the reference feature exists it is possible to share some code between core plugin - client plugin. I am not sure it is very clear but i think some improvement can be made on plugin management framework can made the plugin development more easy Best Regards Fabrice Last edited by fabriceD06; 2008-01-12 at 15:57.