JP Honeywell
30 minutes ago
@The Harvest is Ready Yeah, I see your point. You have to make sure the chord data stays where it should. That makes perfect sense.
[Just out of curiosity, have you tried looking at the newStage view on an Android phone or tablet? Does it display the way you would expect it to? I ask because it seems like a lot of space between Transpose div and currentslide div. Probably because of the padding-top:122px in the css file? I wonder if that could be a percentage of the vertical screen dimension instead of a hard coded value? (I did web application development 20 years ago but have forgotten much of what I ever knew about css.)]
I like the features of the standard Stage view that you left in the newStage view. The slide #/verse #, the clock, the Notes, etc. But then you made newStage much better than the standard Stage view with the ability to change the font size on the fly. In my opinion, that feature should be built-in to the standard Stage View.
So, maybe you could rename newStage to ChordView and then make a better version of the standard Stage view. Something that takes advantage of the Fonts folder like the other custom Stage views. Maybe call it StagePlus? ;)
I can think of a few other features to consider for StagePlus :
1) When advancing to the next slide, highlight nextslide (just as currentslide was highlighted) and scroll nextslide up so readers/singers don't lose their place.
2) Identify which fonts are in the Fonts folder and allow on-the-fly font selection from a dropdown menu
3) Allow the clock to be resized/repositioned and choose color/font. Bottom center seems like a good location but who knows?
4) Maybe make Notes appear in a different place like the bottom of the screen. Where they are now seems to be a floating region that can have a negative impact on the currentslide div.
Well, enough brainstorming for now. :) You're doing a heck of a job helping us folk struggling with this tool. God bless.
JP Honeywell 30 minutes ago @The Harvest is Ready Yeah, I see your point. You have to make sure the chord data stays where it should. That makes perfect sense.
[Just out of curiosity, have you tried looking at the newStage view on an Android phone or tablet? Does it display the way you would expect it to? I ask because it seems like a lot of space between Transpose div and currentslide div. Probably because of the padding-top:122px in the css file? I wonder if that could be a percentage of the vertical screen dimension instead of a hard coded value? (I did web application development 20 years ago but have forgotten much of what I ever knew about css.)]
I like the features of the standard Stage view that you left in the newStage view. The slide #/verse #, the clock, the Notes, etc. But then you made newStage much better than the standard Stage view with the ability to change the font size on the fly. In my opinion, that feature should be built-in to the standard Stage View.
So, maybe you could rename newStage to ChordView and then make a better version of the standard Stage view. Something that takes advantage of the Fonts folder like the other custom Stage views. Maybe call it StagePlus? ;)
I can think of a few other features to consider for StagePlus : 1) When advancing to the next slide, highlight nextslide (just as currentslide was highlighted) and scroll nextslide up so readers/singers don't lose their place. 2) Identify which fonts are in the Fonts folder and allow on-the-fly font selection from a dropdown menu 3) Allow the clock to be resized/repositioned and choose color/font. Bottom center seems like a good location but who knows? 4) Maybe make Notes appear in a different place like the bottom of the screen. Where they are now seems to be a floating region that can have a negative impact on the currentslide div.
Well, enough brainstorming for now. :) You're doing a heck of a job helping us folk struggling with this tool. God bless.