You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This will be a common UX problem in the app design
In the CharacterProfile component we currently serve the Character name and depiction, two properties that we assume will be common to all MUD characters
We want our client to be world-server agnostic, which means that we want to display whatever properties are on the Character, which we won't know for sure until run-time. Hence we would want to cycle through each triple on the Character and work out how to render it
We may need to model in the ontologies of the properties themselves whether (and how?) they will be displayed
This will be a common UX problem in the app design
In the
CharacterProfilecomponent we currently serve the Character name and depiction, two properties that we assume will be common to all MUD charactersWe want our client to be world-server agnostic, which means that we want to display whatever properties are on the Character, which we won't know for sure until run-time. Hence we would want to cycle through each triple on the Character and work out how to render it
We may need to model in the ontologies of the properties themselves whether (and how?) they will be displayed