I would like to make the case for a way to export a folder/collection into a new project.
I have one project that I keep all my backstory/research/snippets/unrelated scrivenings for a specific fiction milieu in. Occasionally, one of these snippets turns into a short story or novella or something. At that point, I want to export that folder and its children into a shiny new project, which will be maintained separately.
I do want it to be separate, for archival purposes.
Ideally, I would want a context-menu to simply supply a “Make new project from…” dialog box entry, so I could context-click (control-click, right mouse button, etc depending) on a folder, Make new project from… and hey presto.
The new project would offer to inherit all settings/configuration from the existing project or from the default settings. It would help if after doing so, the original folder was somehow archived (maybe simply change the folder icon, and insert an “Archived” tag on it, AND create a link in the Binder that opens/switches to the created Project. I tried dragging a .scriv project into the Spawner project and got teh “no media files” dialog. I’m looking for something like a softlink (ln -s …)
I think the above request has been made before, but I was unable to find the forum post where it was made, sorry. The workaround suggested manually creating a new project and dragging the folder over. This works, but it does a deep copy of the documents without bringing the settings/configuration over, and doesn’t do anything to the source to let me/us know that I/a collaborator had exported it manually to a new project. It’s a bit of an error-prone process.
to which I add a . Sorry, I try not to delete anything not since a rogue rm -rf (as root) on / on a computer at work in 1997. Still have the scars from that one.
I know there are current steps that allow me to get from A-Z. I want a single step process that implements those steps for me, so I don’t have to have a process, plan and checklist to make sure I didn’t skip something. … or a way to automate it using perl and such.
Are the Binder names stored in a machine readable fashion someplace? Could I simply walk the .scriv file tree with a perl script, copying files as I go, but skipping anything from the Binder not flagged with a Promote keyword or tag?
You would need to parse the .scrivx XML file to find the RTF files associated with each binder item. Copying a project and deleting what you don’t need is perfectly safe, given that it won’t touch your original files. There are no plans to add anything like a “Create new project from these documents” feature, I’m afraid, so I was just trying to give you a way of doing it.
Is there an XSD for the XML file? or do you ad-hoc it?
I can work either way, but having an XSD tends to make changes more slow in coming. Not asking to see the XSD, just asking for the knowledge that one exists or not.
The hardest thing to learn to do is how to say no. I accept your comments as Word.
Still I’ll look at what the XML file contains, and go from there.
I’m talking about hacking meta-information underneath, which is done at my own risk, and fully with the understanding that I am, in no way, protected from any future L&L changes to the underlying code structure, APIs or behavior, and
I’m not entitled to a voice in the matter and
If something breaks inside Scrivener, I’ll take steps to prevent you from hearing about it until after I can prove it had nothing to do with my fumbling about blindly under the skirts.
. Sorry, I try not to delete 
and