Comments (8)
Let me know what you think of this Gist
from mountain.
+1 for optional closing tags.
from mountain.
In the example in this ticket's description, you have # ACT I = Meet the **Hero**.
automatically written to screenplay-ref1.fountain
. These lines precede a split
directive.
However, in the gist, the entire EXT. CAFE - MORNING
is not written to an auto-numbered file (it stays put, in the manifest) -- but, like the other example, it also precedes a split
directive.
This seems inconsistent to me, and it's one of a few examples in the file where it's not clear to me what the correct behaviour should be.
I also don't like auto-numbered files because they don't play nice with source control (and even if you aren't using proper source control for your screenplay, if you're using Dropbox or something like it, you get file history for free, which this would interfere with). There's also the matter of not being able to look at the "joined" screenplay file and determine which smaller file to edit, without first opening the manifest, which feels wrong to me. I also think that you end up with a better, more useful manifest file if you need to be deliberate about placing closing tags.
I know that this would be an optional feature, but I'm still not convinced that it adds more value than the complexity it introduces.
from mountain.
Ah yeah I tried to make the gist complicated to try cover all bases. Probably wasn't a good idea because I appear to have confused myself. My examples are indeed inconsistent. The upper part of the gist was supposed to be the very messy way a very messy writer might attempt to use the syntax. I don't now what I was thinking with the lower gist section (so I've now removed it).
I think the crux of my somewhat fractured thinking was two separate but related ideas. The first is optional closing tags; the second is optional filename specification. Considering I managed to easily confuse myself with optional filename specification, and the the source control issues it presents, let's dismiss that idea outright.
To simplify, what if an opening [[ reference: *.fountain ]]
directive may be closed by either [[ /reference ]]
, another [[ reference: *.fountain ]]
, or the end of file?
# ACT I
= Meet the **Hero**.
[[ reference: foo.fountain ]]
FADE IN:
# ACT II
[[ /reference ]]
# ACT III
[[ reference: bar.fountain ]]
## Finale
[[ reference: baz.fountain ]]
> FADE OUT.
>THE END<
....becomes...
foo.fountain
FADE IN:
# ACT II
bar.fountain
## Finale
baz.fountain
> FADE OUT.
>THE END<
In this way, opening directives still need to be closed, but can be closed in a simpler fashion.
from mountain.
This sounds a lot more sane to me. Does this introduce any issues with going in the reverse direction? (And back-and-forth-and-back-again?)
If anyone wants to take a stab at implementing this, feel free :)
from mountain.
I'd only propose that the writer can be lazy in adding closing /reference
tags in the first instance, i.e when first running mountain split
, and that mountain join
would always insert closing tags.
I guess this means a user can mountain join
a screenplay, then points such as this
[[ reference: big-fight.fountain ]]
...
[[ /reference ]]
[[ reference: the-end.fountain ]]
...
would be equivalent to
[[ reference: big-fight.fountain ]]
...
[[ reference: the-end.fountain ]]
...
I can take a stab at implementing, although fair warning, my python skills are weak, the stabs wounds may be messy and ineffectual.
from mountain.
Great idea -- having mountain join
always insert closing tags makes sense to me.
from mountain.
Sorry to dust off something from the distant past; I actually use Makefiles for joining projects these days, so for the sake of housekeeping you can close this if you like.
from mountain.
Related Issues (2)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from mountain.