I'm probably not done. I'm going to sit on this design for a day or two to see how it feels. I had a suggestion about adding a right triangle showing people base, slope, rise, angle, etc. I'm kind of torn on that part.
In essence, this is probably about 90% done as far as the User Interface goes. I like it, I think. I'm hoping to be able to pass the keyboard strokes directly into the program, rather than have someone point and click. If I can get that done, the flow will be ten times better. I'm excited about the math involved and the fact that this will actually be functional.
There are two things I'm struggling with right now. The first is the programming language. I've mentioned this before, I believe, but the programs my group works with are all programmed in VB.net. So, that's the language I'm learning right now. The problem, however, is that the system architect here at work is telling everyone that any new programs should be written in C#. I'm concerned I could be wasting my time on some of this. Not sure.
The second issue, I'm not as conflicted on, but still debating. The architect also mentioned that any apps, if possible, should be on a web platform. I'm not sure I'd like this type of program on the web. It makes sense that it would run faster and be more convenient as a quick-launch icon ready for a detailer.
To be utterly honest, I'm actually really excited about this program. This is one I see people actually using, and possibly even having a demand on, in my industry. Nearly every detailer has one of these calculators and relies on it heavily. If I could come up with a program that can replace or even supplement it, it would be huge.
Other than that, I have no real concerns about the design. I'm open to any feedback anyone has on this. Ideas, thoughts, suggestions, anything. If it's too complicated, then I'm probably going to have to pass for now, but keep it on the shelf for another project as I go forward.
Comments
Post a Comment