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
When creating or editing new object, whether a class or an individual in the "Entities" tab, the individual property / assertions sorting is quite unclear:
Assertion : it would be great if we could have a configuration where we state the order in which assertion should be displayed. Suggestion order:
object property + data property + class description : order by predicate name, then object name (based on what is in View > Render options)
That would be great !
PS : I have tried to look around for existing solution but never found anything complete. please excuse me in advance for wasting your time if it already exists somewhere...
PS2 : this issue could be seen as related to issue #5
The text was updated successfully, but these errors were encountered:
I also strongly vote for lexicographical sorting in the "Property assertions" view (as in the related "Descriptions" view of the "Individuals by class" tab) to find assertions more quickly.
I implemented a basic sorting based on the displayed name. (No additional sorting options are implemented). For my use cases this is sufficient. See (#1235) .
When creating or editing new object, whether a class or an individual in the "Entities" tab, the individual property / assertions sorting is quite unclear:
Assertion : it would be great if we could have a configuration where we state the order in which assertion should be displayed. Suggestion order:
object property + data property + class description : order by predicate name, then object name (based on what is in View > Render options)
That would be great !
PS : I have tried to look around for existing solution but never found anything complete. please excuse me in advance for wasting your time if it already exists somewhere...
PS2 : this issue could be seen as related to issue #5
The text was updated successfully, but these errors were encountered: