The BETA version of 'Karaoke Pro Tools'
Posted: Tue May 21, 2013 5:58 am
Nearly there.......
Seems every time I say "I'm done!", I recall something else that needs work....., but, thankfully, those are very few now!
And, then, there's those 'easy' ones that I put off for awhile and when I get into it, I find that "Microsoft is not compatible with that" in some form or another (I spent all weekend working on a 'easy' one that turned out much bigger than I thought and then spent all day yesterday figuring out how to get around an issue with Internet Explorer [worked first time in Chrome and Firefox, but IE......] but got it late last night).
I was ready to 'build' today, but then I woke up this morning and realized that I need to finish the 'Enter Your Email' feature (Name works, but I have an issue with that - see below) - I want to build a storage area for those that give an Email address and as a 'reason' for them to give the email, we'll keep their PERSONAL list of songs they sing (this feature was requested on the forum). That is simple enough (as I get into finishing it - I have the 'core' done), but my issue is with the 'one-off' singer and how to avoid duplicates.
Just how should I handle the 'one-off' singer?
Here's the scenario: 'Joe' comes up to the kiosk for his first time ever singing. He is nervous about it, but wants to maybe try. When he goes to look, he is OK about entering his first name, but an Email is 'intrusive' (which is why I don't want it as a first entry point!). So, he enters 'Joe' and selects a song.
Now, 'Joe' (whom we all know, because he comes around every time there is a show - yeah, he sings the same song all the time, but we love him....... comes in - a bit later than usual, but he heads over to the kiosk and wants to enter his name (he's one of those 'weird' people that doesn't have an email account......).
And, of course, a bit later, 'Joe' comes in (the big bruiser bully that always demands his song is 'next' no matter what rotation...... - always a problem guy, but in person, it is possible to explain and you've always worked around it.....)
Well, you get the idea - multiples of one name.......
How do you handle that 'manually'? Just how should it be handled in the software?
What I did was to just 'reserve' the name for the night (configurable in the software, with a default of 5 hours....). Worked great, until 'Joe' wanted to sing another song! Yep, he was locked out as well as 'Joe' (#2 and #3...)!!!! How to allow the 'real' 'Joe' to get another song? One thing I thought of was to present them with a new login 'name' (code) that was simple enough to remember for the night (even after a couple drinks) - perhaps 'Joe1', or something - to make it unique for the night????
Scenarios like this are what makes programming so tasking - while a person may just 'handle it' in an instant, we have to tell the program what to do, step by step, in such a situation.
That's where I have been 'stuck' for awhile and now, before I can release the beta, I really have to address it.
Your thoughts and input are most welcomed!
Steve
Seems every time I say "I'm done!", I recall something else that needs work....., but, thankfully, those are very few now!
And, then, there's those 'easy' ones that I put off for awhile and when I get into it, I find that "Microsoft is not compatible with that" in some form or another (I spent all weekend working on a 'easy' one that turned out much bigger than I thought and then spent all day yesterday figuring out how to get around an issue with Internet Explorer [worked first time in Chrome and Firefox, but IE......] but got it late last night).
I was ready to 'build' today, but then I woke up this morning and realized that I need to finish the 'Enter Your Email' feature (Name works, but I have an issue with that - see below) - I want to build a storage area for those that give an Email address and as a 'reason' for them to give the email, we'll keep their PERSONAL list of songs they sing (this feature was requested on the forum). That is simple enough (as I get into finishing it - I have the 'core' done), but my issue is with the 'one-off' singer and how to avoid duplicates.
Just how should I handle the 'one-off' singer?
Here's the scenario: 'Joe' comes up to the kiosk for his first time ever singing. He is nervous about it, but wants to maybe try. When he goes to look, he is OK about entering his first name, but an Email is 'intrusive' (which is why I don't want it as a first entry point!). So, he enters 'Joe' and selects a song.
Now, 'Joe' (whom we all know, because he comes around every time there is a show - yeah, he sings the same song all the time, but we love him....... comes in - a bit later than usual, but he heads over to the kiosk and wants to enter his name (he's one of those 'weird' people that doesn't have an email account......).
And, of course, a bit later, 'Joe' comes in (the big bruiser bully that always demands his song is 'next' no matter what rotation...... - always a problem guy, but in person, it is possible to explain and you've always worked around it.....)
Well, you get the idea - multiples of one name.......
How do you handle that 'manually'? Just how should it be handled in the software?
What I did was to just 'reserve' the name for the night (configurable in the software, with a default of 5 hours....). Worked great, until 'Joe' wanted to sing another song! Yep, he was locked out as well as 'Joe' (#2 and #3...)!!!! How to allow the 'real' 'Joe' to get another song? One thing I thought of was to present them with a new login 'name' (code) that was simple enough to remember for the night (even after a couple drinks) - perhaps 'Joe1', or something - to make it unique for the night????
Scenarios like this are what makes programming so tasking - while a person may just 'handle it' in an instant, we have to tell the program what to do, step by step, in such a situation.
That's where I have been 'stuck' for awhile and now, before I can release the beta, I really have to address it.
Your thoughts and input are most welcomed!
Steve