Hi @Romanos
Just because the Dorico team use the word flow as a general term to describe a music storage container as part of recognising it may have a range of uses doesn’t mean that they necessarily specifically understand the specific conflict I highlighted - between using flows for composition - and using flows for performance breaks and formatting. Can you and the four people who were more eager to like your criticism of my suggestion (which doesn’t engage with it in any way) give me a break? I mean you didn’t actually give any indication whether or not you like my idea and why - not that I need that - you could instead have improved on it (with some detail) - I would consider either a compliment - real engagement. Do you have a better idea or is my suggestion (which rides on the coat tails of @snakeeyes021) the best one you can think of (but you just forgot to mention it)?
One addition to my suggestion - since the number of flows will become very big if flows really do become compositional units my suggestion is that the flow view I suggested in my previous post require the user to choose the version (a word I defined in my previous post) whose flows they want access to - reducing the number of possible flows to those contained in the version. Except in one situation - and this raises an issue with providing the abilities I have suggested - if there are lots of flows how is the user supposed to remember what music is contained in a particular flow? My suggestion is that when a user double clicks on a flow in the arrange view I suggested exist - (when the fact that they have named the flow isn’t enough to remind them what music is in it) - it should open in Flow view (which is either Page or galley view - but viewing just one flow). Then pressing some kind of back button returns the user to the Arrange view where flows can be added - allocated to versions - and ordered - and duplicated - and parked - and deleted. Maybe as a way to recognise the danger of forgetting that a flow can be used in multiple versions a flow would have to first be parked for all versions (I suppose there could be a way of indicating that a flow is not in use in any version) - and only then could it be deleted.
I point out that what I am calling Flow view is a kind of focus view like they have in writing programs - it hides all other music - allowing the user to work only on the flow (which might be only a small part of the piece) that they have chosen. I believe it’s an idea that would be very compatible with the problems which an iPad version of Dorico must grapple with (limited screen real estate - difficulty scrolling etc).
If my suggested functionality existed no-one need use it if they don’t wish to. They can open up their Dorico file with one version - and possibly only one flow per performance unit - and continue as they have before.