I'm programming a robot! Which is cool... *but* even though I can program the robot in it's proprietary language, it requires that for a custom GUI, I need to write it in vb.net, which I'm new at.
The issue I have is not being any good in modern languages, *and* I have to press on. No opportunity to stop everything, take a couple of semisters, and then do it right. I have to press on, learn as I go.
I really need your advice on how to (re)organize my code. The short path to success has thus far been to just shove everything into the form code. While this works... the probelm is that as the code grows, it's getting ungainly. The robot has many different tasks that it can perform, and organizationally, I think I'd like to move dedicated task functionality off to code modules maybe. I know that this will start to break things if I just copy/paste... and maybe code modules aren't the right way to go... that's the problem with being a noob at this.
I really need your advice and experience...
The situation:
I have a form
The form has several "personalities" (arranged in a tab control) so that multiple jobs can be handled from a single GUI. Some controls are common across tabs (and are located outside of the tab control)
I have code for the form, in it's default public class. I have code for all of the unique robot control in the same place.
In that class, I have subroutines to handle form object events.
In that class, I have procedures that perform program logic of a more general nature (TCP/IP communications, file handling, etc).
What might you do in this situation to "clean things up"? What problems should I anticipate, and what solutions to them?
I'm willing to try anyhthing suggested, and as the inevitiable bumps in the road come... hopefully I can ask a follow-up question or two.
I've never set up any classes of my own... so I'm pretty much coding in line style with subs and functions. Stick to what you know, right?
Thanks for your kind help!
R
The issue I have is not being any good in modern languages, *and* I have to press on. No opportunity to stop everything, take a couple of semisters, and then do it right. I have to press on, learn as I go.
I really need your advice on how to (re)organize my code. The short path to success has thus far been to just shove everything into the form code. While this works... the probelm is that as the code grows, it's getting ungainly. The robot has many different tasks that it can perform, and organizationally, I think I'd like to move dedicated task functionality off to code modules maybe. I know that this will start to break things if I just copy/paste... and maybe code modules aren't the right way to go... that's the problem with being a noob at this.
I really need your advice and experience...
The situation:
I have a form
The form has several "personalities" (arranged in a tab control) so that multiple jobs can be handled from a single GUI. Some controls are common across tabs (and are located outside of the tab control)
I have code for the form, in it's default public class. I have code for all of the unique robot control in the same place.
In that class, I have subroutines to handle form object events.
In that class, I have procedures that perform program logic of a more general nature (TCP/IP communications, file handling, etc).
What might you do in this situation to "clean things up"? What problems should I anticipate, and what solutions to them?
I'm willing to try anyhthing suggested, and as the inevitiable bumps in the road come... hopefully I can ask a follow-up question or two.
I've never set up any classes of my own... so I'm pretty much coding in line style with subs and functions. Stick to what you know, right?
Thanks for your kind help!
R