That is a great idea. I have a set of working tabs, so with a little creative photo-shopping I can do a graphical mock-up too. (Not that I can actually achieve what I can dream in photo-shop. But it is a target to aim for.) And don't worry about throwing ideas out there. I'm find it stimulating and you are already causing me to improve on my vision. I look forward to seeing your ideas, sharing my own, and fusing the best of both worlds within the scope of what I can actually code. If you are interested enough to do some coding, maybe we can share that part too. No pressure though. No obligations. Consider it an invite.
But if you are interested, and once we hammer out a draft vision, I could focus on the tab and roster framework in the near term, get that into a stand-alone modular state, and then turn you loose with it to take it in whatever feature direction you choose while I focus on another feature. Programing by committee! What could go wrong? lol
Worst case, we wind up with two roster programs covering two visions and there would be nothing wrong with that. Anyway. Let me know what you are game for. I'm flexible. And weather you choose to be a suggestion person or a hands-on coder, this is a project I'm excited to do.
-CW
"Of COURSE the laundry is clean. The cat is sleeping on it, isn't she?"
But if you are interested, and once we hammer out a draft vision, I could focus on the tab and roster framework in the near term, get that into a stand-alone modular state, and then turn you loose with it to take it in whatever feature direction you choose while I focus on another feature. Programing by committee! What could go wrong? lol
Worst case, we wind up with two roster programs covering two visions and there would be nothing wrong with that. Anyway. Let me know what you are game for. I'm flexible. And weather you choose to be a suggestion person or a hands-on coder, this is a project I'm excited to do.
-CW
"Of COURSE the laundry is clean. The cat is sleeping on it, isn't she?"