Structure arcs

[peter88213]

Currently (v4.2.5), you can describe an arc by creating a "Todo" scene, assigning it to the corresponding arc. Then the number of normal scenes assigned to this arc is shown in the "Todo" scene's properties in the right pane. This is optional; you don't have to create a "Todo" scene in order to assign arcs to normal scenes.

It would be nice to break down arcs into several steps that can be connected with scenes. To realize this within the limitations of the .yw7 file format, the following is suggested:

1. The arc, consisting of a sequence of steps, is represented by a "Todo" type chapter with scenes representing the steps.
2. The steps can be assigned to normal scenes in the same way as characters, locations, and items. This is additionally to the arc assignments. If a step is assigned to a scene, the "parent" arc will be assigned too.
3. The steps are displayed in a tree column. Open point: How discriminate arcs, if multiple steps of different arcs are assigned to a scene? Coloring is no option here.
4. We can think of creating a special view, where the steps are displayed in the tree in a special way, e.g. as plot points, or as sections such as acts. This would be implemented as a a plugin.

[JPhB]

What I do is export the table as a spreadsheet, and replace relationship symbols with a short comment saying how this scene contributes to the arc (so this is more a scene-centric view than the arc-centric view exposed above). The saved spreadsheet is then updated as the project develops. At the end we can see the arcs unfolding (in columns), their respective chronology, and overlap points (important scenes).

It doesn't look easy to get that from the program itself, except perhaps as a plugin. I thought of putting those relationship comments in the Notes, but unless I'm mistaken they are not exported.

Coloring is no option here.

No option or one option?

[peter88213]

What I do is export the table as a spreadsheet, and replace relationship symbols with a short comment saying how this scene contributes to the arc (so this is more a scene-centric view than the arc-centric view exposed above).

In principle, it is not a bad idea to use an automatically generated table as a starting point for manual documentation. However, an automatic update is out of the question.

My work on novelyst aims to keep all relevant information in the yw7 project file and to be able to regenerate documents of all kinds at any time. The new concept for story arcs should actually be a help here, but yes, it is arc-oriented. It helps especially in the conception of an arc when the actual scene structure is not even available yet.

It would be conceivable, however, to generate a cross-reference to check whether all sub-elements of a story arc are assigned to scenes, and to which ones.

To document how the action of a scene fits into the whole, the three text fields of action/reaction would be suitable. Of course, there is no graphical overview for this. However, Novelyst's Scene list export lists these three fields in a spreadsheet that can be written back.
To obtain a HTML table with these three fields for each scene, you also might want to give yw-reporter a try.

Coloring is no option here.

No option or one option?

This is because color can only be used for unique assignments.

[peter88213]

If the connection between the arc subelements and the scenes is fixed, one could also have the titles of these subelements automatically entered into the retablex table, instead of a binary information.

[peter88213]

In the meantime I released novelyst v4.3.0, where the story arcs are no longer described with scenes but with chapters, so that the included scenes can be used for the steps. However, linking such steps with normal scenes is currently not yet possible.

A very generic example:

[peter88213]

Now the question is how to most comfortably create the references between the scenes and the arc-sub elements. A matrix for ticking off would probably be too extensive.

[peter88213]

Here a dropdown list could fit, which limits the selection to the subelements of the already assigned arcs.

[peter88213]

The concept of story arc subelements

A specification is now needed to choose the right implementation. To simplify the description, I shall name the story arc sub-elements "Points".

The concept is as follows:

Mapping to the yWriter model

• Each story arc is defined with a "todo" chapter. Missing defining chapters for already assigned story arcs are created automatically.
• Each point is defined with a "todo" scene belonging to the arc defining chapter.

Associating Scenes with arcs and points

• Each normal scene can be associated with any number of arcs.
• Each arc can be associated with any number of normal scenes.
• Any number of points can be asociated with each normal scene. If a point is assigned to a scene, the assignment of the corresponding story arc is linked to it at the same time.
• Each point can be associated to a maximum of one scene. Multiple assignments should not be possible.

This is how it looks in UML notation:

Change type

• If the scene type is changed from normal to other, its arc and point associations are lost.
• If the type of a point defining scene is changed from todo" to other, its arc and scene associations are lost.
• If the type of an arc defining chapter is changed from "todo" to other, all points are lost. If the arc is associated with any scene, a new "todo" Chapter for this arc is automatically generated, and the scene associations persist.

Delete/rename

• If the an arc defining chapter is deleted, all its points are moved to the "Trash" folder, and their scene associations are lost. If the arc is associated with any scene, a new "todo" Chapter for this arc is automatically generated, and the scene associations persist.
• To delete an arc defining chapter, first all its scene assignments must be removed.
• Arcs cannot be renamed. Instead, a new arc must be created and assigned to the scenes with novelyst_matrix. Then, the points of the old arc can be moved to the new arc, and the old arc can be unlinked and deleted as described above.

Move points

• If a point defining scene is moved to another chapter that isn't defining an arc, all its scene associations are lost.

[peter88213]

The state of the art on january 13, 2023

Now, the test version v4.4.2 is inofficially available. "Arc points" are implemented. For associating with points, scenes can be picked from the tree.
The "Arcs" help page now it gives a definition of arcs as used with novelyst.
The latest version of novelyst_retablex can enter the "arc points" into the generated table.

In abstract terms, arcs allow to arrange scenes in parallel structures that differ from the usual chapter structure. For this purpose, the possibility was created to link scenes with each other, depending on their type and their position in the project tree. However, because both can be changed by the user at any time, each corresponding user action triggers checking and correction routines that ensure compliance with the boundary conditions.

In order to test the stability of the program and to verify the practicability of the concept, the whole thing is now going into a test phase in which I want to work with the 4.4.x versions for a while and gain experience.

The development progress can be tracked here. The releases with the new features are not yet offered on the download page, but are part of a developer branch. There they are accessible to everyone in the Dist directory. However, I strongly advise against using these developer versions for serious work as the file format is subject to change, and files generated with the test versions might be incompatible with the final release.

As far as arcs and points are concerned, the program handling is still a bit primitive, at least not the way I want it to be in the end. However, I can only implement the desired operating concept when the implementation of the data structures is final.

[peter88213]

With version 4.4.4 this feature is implemented and released.
What's still missing:

• A more convenient way of assigning arcs to scenes. (see Drop-down list for Arcs #5)
• Hyperlinks between scenes and arcs/points/characters etc.
• A "Plot list" spreadsheet document export.
• Complete help.

[peter88213]

With version 4.5.0 there is an "Arcs" document export. It's not exactly the "Plot list" mentioned above, but an .odt document listing all arcs with descriptions and all children "points", each with hyperlinks to the associated scenes in the manuscript and scene description document.