Reply to thread

Message

<blockquote data-quote="MariachiElf" data-source="post: 55030" data-attributes="member: 20753">I think I just figured out what to do about the problem of what are the exact details of how to associate tags to Media Elements.I was putting the burden on the UI Plugins to manage the UI interaction for inserting/updating tags.&nbsp; However that's not their job, and that's a lot of boilerplate code duplicated everywhere.&nbsp; UI Plugins shouldn't make calls to the InputDevice Plugins directly.&nbsp; They should make calls to the central manager.&nbsp; Just like the Input Device Plugins don't really care what or how many UI Plugins there are, UI Plugins don't want nor care to keep track of Input Device Plugins.They simply make an API call to the central manager like AssociateTag( mediaElement, Command ).The central manager will then know how to interrogate for each inputDevice and present the list to the end user and after the end user chooses their device it can make an API call to the Input Device Plugin UI to request a Tag, then make the API to call the Input Device Plugin again to insert or update the mediaElement and tag/Command association.The more I think about this central manager piece, the more I begin to believe that this &quot;central manager&quot; role really belongs as part of the core of MP.</blockquote>

[QUOTE="MariachiElf, post: 55030, member: 20753"] I think I just figured out what to do about the problem of what are the exact details of how to associate tags to Media Elements. I was putting the burden on the UI Plugins to manage the UI interaction for inserting/updating tags. However that's not their job, and that's a lot of boilerplate code duplicated everywhere. UI Plugins shouldn't make calls to the InputDevice Plugins directly. They should make calls to the central manager. Just like the Input Device Plugins don't really care what or how many UI Plugins there are, UI Plugins don't want nor care to keep track of Input Device Plugins. They simply make an API call to the central manager like AssociateTag( mediaElement, Command ). The central manager will then know how to interrogate for each inputDevice and present the list to the end user and after the end user chooses their device it can make an API call to the Input Device Plugin UI to request a Tag, then make the API to call the Input Device Plugin again to insert or update the mediaElement and tag/Command association. The more I think about this central manager piece, the more I begin to believe that this "central manager" role really belongs as part of the core of MP. [/QUOTE]

Verification