I would suggest an additional quick win: the ability to define a compound time signature with another definition that is equal.
For example 3/4|4/4 displayed as 7/4.
You know I love all of you beautiful users, but one thing I don’t love is assumptions about how easy or otherwise any given feature might be to implement.
After the release, can you pick an “easy” feature that you implemented and tell us all how you did it?
The double-tap dot?
Nah, that would be too easy.
Absolutely certain that whenever it arrives the update will be great - whether with new features or improvements on old ones. Certainly a Christmas present I won’t be returning ![]()
Folks, you can’t even imagine how true this is. Making jokes about it just hurts us software developers …
Complex applications are complex, consider the Bible has about a million words. How many lines of code in Dorico did I hear? I think we’re past a couple million. And unlike the Bible they’re all interconnected. Change one and it may have effect elsewhere (we try to design to prevent this but you can only go so far). And the developers have to keep all those millions in their head, understand it conceptually at different levels of abstraction.
So you make a one line change - you folks have no conception of how much test has to go into insuring there’s no ripple from that one line. The line may have design or API implications, or backwards compatibility. These require discussion with your colleagues to understand the implications of it, so on and so on.
So sure, there are one liners that are trivial fixes - they happen every day (but interestingly they are usually fixes, rarely are there one liner features), but you folks have no possible way of knowing what is easy and what is hard, so yes Please Stop Saying It’s Easy or even joking about it, it’s not funny.
“Everytime a forum says ‘it’s easy to code’, a developer loses his wings.” ![]()
![]()
consider the Bible has about a million words
My text file of the King James Bible is 4,305,838 characters; 852,260 words, and 31,299 lines.
It’s a 4.3 Mb text document. The Dorico app by itself is over 200 times the size!!
correction: ‘a developer gnaws his own wings off’
Just reading the more-heat-than-light about the online shop and its impact on releases: What are we expecting at the moment, a 5.1? 5.5? or a 6.0?
I’m sorry @dspreadbury , I certainly didn’t mean “easy” in that it was easy to make… I meant that it was an “easy win”.
You know I’m going to love it no matter what you guys DO add to Dorico, it’s all great, whether it’s things I don’t use personally, or that I might not notice at the surface, or things that I can easily see for myself.
We love you, too. And certainly does Michel Edward.
Daniel has thicker skin than me, I hate dealing with users. They stick me in a closet with a slot to feed pizza’s into
But this is a seriously good group of people here on the forums …
And unlike the Bible they’re all interconnected.
I think there might be people who disagree with this.
I was going to post a comment, but I restrained myself! ![]()
Me too, lol.
I recommend leaving that side conversation there, before anyone ends up too far off-topic for the Dorico forum.
You are right!
Is it true that we are one day closer to release?
Is it true that we are one day closer to release?
It’s just over this next hill. ![]()