No way to write documentation

For a study I'm running I needed some documentation to support a subject programming in arduino for the first time. This is proving a tuff work flow as the stuff that needs to be documented is written, then fitted into the java source code, then tested, then fixed, then exported as app, then used, problems spotted and we are back to the begging.

It's interesting how some of the decisions are made here. First why java, is interactivity really that big a deal? cut an paste from a pdf might be fine. The java bit seems to be a recurring design decision [for the wrong reasons] java is the tool I have to hand, so for minimum work will probably do the job. A web technology may do it better but this is balance between learning something new and getting the job done.

The difference between a button click and an alternative route to copy and past is more subtle bit of interaction.

I will be working with school pupils, most well able to cut and paste a text fragment form an un-editable document. The difference is;
read, click, use(paste) vs
read, click before drag over, do I need the semicolon, realise mouse button. copy (younger kids tend to use menus), use(paste).

In practice this can make a non trivial difference in the time to run a session. Putting the user in a position where is it is hard to make mistakes (copy incorrect code) is much better than catching the errors. So in this case interactivity makes a difference.