[eugenR]

Hi
Rob Röterdink has published here a pdf for TimetableChanges at the end in the first post:
http://www.elvastowe...ode-signalling/
Perhaps somebody can also entered this Informations in the Manual in the Chapter 11 ?

Regards
EugenR

[cjakeman]

eugenR, on 08 August 2020 - 08:09 AM, said:

Rob Röterdink has published here a pdf for TimetableChanges at the end in the first post:
http://www.elvastowe...ode-signalling/
Perhaps somebody can also entered this Informations in the Manual in the Chapter 11 ?

Thanks for linking back to that document, Eugen.

To copy Rob's text from a PDF into the manual involves using the RST markup, which is designed to be quick and simple. Then the document is submitted to GitHub. I would be happy to help with the technology.

Is anyone willing to take this task on?

[roeter]

cjakeman, on 09 August 2020 - 12:30 AM, said:

Thanks for linking back to that document, Eugen.

To copy Rob's text from a PDF into the manual involves using the RST markup, which is designed to be quick and simple. Then the document is submitted to GitHub. I would be happy to help with the technology.

Is anyone willing to take this task on?

Latest version for timetable commands is here.
There is a MS-word version available if that helps. If anyone is interested, just let me know.

Regards,
Rob Roeterdink

[rickloader]

Hi Chris, Rob, I would like to try and help with timetables and the manual.
Rick

[Weter]

Waiting for new functional's descriptions, I've found it very difficult to read 243 pages over and over, in order to search new text.
Why not to place timestamps, showing each paragraph's update time?
Then each one can see clearly, where's the new information, and where's no, so not to re-read old paragraphs again.

[cjakeman]

rickloader, on 09 August 2020 - 08:48 AM, said:

Hi Chris, Rob, I would like to try and help with timetables and the manual.
Rick

Hi Rick,

Thanks for the offer - great to have volunteers stepping forward.

[cjakeman]

Rob Roeterdink's Signalling Functions have now been added to the Unstable version of the manual and will, no doubt, show up in the Testing version is a week or so.

R H Steele, on 17 July 2020 - 12:15 PM, said:

A compendium of all the "ORTS" parameters organized into logical areas...wag section; eng section; brakes, route, sounds, etc. A usage manual with correct examples and perhaps a set of templates incorporating the "ORTS" parameters.

This is the next request on this thread.

As well as a complete list logically organised, also a usage manual and also a set of templates - sounds like a substantial document all on its own!

Anyone able to help with this?

[cjakeman]

Weter, on 10 August 2020 - 01:10 PM, said:

Why not to place timestamps, showing each paragraph's update time?

I've never seen datestamped paragraphs in use anywhere. Seems an interesting idea, but is it perhaps overkill?

Instead, I've seen documents with change-bars in the margin indicating changed material. We could perhaps compare the current document with the one from the previous stable release (i.e. v1.3.1)

Any idea how we could add change-bars automatically?

[cjakeman]

R H Steele, on 17 July 2020 - 12:15 PM, said:

A compendium of all the "ORTS" parameters organized into logical areas...wag section; eng section; brakes, route, sounds, etc.

I have a copy of a spreadsheet which was the result of extensive analysis:



The author has clearly thought a lot about parameters, so we ought to have a chat before I go ahead and add "a compendium of all the parameters" into the manual.


Can anyone tell me who contributed it?

[Weter]

cjakeman said:

I've never seen datestamped paragraphs in use anywhere.
...
Any idea how we could add change-bars automatically?

I have thought better and remembered:
Our technical documentation has, at the very last pages of document, the "list of changes registered" table, with "paragraphs ##","date" and "author/reviewer's signature" columns.