Alan - if you want to write documentation, we can arrange something. The trouble is going to be how quickly the documentation changes due to new features. That's why we have self-documenting software. So you click on things, or hover question marks for the answer.

Mostly i believe what people are looking for are examples - and that falls under content. Historically, we can document the world and people will still ask "how do i do this?"

I am going to disagree somewhat.... I learn more when I tinker as opposed reading boring manuals... I really just want the "Coles" note version... I learn much more from doing not reading... I do agree with having examples, however....

The solution to documentation with examples is to cross-link objects and controls so they can be referenced in the use case. For example, click on a control manual page and scroll to the bottom. Any use-cases from tutorials are linked to that control.

Also, something that is often over looked in EZ-Script syntax is the Examples folder that installs with ARC. As far as documentation, i'm quite confident ez-robot has a lot more than anyone is used to. And, it's all very easily accessible online and in the software. It's pretty hard to get lost - specifically when everything is cross referenced.

You could argue that a few attributes are missing, such as "what controls use multi boards", but a similar argument of "what controls are hazardous to your health" can be disputed - considering the likely hood of either question being asked is in a low decimal place below 1%.

Continuing forward with content examples is by far the most productive use of documentation with technology.

When a question has been answered on the forum, a polite message box displays a suggestion to create a tutorial on that topic. It's one way to document your own findings for future reference, with the added feature of giving others the ability to use the resource. All user tutorials are linked to controls for cross-reference.

If it would be useful, I can have James organize another user tutorial marathon in exchange for ez-credit?

Quote:

Alan - if you want to write documentation, we can arrange something. The trouble is going to be how quickly the documentation changes due to new features Smile.

It isn't like I really have the time either, but after I do the multi-EZ-B in one project tutorial I signed up for, I may take a stab at punching up some of documentation for some features that I think the documentation is a little light on (interestingly enough, it is a lot of the older features that need the most help).

Alan

@DJ- I have been an Instrument and Electrical Technician for 30 years now and my workplace life revolves around having good solid up-to-date documentation. College, (1980's), was focused on digital electronics. Logic gates and passive support components. I will admit it gets tedious sometimes pouring over manuals and schematics to find information on something I am troubleshooting or building. However, to me, this is an essential thing. When starting a project, I plan it out to the best of my ability so that I wont get deep into it only to find out that I missed something and now I will have to spend (waste) a lot of time tearing things down and reassembling all over again. Not to say that it does not happen but, time is precious to me. Not getting any younger .

Here is the space shuttle.....don't bother with reading the manual....just push buttons and try things till ya figure it out.... stress

Nope...can't do it....gotta have me books....

Robots and electronics are my true passion and EZ-Robot has opened up a whole new world for me. It is an exciting time to be alive! And thanks to DJ and his team, robotics has been taken to a new level of amazing potential. Keep up the good work.

Thanks Steve for looking at this....