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
{{ message }}
This repository has been archived by the owner on Dec 26, 2022. It is now read-only.
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
The text was updated successfully, but these errors were encountered:
We may be able to use shapes to generate a form, although auto-generating forms totally would lack the finesse of a human designer - for reading on this see this article on the subject
There is a (work-in-progress) UI ontology which could be used to represent and store form data, accessible from the ontology itself. When the form structure could be fetched in this way, it could be rendered following from the data's schema itself
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 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
The text was updated successfully, but these errors were encountered: