Reply to thread

Message

<blockquote data-quote="Janx" data-source="post: 5905588" data-attributes="member: 8835">I like your breakdown.&nbsp; I'm sold.I would add that the AssetEditor is likely a seperate screen (or modal pop-up from the Asset list screen).&nbsp; Some people merge the two (as in you see a list, and you edit on that same list screen), but functionally, they are seperate, but tied together.In defining Assets, I think we'll need to a Category aspect and some kind of flag indicating this is a Top-Level Asset.&nbsp; That way, the user can hide the baby-helper tables/blocks that are needed, but you wouldn't really use directly.&nbsp; Some of your wording refers to this same concept.So, thus far for Fields on an Asset:NameTypeCreatedBy (who first made this)CreatedOnDateUpdatedBy (who last updated this)UpdatedOnDateCategory (from some arbitrary list of categories: encounter, treasure, dungeon, etc)IsPublic (a flag so the owner can indicate he's ready for others to use it)IsHelper (a flag that indicates this is a minor table and should be hidden from the Main screen, but available to use as a sub-table)Body (this is where the table or block content and meat goes,&nbsp; The parser reads this and does what it needs to do)There's be other relational DB tables to link users to favorite Assets and record user votes, etc.&nbsp; But that's all secondary to the functionality.Does all that sound like what you expected?</blockquote>

[QUOTE="Janx, post: 5905588, member: 8835"] I like your breakdown. I'm sold. I would add that the AssetEditor is likely a seperate screen (or modal pop-up from the Asset list screen). Some people merge the two (as in you see a list, and you edit on that same list screen), but functionally, they are seperate, but tied together. In defining Assets, I think we'll need to a Category aspect and some kind of flag indicating this is a Top-Level Asset. That way, the user can hide the baby-helper tables/blocks that are needed, but you wouldn't really use directly. Some of your wording refers to this same concept. So, thus far for Fields on an Asset: Name Type CreatedBy (who first made this) CreatedOnDate UpdatedBy (who last updated this) UpdatedOnDate Category (from some arbitrary list of categories: encounter, treasure, dungeon, etc) IsPublic (a flag so the owner can indicate he's ready for others to use it) IsHelper (a flag that indicates this is a minor table and should be hidden from the Main screen, but available to use as a sub-table) Body (this is where the table or block content and meat goes, The parser reads this and does what it needs to do) There's be other relational DB tables to link users to favorite Assets and record user votes, etc. But that's all secondary to the functionality. Does all that sound like what you expected? [/QUOTE]

Verification