• Edit

    With fountain mode enabled an arrow pointing right > will appear next to scene headings that begin with INT. or EXT.

    Click the arrow and all of the scene's contents will be folded into the INT. or EXT. scene heading.

    Hope that's helpful.

    posted in Editorial read more
  • Edit

    First of all thank you for this amazing app! It is just wonderful and I could go on using it as is but wanted to offer a correction to the FOUNTAIN FOLDING.

    CURRENTLY:

    In Fountain mode on Editorial all elements are FOLDED into the SCENE HEADING (i.e. EXT. FOREST -DAY)

    ↧ EXT. FOREST - DAY (Everything is FOLDED into the SCENE HEADING)<br>
    # Act II<br>
    = synopsis<br>
    ## Sequence<br>
    = synopsis<br>
    ### Scene<br>
    = synopsis<br>

    This is incorrect.

    CORRECTION:

    FOLDING (NESTING) for Fountain should follow the following hierarchy. "Scenes" should be folded into "Sequences" which should be folded into "Acts"
    (http://fountain.io/syntax#section-sections)

    ↧# Act<br>

    ↧## Sequence<br>

    ↧### Scene

    Every ACT, SEQUENCE and SCENE can also include a SYNOPSIS denoted by an = (equal sign). Even when the ACT, SEQUENCE and SCENE headings are folded I would still show the ACT SYNOPSIS , SEQUENCE SYNOPSIS and SCENE SYNOPSIS. So ideally I would do the FOLDING...

    ↧ # Act I<br>
    = synopsis (show Act synopsis when Act is folded)<br>
    ↧ ## Sequence<br>
    = synopsis (show Sequence synopsis when Sequence is folded)<br>
    ↧ ### Scene<br>
    = synopsis (show Scene synopsis when Scene is folded)<br>
    ↧ EXT. FOREST - DAY (fold scene's contents into its heading)<br>
    ↧ # Act II<br>
    = synopsis<br>
    ↧ ## Sequence<br>
    = synopsis<br>
    ↧ ### Scene<br>
    = synopsis<br>
    ↧ EXT. FOREST - DAY<br>
    ↧ # Act III<br>
    = synopsis<br>
    ↧ ## Sequence<br>
    = synopsis<br>
    ↧ ### Scene<br>
    = synopsis<br>
    ↧ EXT. FOREST - DAY<br>

    When completely FOLDED it would look like this...

    ↦ # Act I<br>
    = synopsis<br>
    ↦ # Act II<br>
    = synopsis<br>
    ↦ # Act III<br>
    = synopsis<br>

    Thank you again for this wonderful app!!!

    posted in Editorial read more
  • Edit

    First of all thank you for this amazing app! It is just wonderful and I could go on using it as is but wanted to offer a correction to the FOUNTAIN FOLDING.

    CURRENTLY:

    In Fountain mode on Editorial all elements are FOLDED into the SCENE HEADING (i.e. EXT. FOREST -DAY)

    ↧ EXT. FOREST - DAY (Everything is FOLDED into the SCENE HEADING)<br>
    # Act II<br>
    = synopsis<br>
    ## Sequence<br>
    = synopsis<br>
    ### Scene<br>
    = synopsis<br>

    This is incorrect.

    CORRECTION:

    FOLDING (NESTING) for Fountain should follow the following hierarchy. "Scenes" should be folded into "Sequences" which should be folded into "Acts"
    (http://fountain.io/syntax#section-sections)

    ↧# Act<br>

    ↧## Sequence<br>

    ↧### Scene

    Every ACT, SEQUENCE and SCENE can also include a SYNOPSIS denoted by an = (equal sign). Even when the ACT, SEQUENCE and SCENE headings are folded I would still show the ACT SYNOPSIS , SEQUENCE SYNOPSIS and SCENE SYNOPSIS. So ideally I would do the FOLDING...

    ↧ # Act I<br>
    = synopsis (show Act synopsis when Act is folded)<br>
    ↧ ## Sequence<br>
    = synopsis (show Sequence synopsis when Sequence is folded)<br>
    ↧ ### Scene<br>
    = synopsis (show Scene synopsis when Scene is folded)<br>
    ↧ EXT. FOREST - DAY (fold scene's contents into its heading)<br>
    ↧ # Act II<br>
    = synopsis<br>
    ↧ ## Sequence<br>
    = synopsis<br>
    ↧ ### Scene<br>
    = synopsis<br>
    ↧ EXT. FOREST - DAY<br>
    ↧ # Act III<br>
    = synopsis<br>
    ↧ ## Sequence<br>
    = synopsis<br>
    ↧ ### Scene<br>
    = synopsis<br>
    ↧ EXT. FOREST - DAY<br>

    When completely FOLDED it would look like this...

    ↦ # Act I<br>
    = synopsis<br>
    ↦ # Act II<br>
    = synopsis<br>
    ↦ # Act III<br>
    = synopsis<br>

    Thank you again for this wonderful app!!!

    posted in Pythonista read more

Internal error.

Oops! Looks like something went wrong!