Make "Simple planning" option label text much more descriptive#732
Make "Simple planning" option label text much more descriptive#732kjcole wants to merge 1 commit into
Conversation
|
(It's dynamic too.) |
|
Cool! I'll check it out. We'll need to put in the translations too - I can do that if you don't want to take that piece on.
…On Mon, Apr 13, 2026, at 11:27 PM, Kevin Cole wrote:
Close issue #646 <#646>
You can view, comment on, or merge this pull request online at:
#732
Commit Summary
• ab050db <ab050db> Make "Simple planning" option label text much more descriptive
File Changes
(1 file <https://github.com/Gig-o-Matic/GO3/pull/732/files>)
• *M* templates/band/band_form.html <https://github.com/Gig-o-Matic/GO3/pull/732/files#diff-1030a3ee6e080cf642e45c4f6fb33723c4388c6edb434ff83b2963208268635f> (21)
Patch Links:
• https://github.com/Gig-o-Matic/GO3/pull/732.patch
• https://github.com/Gig-o-Matic/GO3/pull/732.diff
—
Reply to this email directly, view it on GitHub <#732>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAWDDNVIRHC5BQSEJL6O5H34VWV3ZAVCNFSM6AAAAACXYI2AV6VHI2DSMVQWIX3LMV43ASLTON2WKOZUGI2TSMZRGEZDQMY>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
I should have considered that... I'm guessing my "solution" isn't super elegant and may not stand up to adding lots of translations in a well-structured way, but it may give better minds an idea. If wedging JavaScript in rather than taking advantage of Django's templating system isn't a great idea, perhaps a more robust but less interactive solution would be changing the " |
|
It might be even simpler just to list out the two sets of options and a pair of radio buttons. Just call it "attendance options" or something and present the two lists..?
…On Tue, Apr 14, 2026, at 10:28 AM, Kevin Cole wrote:
*kjcole* left a comment (Gig-o-Matic/GO3#732) <#732 (comment)>
> Cool! I'll check it out. We'll need to put in the translations too - I can do that if you don't want to take that piece on.
>
I should have considered that... I'm guessing my "solution" isn't super elegant and may not stand up to adding lots of translations in a well-structured way, but it may give better minds an idea.
If wedging JavaScript in rather than taking advantage of Django's templating system isn't a great idea, perhaps a more robust but less interactive solution would be changing the "`Simple planning`" column / field to "`Expanded attendance options`" (or similar: "`Extended set`", "`Full set`", etc.) and reversing the logic on the checkbox: When checked (the default), the full set of attendance options is available. When unchecked the reduced set of attendance options is available. Then go back to letting Django's templating system do the heavy lifting.
—
Reply to this email directly, view it on GitHub <#732 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAWDDNQSVNBPRKC2OWVIBVD4VZDKTAVCNFSM6AAAAACXYI2AV6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DENBUGY4DOMJXGM>.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
I changed the text to just "use yes/no/maybe responses" - is that clearer? |
Yes... but, perhaps indicate what that is in contrast to. Perhaps something akin to: |
|
Seems clunky. I'm going to leave it this way for now - it's better what was there before. I'll think about something better. |
|
(I've converted the PR to draft until there's a longer-term plan.) |
2 participants
Close issue #646