- Control Structure Pane - For example, RadForm has a RadTitleBarElement, which contains no styles, because they are inherited from the RadTitleBar control. Here we can add a note, which says from which control the styles are inherited:
- Design / Preview Pane - Click on an element from the Design view and select it into the control element tree.
- Elements Pane - Add an option to expand all sub-nodes in the Control Structure tree. Save the setting for the filter chosen by the user.
- Find repository usages: Add an option to expand all sub-nodes.
- Repositories - Sort applied repositories on top or in another list. Currently, we can see all the applied only when we click "Show only applied repositories".
- Repositories - Add an option to filter the repositories by type(font, fill, border, image, and so on). Currently, we can filter them only by name.
From a planning perspective, I worry that there are too many items here to do effective prioritization.
For example, I recently submitted a support ticket regarding the last item "PropertyWindow - Add an option to allow the property window to take all the available space, thus allowing you to see more property settings." . I had submitted this intending to highlight that it feels like a bug (imagine if you opened up a "File>" menu in office, and only 3 items appeared and you had to scroll to reach "Close"... it impacts basic usability. It's almost like if you tried to use Excel, and the "grid" portion of the active workbook didn't fill in the space to the bottom area of the window... ).
However, "Add an option to filter the repositories by type" is clearly a feature request, a desire to add more functionality than originally planned. I was directed here to vote on this item, but I worry that what may be a relatively low level of effort of setting a dock/fill + CanResize property may be lost against a monolithic task of a large and compound scope.
Attached shows that the non important content area can expand, while the primary data cannot. If the users should be able to vote in a way that lets features and fixes get prioritized, then each feature and fix should be separate.
