Detailer Calculator GUI

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

Bigger Picture

I've learned a big part of development since I've been a part of this team. We have meetings. Some seem long-winded, some seem unnecessary at times, but I've gotten something from all of them in every case. There's a lot of communication involved in this role. I focused on a lot of technical, but there are many soft skills involved to make it successful. Below is a summary of some of the things I've learned in just a few quick months. 1. Know When You Don't Know There's nothing wrong with not knowing. There are developers on this team that I've heard everyday say, "I"m not sure how to do that, I need to ask 'so and so'." I feel I'm part of a great team, and maybe this type of honesty isn't the norm. In any case, it's refreshing to see that type of behavior. It's also encouraging to see someone who has been here for many years not afraid to admit when he/she doesn't know something. No one is going to kn...

New Pet Project

Okay, I've got my next great idea for my pet project. It's a little more complicated, but not terribly. My biggest complaint I had when I transferred from the Detailing Department to the Customer Service department was the loss of my trusty HP48G calculator. This thing was awesome! You calculated feet and inch calculations with formulas. The format was feet.inches and sixteenths. For instance, 14.0608 = 14'-6 1/2". The formulas removed parts of the inputted number and converted them from a foot to a number to add and subtract, and then reconverted the number to a foot answer to display. I and a colleague created several excel sheets that essentially did the same thing, but it just wasn't convenient and didn't flow very well. So, I'm going to create a program that looks close to this calculator. In addition to the addition, subtraction, multiplication, and division of feet-inch numbers, there were formulas that calculated roof slopes, weights, and...

Pet Project Progress

Well, I've started my pet project, and I've got a GUI laid out. It's a little slow going, but it should work well in the end, I think. I'm sure there's going to be lots of feedback and many different ways I could do things. Right now, however, I'm limited to what I am learning in the text. As promised, here's the screenshot of my first program. Help? I'm trying not to ask too many people how to write any of the code yet for a couple of reasons. First, I haven't learned any code yet, and I likely won't understand a word of what's being told to me. Second, I'm afraid that what I'll be told I'll understand at that moment, but since I didn't have to work for it, it won't get burned into my memory like the knowledge I have to seek out. Those long hours searching usually scar you to the point you never want to forget those lessons again. Function Since I don't have too much to show, I'll just explain what th...

Path 2 Developer

Search This Blog