Darell
Flashaholic
OK, I've done this once before, and apparently didn't learn my lesson. So I'm doing it again. Those of you who are familiar with the Bflex, know that George and I made a Bicycle UI for it. That circuit now has a shared menu, and a choice of three UIs. Fixed, portable and bicycle. And they all work great, if I do say so myself... and I do.
So it turns out that most folks (or at least a large percentage) who are buying the Bflex are using it for bicycle lighting. So George and I agreed that a bicycle-only UI would be in order. In fact, we even have a secret weapon in the wings who is designing a new bicycle light around this board, but that's all top secret and hush-hush, so don't make me keep talking about that until the time is right. I'd hate to have to kill you. Edit: The word is out. It is the MinT, shown here: http://candlepowerforums.com/vb/showthread.php?t=172053
The advantage of a bicycle-only UI is that the menu won't need to be shared, and you won't have to stumble over menu options that make no sense on the bicycle. The menu will be easier to enter than in the current UIB that needed to use the same scheme as the other UI's. The menu also won't be needed as much. The three-UI Bflex is very flexible and fantastic for so many uses. But once you put a Bflex into a light housing, you aren't going to use the other UIs... so UIB2 will be born.
As I said initially, I've done this before. But I didn't do it here - I did it on the MountainBikeReviewForums, and got some great input from bikers who are also lighting guys (many of you are here, I see!). This time, I'm going to conduct the process on CPF to get input from light guys who are also bicyclists. Should be interesting. To see how it went before, go here
Please note that I'll be copying and pasting from the initial post to avoid cramping my fingers.
-----------------------
Now is your chance to be heard!
Everything that the uController on the bFlex can do is controlled by a single momentary button that can be mounted remotely, or stay on the board. There are two ways to enter info via that button. A Click and a Press. Two distinct actions, one that releases the button immediately after use, and the other that holds the button down for a moment until the effect is achieved. George and I have spent countless hours, and have refined after many months and even years how the UIF and UIP function with that single button. I've learned quite a bit in this process, and would also like some fresh ideas from folks who aren't as mired in the details as I can get.
In my next post, I will give the outline of what I'm thinking, and see how it floats. I will also have some questions to see what sort of direction this should go.
Everybody have your thinking caps on? Let's have your input! There are no promises that your ideas will be incorporated, but I can guarantee that it'll help shape the final product. I have plenty of ideas on how to incorporate most of this, and I know from experience much of what does and does not work in the real world. I also have experience actually using my first UIB - and what I do with this UI will be largely based on the improvements that I'd like to see in the first UIB.
Let me be very clear here that I do not do the coding or the circuit design. That's all George, and he stamps his name on the boards to prove it! Plus he's reading this, so I can't secretly take more than my share of credit. My job is to do all the *really* hard thinking. I try to figure out what the user will want, and how to make it the most practical to use. Then George translates it into code, and we both program a board and test for hours. Some days we'll go through countless versions of code and too many hundreds of clicks. Eventually we get it right... and that's the process I'd like to start all over again with this new UIB2. So bring it on.
So it turns out that most folks (or at least a large percentage) who are buying the Bflex are using it for bicycle lighting. So George and I agreed that a bicycle-only UI would be in order. In fact, we even have a secret weapon in the wings who is designing a new bicycle light around this board, but that's all top secret and hush-hush, so don't make me keep talking about that until the time is right. I'd hate to have to kill you. Edit: The word is out. It is the MinT, shown here: http://candlepowerforums.com/vb/showthread.php?t=172053
The advantage of a bicycle-only UI is that the menu won't need to be shared, and you won't have to stumble over menu options that make no sense on the bicycle. The menu will be easier to enter than in the current UIB that needed to use the same scheme as the other UI's. The menu also won't be needed as much. The three-UI Bflex is very flexible and fantastic for so many uses. But once you put a Bflex into a light housing, you aren't going to use the other UIs... so UIB2 will be born.
As I said initially, I've done this before. But I didn't do it here - I did it on the MountainBikeReviewForums, and got some great input from bikers who are also lighting guys (many of you are here, I see!). This time, I'm going to conduct the process on CPF to get input from light guys who are also bicyclists. Should be interesting. To see how it went before, go here
Please note that I'll be copying and pasting from the initial post to avoid cramping my fingers.
-----------------------
Now is your chance to be heard!
Everything that the uController on the bFlex can do is controlled by a single momentary button that can be mounted remotely, or stay on the board. There are two ways to enter info via that button. A Click and a Press. Two distinct actions, one that releases the button immediately after use, and the other that holds the button down for a moment until the effect is achieved. George and I have spent countless hours, and have refined after many months and even years how the UIF and UIP function with that single button. I've learned quite a bit in this process, and would also like some fresh ideas from folks who aren't as mired in the details as I can get.
In my next post, I will give the outline of what I'm thinking, and see how it floats. I will also have some questions to see what sort of direction this should go.
Everybody have your thinking caps on? Let's have your input! There are no promises that your ideas will be incorporated, but I can guarantee that it'll help shape the final product. I have plenty of ideas on how to incorporate most of this, and I know from experience much of what does and does not work in the real world. I also have experience actually using my first UIB - and what I do with this UI will be largely based on the improvements that I'd like to see in the first UIB.
Let me be very clear here that I do not do the coding or the circuit design. That's all George, and he stamps his name on the boards to prove it! Plus he's reading this, so I can't secretly take more than my share of credit. My job is to do all the *really* hard thinking. I try to figure out what the user will want, and how to make it the most practical to use. Then George translates it into code, and we both program a board and test for hours. Some days we'll go through countless versions of code and too many hundreds of clicks. Eventually we get it right... and that's the process I'd like to start all over again with this new UIB2. So bring it on.
Last edited: