Books

[kelli217]

I wouldn't be as worried about errors so much as breaking changes in later Kernal/HW revisions, like the vector pull, the Kernal's layout of video memory usage, and the keyboard keycode change. Although, I haven't seen any such changes for a while now (only non-breaking stuff, like new commands and extensions), so maybe this isn't a concern anymore.

Effort is being made to prevent any further changes that would break existing code. Behaviors are being corrected, and in some cases added, but not changed if it can at all be avoided.

[DragWx]

Thanks, that's good to know.

[mortarm]

I wouldn't be as worried about errors so much as breaking changes in later Kernal/HW revisions,

Certainly, that can happen, especially with community-driven projects like this, however, these require simple updates which can be added to the existing docs. Not so easy for grammatical, spelling and other such errors, which would need to be hunted down and corrected. Also, such errors can impact the new user experience; if a program listing is wrong or an algorithm is off, the user may become frustrated and give up or complain on social media, which wouldn't be good for the author(s).

There's no excuse for sloppy writing.

[Jestin]

Thanks guys. I'll be looking out for those books especially the one that is written like the old Commodore VIC-20 and 64 user's guides.
mlk

Just keeping everyone up to date, publicly downloadable releases of the user guide are being published to GitHub on each commit: https://github.com/X16Community/x16-use ... sers_Guide

Lots of work yet to do, but there's progress being made.

[Jestin]

Jestin is working on something more like the User's Guides that came with the various Commodore computers back in the day. It just isn't quite ready yet.

Hey, me too! Nothing like some healthy competition, eh?

Do you have a link to your manual? I'm developing mine in public view here: https://github.com/X16Community/x16-user-guide

I wouldn't think of what I'm doing as competition, however. I don't want to write a manual; I want to have a manual. Writing one is just the means to an end. I'd love to see what you've come up with, and maybe even talk about merging them, if that makes sense. If not, it'll just be more choice for the community!

[mortarm]

I'd love to see what you've come up with, and maybe even talk about merging them, if that makes sense. If not, it'll just be more choice for the community!

I'm waiting until my board arrives so I can write from a first-hand experience.