Quote:

I'm a noob at KiX (all programming really) but a veteran at being disorganized. I start KiX projects that I can hardly read the next day. Does anyone have tips or links to help me organize a project beforehand and stay organized during?

I know about properly labeling variables and functions, but does anyone actually map out their program beforehand, a script for their script if you will? I know this is probably Computer Science 101 but I was an English major!



i once had a 12th grade public school teacher make us write out on pen and paper and get it approved by her the entire program before we even got a change to type it in to the computer (BASIC on a Apple IIe)

the really sad thing about that class... i think i knew more than the teacher... and to top it all off... the class that i HAD to take in the 12th grade, was the same class that i look as a intro to computer science in the 6th grade while in a different school system.... BASIC on a apple IIe......


As for keeping orginized.... use white space TAB, space, line returns to organize your code. Use comments.... Don't try to GOLF your code right away... take your time... spread out get to know the logic behind the process you are trying to do before you look at condensing it.

Also as of late...i find my self programming more and more UDF's that call other UDF's.... this lets me compartmentalize my code, break it down to small chucks that are easier to handle. This type of behavior is really apparent in KixForms scripts!