Hi Richard, hi Josiah,
I think I will continue my efforts then.
Seeing the syntax fountain uses, it should be the smartest way to do it
interpreting "action" "charakter" etc as list-items and define a special
format for them...because you do not have to close them.
The only problem i see is that in the normal parsing behaviour lists are
broken if they are not preceded by other list items or an empty line
Do you think we could we change that behaviour in the
$:/core/modules/parsers/wikiparser/rules/list.js?
Yours Jan
Am 29.08.2017 um 12:28 schrieb @TiddlyTweeter:
Ciao Jan
I looked more closely at Fountain Syntax.
It might be possible, I think, to do a reduced, but still effective,
simpler subset in a TW markup. Its basically using regular expressions.
The Fountain *forced* syntax is very simple. Lines starting with
special characters get converted in a consistent way. This means the
parser does not to have to make "guesses" the more complex method
uses. The minimal small "forced" set is only this ...
. = Scene Heading
! = Action
@ = Character
> = Transition
Character is the most complex because its a block, not just a line,
i.e. its Character name plus dialogue, and sometimes parenthetic comments.
My point is that it might be just as easy, if not easier, to achieve
directly in TW, rather than import a library.
Just thoughts
Josiah
On Monday, 28 August 2017 22:40:35 UTC+2, Jan wrote:
Hi Josiah,
fountain (at least as it seems to me) is a markuplanguage with a
freeware .js. Hopfully it could be implemented like markup is in
the new release, some features are already very similar.
http://bjtools.tiddlyspot.com/#%24%3A%2Fplugins%2Fbj%2Fmarkdownlike%2Freadme
<http://bjtools.tiddlyspot.com/#%24%3A%2Fplugins%2Fbj%2Fmarkdownlike%2Freadme>
There are implementations for libre-office and mediawiki.
Developping the story of course will be a task for TW.
Yours Jan
Am 28.08.2017 um 17:26 schrieb @TiddlyTweeter:
I feel for you
Its a lot more difficult than it first looks.
The strictness of the screenplay form is both what is good about
it and challenging.
I'm incapable of helping you with code. However I can help with
conceptualisation of how to think about screenplays.
In my own thinking they are a mix of TWO fundamentally different
types of things.
A script is a crossing of "vertical" sections (act, scene etc)
and "horizontal" components that form the "content" -- Dialogue,
Direction, Actions, Scene instructions.
Whilst its relatively easy to think about Tiddlers to create the
"vertical aspect" its not at all easy to conceptualise how to
most appropriately do the "horizontal" content. Should they be
separate Tiddlers? Or just Boilerplate text?
Some cases bring out more clearly the needs. For instance, would
you need to be able to extract ALL but ONLY the dialogue of Eve?
To be able to do that all Eve's dialogue would need to be in
Tiddlers OR you gonna have to develop very smart Regular
Expressions to extract it. The same applies to Scene Setting that
Executive Producers & DPs would need.
My feeling now about Fountain is its excellent if you going for
the Regular Expressions extraction method. TW can actually do
much more than Fountain. I think the issue is getting the right
conceptual model to start from.
Just thoughts
On Monday, 28 August 2017 15:44:44 UTC+2, Jan wrote:
Hi all,
I am working on a tool for screenwriting (So far in german
but with a
languageTiddler to configure:
http://storywriting.tiddlyspot.com/
<http://storywriting.tiddlyspot.com/>)
The aim should be managing ideas, roles and storylines and of
course
formatting Wikitext as a screenplay.
After hours of trying to adapt the normal rules and getting
into an
awfull mess I finally decided I should follow an Idea brought
up by BJ
and Josiah and implement
the fountain library https://fountain.io/
Is there anyone who has done this already?
At the moment I got no clue how this could be achieved.
Yours Jan
--
You received this message because you are subscribed to the
Google Groups "TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to [email protected] <javascript:>.
To post to this group, send email to [email protected]
<javascript:>.
Visit this group at https://groups.google.com/group/tiddlywiki
<https://groups.google.com/group/tiddlywiki>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/d58fb788-661e-4206-ae2b-8659b5d20048%40googlegroups.com
<https://groups.google.com/d/msgid/tiddlywiki/d58fb788-661e-4206-ae2b-8659b5d20048%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout
<https://groups.google.com/d/optout>.
--
You received this message because you are subscribed to the Google
Groups "TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
To post to this group, send email to [email protected]
<mailto:[email protected]>.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/6ed83b13-7134-4909-97df-ccc9fbee5cd6%40googlegroups.com
<https://groups.google.com/d/msgid/tiddlywiki/6ed83b13-7134-4909-97df-ccc9fbee5cd6%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/59A66E8D.5010306%40googlemail.com.
For more options, visit https://groups.google.com/d/optout.
