Reply to thread

Message

That's exactly the type of feedback I was looking for!

-- Media Location
I think adding an optional Media Location is a good idea, that way the Media Type can be used as a human friendly name to be presented to the end user, and the optional Location could be used to clarify the location. Type, Location, and ID would all be submitted back to the UI.

-- Use UI Plugin ID
Didn't know there was an ID, much better. Replace UI Plugin Name above with UI Plugin ID.

-- Media Label
I keep going back and forth with this one. Is there any UI interaction directly from this database. I certainly agree that if there is, then this text field is most useful. On the one hand the user requested the "tag", the only thing that truly understands how to interact with the Element associated to that tag is the UI Plugin. So how about this. I'll add a "command" to the "Tag" table that way when the UI associates the tag to the element the user can choose then what is meant by the tag. To keep things easy to use I don't think a confirmation window is appropriate here. I'm also concerned about keeping things updated. I don't want to add a second copy of the title of a Media Element if I don't have to because I don't know how they would be kept in sync. The last thing I want is for the UI devs to have to manage not only their own label for this thing in their own DB, but also the copy of it in the Master DB.

On that note, I personally feel that Elements really have many names and there really should be an "Element Name" table just for tracking that.

Thanks for the feedback! Keep it coming this is getting good.

[/QUOTE]

<blockquote data-quote="MariachiElf" data-source="post: 54900" data-attributes="member: 20753">That's exactly the type of feedback I was looking for!-- Media LocationI think adding an optional Media Location is a good idea, that way the Media Type can be used as a human friendly name to be presented to the end user, and the optional Location could be used to clarify the location.&nbsp; Type, Location, and ID would all be submitted back to the UI.-- Use UI Plugin IDDidn't know there was an ID, much better.&nbsp; Replace UI Plugin Name above with UI Plugin ID. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />-- Media LabelI keep going back and forth with this one.&nbsp; Is there any UI interaction directly from this database.&nbsp; I certainly agree that if there is, then this text field is most useful.&nbsp; On the one hand the user requested the &quot;tag&quot;, the only thing that truly understands how to interact with the Element associated to that tag is the UI Plugin.&nbsp; So how about this.&nbsp; I'll add a &quot;command&quot; to the &quot;Tag&quot;&nbsp; table that way when the UI associates the tag to the element the user can choose then what is meant by the tag.&nbsp; To keep things easy to use I don't think a confirmation window is appropriate here.&nbsp; I'm also concerned about keeping things updated.&nbsp; I don't want to add a second copy of the title of a Media Element if I don't have to because I don't know how they would be kept in sync.&nbsp; The last thing I want is for the UI devs to have to manage not only their own label for this thing in their own DB, but also the copy of it in the Master DB.On that note, I personally feel that Elements really have many names and there really should be an &quot;Element Name&quot; table just for tracking that.Thanks for the feedback!&nbsp; Keep it coming this is getting good.</blockquote>[/QUOTE]

[QUOTE="MariachiElf, post: 54900, member: 20753"] That's exactly the type of feedback I was looking for! -- Media Location I think adding an optional Media Location is a good idea, that way the Media Type can be used as a human friendly name to be presented to the end user, and the optional Location could be used to clarify the location. Type, Location, and ID would all be submitted back to the UI. -- Use UI Plugin ID Didn't know there was an ID, much better. Replace UI Plugin Name above with UI Plugin ID. :) -- Media Label I keep going back and forth with this one. Is there any UI interaction directly from this database. I certainly agree that if there is, then this text field is most useful. On the one hand the user requested the "tag", the only thing that truly understands how to interact with the Element associated to that tag is the UI Plugin. So how about this. I'll add a "command" to the "Tag" table that way when the UI associates the tag to the element the user can choose then what is meant by the tag. To keep things easy to use I don't think a confirmation window is appropriate here. I'm also concerned about keeping things updated. I don't want to add a second copy of the title of a Media Element if I don't have to because I don't know how they would be kept in sync. The last thing I want is for the UI devs to have to manage not only their own label for this thing in their own DB, but also the copy of it in the Master DB. On that note, I personally feel that Elements really have many names and there really should be an "Element Name" table just for tracking that. Thanks for the feedback! Keep it coming this is getting good.[/quote] [/QUOTE]