FlowCharts

[Amiga Forever]

This is old Flowchart when I used make Space Invaders type game

There was one mistake in that flowchart is if player was facing the boss level then if he/she lose life then it should go back actions between end of level boss(so that he/she can continue fighting the boss) and if player beat the boss and then go on next level

It would be Perfect Flowchart

 

[AmiNeo]

Nice,

I need to get my head in that mindset when programming I think.

 

[Wolfy]

I need to draw out a flowchart for a copper list...

 

[HonestFlames]

My computer studies teacher spent somewhere in the region of 5 1-hour long lessons trying to instill the essential skill of flowchartery into me.

I've never seen the point. If a problem is so complex that your only chance of understanding it is to write it out as a flowchart, you need to rethink the whole concept.

 

[AmiNeo]

It's pretty much the basics of programming logic...


If this, then do this... else do this.

 

[tbtorro]

My computer studies teacher spent somewhere in the region of 5 1-hour long lessons trying to instill the essential skill of flowchartery into me.

I've never seen the point. If a problem is so complex that your only chance of understanding it is to write it out as a flowchart, you need to rethink the whole concept.

The point of a flowchart (or pseudo code, or state diagram or similar) is not so that you can understand your problem but rather that you have a structured way of describing the logic of your program.

Once the logic is complete (and correct) translating it into code is rather straight forward, and debugging is easier, especially once the code gets more complex.

 

[thecellartroll]

At uni we used to use a program that you could draw a flowchart and it would turn it into the framework for a Java program, with all the variables etc that needed to be passed in and out.

Or you could write a Java program and it would turn that into a flowchart. I forget what it was called though

 

[Zetr0]

in three words

Jackson Structured Programming...

while there are many meta languages that describe logic / process, JSP is all you need to know...

I have a couple of books about JSP and prototyping, including Rapid Prototyping Models for systems... err. okay I digress....

Flow Charts are great!

JSP is better =D

 

[HonestFlames]

My computer studies teacher spent somewhere in the region of 5 1-hour long lessons trying to instill the essential skill of flowchartery into me.

I've never seen the point. If a problem is so complex that your only chance of understanding it is to write it out as a flowchart, you need to rethink the whole concept.

The point of a flowchart (or pseudo code, or state diagram or similar) is not so that you can understand your problem but rather that you have a structured way of describing the logic of your program.

Once the logic is complete (and correct) translating it into code is rather straight forward, and debugging is easier, especially once the code gets more complex.

Maybe it's just me then. I may have a slight advantage with a brain wired up in such a way that I score as borderline Asperger's.

Similar thing used to happen in maths classes. "show your working" I kept being told. Never understood why. The answer is the answer. Logic is logic.

 

[Mr.BomberMillzy]

The flowchart should be a 'simplified' version of the code really.
The difficulty arises because the coding language has its nuances which do not dictate to pure logic, so this then causes differences which may need changing in the flow diagram to accommodate.
I find designing the diagrams, then coding, changing the code to fit or 'work', then re-editing the diagrams to fit with the flow of the code is the best option (sort of like design to implementation feedback).

 

[Zetr0]

I refer the most honerable (car recently MOT'd) Mr BomberMillzy to post number 8

For those that have not used or heard this method of prototyping, IMHO its the best tool about!

here is some more information on JSP, and here is a PDF that teaches you how to use the symbology and teminology - If you are going to learn how to program, no matter the language you choose, you should pickup JSP - its easy and methodical - well worth the effort 10 fold IMHO!

 

[Merlin]

Process flow diagrams are very similar; for those that are maybe struggling with the concept, try having a go at drawing the process flow for making a cup of tea and see where that takes you in terms of on/off, yes/no and other logic.

It might be a good exercise for this thread.

 

[Mr.BomberMillzy]

I refer the most honerable (car recently MOT'd) Mr BomberMillzy to post number 8

For those that have not used or heard this method of prototyping, IMHO its the best tool about!

here is some more information on JSP, and here is a PDF that teaches you how to use the symbology and teminology - If you are going to learn how to program, no matter the language you choose, you should pickup JSP - its easy and methodical - well worth the effort 10 fold IMHO!

Thanks Zetr0, I will have to check this out (possibly along with UML2 which has always been rumored as a big deal) although its probably a bit late for my current project, anything that can improve the ease of logic design is very welcome!