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
Showing all possible relation all the time can be overwhelming and confusing for someone who is interested in only one wordnet because a large percentage of the relations are irrelevant. We could add some feature to filter out those that are not used by a particular wordnet, perhaps by adding HTML classes, CSS, and a bit of javascript, or through custom builds that use the project information.
The text was updated successfully, but these errors were encountered:
How do we go about this? By filter do you mean adding search functionality to the documentation page? And also how do we know the relations that are not used by a particular Wordnet and also what should be the first thing a user sees when he opens the documentation page?
Then when a user selects some wordnet (through a combobox on the page, or a URL parameter, or something), a Javascript function goes through each <article> and adds the .hidden class if the relation is not part of the selected wordnet. If no wordnet is selected (the default), all relations are shown.
Showing all possible relation all the time can be overwhelming and confusing for someone who is interested in only one wordnet because a large percentage of the relations are irrelevant. We could add some feature to filter out those that are not used by a particular wordnet, perhaps by adding HTML classes, CSS, and a bit of javascript, or through custom builds that use the project information.
The text was updated successfully, but these errors were encountered: