I know it seems like an odd question to ask, but how can a user of GCB help with the project? My programming skills arent really the best, and if what I use works, then I just use it. Im more of a hardware person anyway. Is the simple fact that I use the software "good enough" to help?
I have some code that Ive modified from the examples, but its trival at best. For example, I got the Rotary Encoder demo working, but instead of using a LCD, I spit out stuff via UART. I thought of remaking the LPC dev board since you cannot find them anywhere and they seem useful, even if they just have 1 Pot and 4 LEDs. Maybe a remake that includes a GLCD would be nice. Just throwing some ideas out there. I have my own "dev" boards, which are nothing more than a 28 PIN dip socket and a connector for ICSP that plug directly into a bread board.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have noticed that the help files leave something to be desired, or are quite lacking in info that I find myself going to the demo's to look for. Even something simple like how to set up I/O ports leave something to be desired imho. I find my self going back and forth between old projects and new ones saying to myself "Wait, how do I do that again?"
How would I go about editing the help file? Should I just compile the notes I have and submit them? They aren't formal at all, just comments in my programs.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Editing is simple.
All the file are in GitHub. Create an GitHub account and we grant you edit permissions.
The files are plain text. The formatting is very easy to learn. The formatting is strict - which means the format is the format and there is no option but that format. The format is called ASCIIDOCs - this is simplicity. https://github.com/Anobium/Great-Cow-BASIC-Help/blob/master/readme.adoc
Each page of the Help is one file. There is a mega tool that then processes and creates all the format.
Track.
1. People send new Help. I integrate. Easy to do.
2. People clone GITHUB, make changes and submit for review.
3. Some of the team have editor access.
In all cases. When it re-sync's here. I see all the changes in the change log.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I know it seems like an odd question to ask, but how can a user of GCB help with the project? My programming skills arent really the best, and if what I use works, then I just use it. Im more of a hardware person anyway. Is the simple fact that I use the software "good enough" to help?
I have some code that Ive modified from the examples, but its trival at best. For example, I got the Rotary Encoder demo working, but instead of using a LCD, I spit out stuff via UART. I thought of remaking the LPC dev board since you cannot find them anywhere and they seem useful, even if they just have 1 Pot and 4 LEDs. Maybe a remake that includes a GLCD would be nice. Just throwing some ideas out there. I have my own "dev" boards, which are nothing more than a 28 PIN dip socket and a connector for ICSP that plug directly into a bread board.
Thank you for asking.
The Help needs an uplift. You dont have to be an expert at it all, as there are many that can help, but, an edit of the Help would help everyone.
Would that be of interest?
I have noticed that the help files leave something to be desired, or are quite lacking in info that I find myself going to the demo's to look for. Even something simple like how to set up I/O ports leave something to be desired imho. I find my self going back and forth between old projects and new ones saying to myself "Wait, how do I do that again?"
How would I go about editing the help file? Should I just compile the notes I have and submit them? They aren't formal at all, just comments in my programs.
Editing is simple.
All the file are in GitHub. Create an GitHub account and we grant you edit permissions.
The files are plain text. The formatting is very easy to learn. The formatting is strict - which means the format is the format and there is no option but that format. The format is called ASCIIDOCs - this is simplicity. https://github.com/Anobium/Great-Cow-BASIC-Help/blob/master/readme.adoc
Each page of the Help is one file. There is a mega tool that then processes and creates all the format.
Take a look at https://github.com/Anobium/Great-Cow-BASIC-Help/blob/master/source/lcd_variants.adoc this is a newer page. Then look at this https://raw.githubusercontent.com/Anobium/Great-Cow-BASIC-Help/master/source/lcd_variants.adoc it is the same page but in the format that we edit in. As you can see the format is text, is has the format.
I would be very, very willing to do a training session. This would be the best way to start. What time zone are you on?
I'll give it a shot when I have time and contact you with any questions. I am on EST (CT,USA).
How do you keep track of who contributes what?
Excellent.
Track.
1. People send new Help. I integrate. Easy to do.
2. People clone GITHUB, make changes and submit for review.
3. Some of the team have editor access.
In all cases. When it re-sync's here. I see all the changes in the change log.