i probably could do a better job of making it easier to read, its just usually my process includes starting at line one, figuring out how to enter what i'm trying to do, make the body of the script with what i want my subs to do in mind beforehand, then filling in subs to fit what i just wrote. Usually the scripts i do are done in one session of writing, with some debug afterwards.
For the most part i throw my scripts out when they stop working and start from scratch unless it was a small fix, implementing some of the more recent things i have learned or organize it better as a 2nd go around, being more familar with what it needs to do. and seeing a more efficient way to do it.
for ex:
with
http://www.easyuo.com/forum/viewtopic.php?p=397879#397879my 1st look into pulling things out of strings was probably a couple weeks before that. And my 1st crack at it, had to write out the whole thing long hand before could grasp it totally, and condense it into subs. Probably next time i need to do it, will try to turn the 5 different resists subs into 1 sub with more %1 variables to save more space.
Its just kinda been my process for learning, and don't have any coding background before easyuo, so its kinda learn as i go.
in short, this has been my general approach to organization, trying to shorten anything that i see as repeatable or doesn't happen every time into subs to either save space or not force the program to slow down with looking over unnecessary lines
;startup:
;things i only gotta do once before the scrypt kicks in
;
;item change:
;if the main loop needs to perform a diffrent function
;
;mainloop:
;what the sctypt does
;goto mainloop
;
;Sub a
;
;sub b
;
;sub c