IF I would write a book about coding a 1K ZX81.....

[dr beep]

... what should I add for you in the book?

How many pages should the book be?

Who could redirect my writing since english is not my native language?

What style of writing would you like? For instance I could write it as telling my story or just like a
manual explain how to get most out of 1K

What shoukd be in the book?
-routines, examples, hires, lowres, ideas

What have I forgotten what you want to know?

[Lardo Boffin]

That would be an awesome book!

Initial thoughts:-

The number of pages should be driven by the content you wish to include, unless you are planning to physically print it? In which case I guess there will be sensible limits due to cost.

I’m happy to proof read stuff. I don’t have huge amounts of free time (too busy refurbishing zeddies) but should be ok most of time.

Writing style preference will vary from person to person. I personally liked the style of the book Assembly Lines (for the Apple II, by Roger Wagner).

I would personally like to see one start to finish ‘story’ of the development of a 1K game included. The whole book could be based around this assuming you could think of an example that would include all required sections.

Are you going to assume the reader knows how to code in Z80 machine code (to some extent) and just wants to get the best of a 1K machine or assume no knowledge of Z80?

[dr beep]

That would be an awesome book!

Initial thoughts:-

The number of pages should be driven by the content you wish to include, unless you are planning to physically print it? In which case I guess there will be sensible limits due to cost.

Both is possible, online PDF or physical.

I would personally like to see one start to finish ‘story’ of the development of a 1K game included. The whole book could be based around this assuming you could think of an example that would include all required sections.

I am planning such, but it will be a small game with score and hiscore

Are you going to assume the reader knows how to code in Z80 machine code (to some extent) and just wants to get the best of a 1K machine or assume no knowledge of Z80?

If you want to learn Z80 we have other books. This is to get the most out of 1K, which by the way, will mean you have to code Z80. I am explainingwhy BASIC is insufficient.

[siggi]

What style of writing would you like? For instance I could write it as telling my story or just like a
manual explain how to get most out of 1K

Maybe the structure could be like the ZX81 BASIC Manual? It is well done to learn BASIC.
And to learn C, the same structure was used:
https://forum.tlienhard.com/phpBB3/viewforum.php?f=8

Siggi

[1024MAK]

In the past, I have checked/proof read a manual/guide written by a contributor in the Spectrum community. The author was also not a native English speaker/writer.

Although their writing was excellent, the English flowed nicely, correct grammar etc. It became clear that there are different, shall we say, conventions and styles used in different countries and hence their languages. For example, in the way that an item is referred to, that author used possessive pronouns rather a lot. Which if telling a story is absolutely fine, but it did not feel appropriate in what was a technical manual and guide (I did communicate with the author and we agreed to some changes that they were happy with).

In English, when you read technical manuals or guides, normally you will find more generic words used in preference to possessive pronouns.

I’m not telling you about this to have a go at (criticise) anyone. And I absolutely do not want to put anyone off. But I thought it was worthwhile pointing out the differences between the way that we use language.

dr beep, from what I have seen, your written English is very good. If you want me to also take a look at any draft versions after Lardo, or if Lardo is unavailable, I’m happy to do so. Although, I also have limited time unfortunately.

I think the community here would really appreciate a book on this subject. I do agree though that it should not be another introduction to Z80 assembly language/machine code. Trying to do that would be too much of a distraction from it’s purpose.

Mark

[dr beep]

So dar I had this already to add in the book, but now is your chance to add other parts too


BASIC vs Machinecode : size

Memorylayout

Compiling model

Compressed screen further compressed

Bytesaving in machinecode

Coding in machinecode
- game setup
- several routines

Randomness

REM-line why not

How to code some artifical intelligence

The ROM, what to use, what not to use

Hidden data on the screen

Advanced programcompression

1K hires

[1024MAK]

Sounds good so far

I presume you are including information relating to which system variables can be overwritten and used for your own program, and when?

Also use of a smaller screen display?

Mark

[dr beep]

I presume you are including information relating to which system variables can be overwritten and used for your own program, and when?

Yes

Also use of a smaller screen display?

Smaller as in less than 25 bytes with a minimum of 1 byte?
Yes!

[dr beep]

Been wrting down a lot already.

At this moment I have filled 33 pages B5 and I am starting at the
1K hires now.

So far:

Code: Select all

How to fully use the 1K ZX81

Introduction
BASIC vs machinecode
The memory layout of a 1K ZX81
Start coding outside the ZX81
Compressed screen 
Coding in machinecode
THE ROM
REM-line
Game layout
Initialisation
Reading keys
Delayroutine
Gamecontrols
Scoring
Highscore
Simplified calculations
Randomness
Compressed screen at loading
Create a screen with your CLS-routine
Code over systemvariables
SP-area
Routines on screen
Hidden data on the screen 
Simple routines
Codingtips
Joystickcontrols
Intruptroutine
1K hires

[Baggey]

I know this is a while ago but did you ever finish your Book!?

Would be very interested to Read is your Language German or French?

Kind Regards Baggey