A use case that I will also present in another proposal is the need for a macro allowing non-technical users to pick an XClass, then select a list of properties, sorting criteria and filters. The macro then displays a Live Data.
In this concept, non-technical users are likely going to be confused if the list contains technical concepts.
Going back to this idea, let’s propose option 5.
Option 5 - introduce a notion categories for XClasses
This is close to option 5, but instead of a single boolean, it is possible to define a set of categories for a given XClass.
I suggest following the same conventions as the ones we use for the macros categories:
- Two special categories exist:
internalanddeprecated, both are hidden for non-technical users - XClasses without one of these categories are considered as non-technical
In term of UI this implies have a way to filter by categories:
- Option 5.1: a second filtering field
- Option 5.2: a special
category:prefix. For instance,category:photography, ormeetings category:projectmanagement. The first query returns any XClass with the photography category, the second query returns any XClass with a name containingmeetingsand part of theprojectmanagementcategory
In term of migration we’ll also need to discuss which categories to add on existing XClasses.
I’m +1 for 5.2 as it is less space consuming and I believe we want to keep the XClass picker compact.