You can help. Add your good work to the demonstration code.
I am sure you have some great demonstration code to share!
If you have something we have not covered then spend a few moments updating your code using the template. Download here.
A few rules. I have found that we need a standard format.
1. Keep the code simple.
2. Test your code, compile it.
3. Test your code, view the code in your editor and Great Cow Graphical Basic (see below.. you should not save in Great Cow Graphical Basic!)
4. Test your code for the 16f886, if you can – this is the baseline Microchip device we want to publish in. If not, publish as is and we can convert/test.
5. Test your code for the mega328p, if you can – this is the baseline Atmel device we want to publish in. If not, publish as is and we can convert/test.
6. The filename needs to be capitalised and representative of the functionality and it needs to specific the chip type. See the example demo code.
7. The filename needs in the top of the demo file.
8. Use the file ‘Sample Header.gcb’ as a starting point.
9. The Author should be ‘you’ plus others. Recognise the others as appropriate.
10. Comment your code – see how we have done it for inspiration.
11. All comments MUST be on the prior line to GCB instruction – not as an extension of the same line as the command. GCGB will moan otherwise.
12. All user comments must not be too long. And, write the user comments as if they were a newbee. Multiple comment lines is good. Long lines bad. GCGB moans.
13. All user comments MUST be preceded by ‘
14. All user comments started with a ‘ should not have a space following the ‘. ‘This is a user comment – this is the correct method.
15. All functions, sub and calls are called ‘methods’. This makes it easier to state things like…. “All hardware is configured within the supporting LCD methods.”
16. All file comments, legal stuff, dates etc MUST be preceded by ; (a semi-colon)
17. The 16F886 is the default chip for Microchip. At 16mhz.
18. The 328p is the default chip for ATMEL. At 16mhz.
19. The date of the demo file should be the current date.
20. The version should be representative of the release level.
21. If you inspect a demo file in GCGB - do not save!! You will lose all the non-user comments.
22. Keep all code indented by ONE space.
Thank you.
Last edit: Anobium 2015-02-05
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You can help. Add your good work to the demonstration code.
I am sure you have some great demonstration code to share!
If you have something we have not covered then spend a few moments updating your code using the template. Download here.
A few rules. I have found that we need a standard format.
1. Keep the code simple.
2. Test your code, compile it.
3. Test your code, view the code in your editor and Great Cow Graphical Basic (see below.. you should not save in Great Cow Graphical Basic!)
4. Test your code for the 16f886, if you can – this is the baseline Microchip device we want to publish in. If not, publish as is and we can convert/test.
5. Test your code for the mega328p, if you can – this is the baseline Atmel device we want to publish in. If not, publish as is and we can convert/test.
6. The filename needs to be capitalised and representative of the functionality and it needs to specific the chip type. See the example demo code.
7. The filename needs in the top of the demo file.
8. Use the file ‘Sample Header.gcb’ as a starting point.
9. The Author should be ‘you’ plus others. Recognise the others as appropriate.
10. Comment your code – see how we have done it for inspiration.
11. All comments MUST be on the prior line to GCB instruction – not as an extension of the same line as the command. GCGB will moan otherwise.
12. All user comments must not be too long. And, write the user comments as if they were a newbee. Multiple comment lines is good. Long lines bad. GCGB moans.
13. All user comments MUST be preceded by ‘
14. All user comments started with a ‘ should not have a space following the ‘. ‘This is a user comment – this is the correct method.
15. All functions, sub and calls are called ‘methods’. This makes it easier to state things like…. “All hardware is configured within the supporting LCD methods.”
16. All file comments, legal stuff, dates etc MUST be preceded by ; (a semi-colon)
17. The 16F886 is the default chip for Microchip. At 16mhz.
18. The 328p is the default chip for ATMEL. At 16mhz.
19. The date of the demo file should be the current date.
20. The version should be representative of the release level.
21. If you inspect a demo file in GCGB - do not save!! You will lose all the non-user comments.
22. Keep all code indented by ONE space.
Thank you.
Last edit: Anobium 2015-02-05