Thans for collating this, it's a shame it's a bit lost in the ideas forum, but I found it :)
My main comment is the last point:
- Incorportate version control and undo/redo functionality
For version control - the critical thing here for me is rather than having this incorporated directly in the UI, instead concentrate on making true version control possible.
- version control is more than simply going back to an old version (although of course simple undo in the UI is essential)
- the real power of version control is the ability to see differences and merge changes across versions.
- the standard way to enable this is to ensure there is an underlying representation as text that has had some though applied to make it possible to merge. Think code + git.
So can I ask that there is some collaboration with the bookmark changes along with the team that is looking at the report-definition equivalent of TMDL.
Currently the report serialization is incredibly granular and verbose, and is impossible to diff+merge.
My key improvements would be:
- One json file per bookmark
- ReportSection ID can be set by user and remains stable
- Visual containers ID can be set by user and remains stable
- A readable DSL grammar for expressions (), rather than a json serializatin of an AST.
If there's a place where this is being discussed in more detail, I'd love to contribute.
