Document Namespaces

[dunx]

There is only one namespace for all documents.

If I create a document called "Chapter 1" in the Drafts folder, I cannot create another document with the same name in Research.

I first noticed this when I was creating a multi-part structure. I wanted to have "Part 1: chapters 1-8" then "Part 2" chapters 1-8" but I cannot name a document in a subfolder with an already used name.

[KB]

This isn't a bug; it's intended behaviour. The reason for this is the way Scrivener stores files within the project directory, and it's normal behaviour for similar apps. The directories aren't real directories on disk; they are virtual directories. Inside the .scriv file, you can find all your documents as RTFD (an upcoming feature will allow you to export a project as as separate files with the virtual files turned into real directories). The binder really expects you to give chapters meaningful titles, so that you know what they are and can move them around easily.

[dunx]

Ah, fair enough. I was thinking too linearly it seems.

[amberv]

Are there any plans for automatic numbering and prefixing based on Draft order. That way,

• The Beginning
  
• The Scourge
  
• The End
  

becomes,

on Draft export, or whatever other prefix other than "Chapter " is desired, or none at all?

Additionally, any long-term plans to export to a structural format, such as LaTeX, for a more complex typesetting solution?

[KB]

Prefixing/autonumbering is something I have thought about, but I can't think of a really good way to implement it. For a start, you don't want to force documents to have numbers, which means they shouldn't get updated automatically. And as you can have an unlimited number of levels, it would be hard to specify how prefixes apply to different levels. The most sensible implementation I can think of would be a ctrl-click opton to "prefix all items on this level in this folder with such-and-such", with an auto-number option. Which would have to spew an error if any of the doc names clashed with any other. Gets complicated, see?

As for LaTeX... No plans at the moment. And certainly none before 1.0.