In the very old days, when I was learning BASIC, the flowchart seemed a good way to lay out my plans for how the program was going to unfold.
Well, LiveCode and stacks are quite a different environment. What advice can anyone give a beginner on how best to lay out a plan for stacks, cards, buttons, handlers, etc.?
Thanks.
John
Any advice on planning the project?
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller
-
bqsbarbqGAnC5Z
- Posts: 77
- Joined: Thu Dec 08, 2011 12:19 pm
Re: Any advice on planning the project?
Hey John,
Not sure what kind of project you're working on but I've been working on a couple of games myself and the way I handled the planning was to work on my cards in reverse order. I wanted to work on the actual gameplay card first and then work my way backwards to score screens and then I went backward again into a main menu and then link them all together at the end. I would say it really depends on what kind of project you're taking on but this seemed to have worked for me. Hope this helped!
Not sure what kind of project you're working on but I've been working on a couple of games myself and the way I handled the planning was to work on my cards in reverse order. I wanted to work on the actual gameplay card first and then work my way backwards to score screens and then I went backward again into a main menu and then link them all together at the end. I would say it really depends on what kind of project you're taking on but this seemed to have worked for me. Hope this helped!
-
cascadesjohn
- Posts: 14
- Joined: Sat Feb 14, 2009 11:25 pm
Re: Any advice on planning the project?
Thanks for the input. I'll try the backwards approach. Programming in BASIC is basically a linear process, zipping off to a subroutine occasionally, and then back to the main road. LiveCode doesn't allow for linear thinking like that, it seems. It's more of setting causes and effects flying around from between and among objects. No BASIC-like flow, hence no flow chart aid. It's big fun, though.