Path: csiph.com!usenet.pasdenom.info!news.albasani.net!newsfeed.freenet.ag!news2.euro.net!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
Newsgroups: comp.lang.python
Date: Fri, 8 Mar 2013 14:42:18 -0800 (PST)
In-Reply-To: <mailman.3103.1362779514.2939.python-list@python.org>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=68.13.70.209; posting-account=UqPACgoAAACxYISNVHVpmBbtSx3U-vdY
References: <d09d7eaf-9271-424c-8c2f-52cf1b082427@googlegroups.com> <mailman.3103.1362779514.2939.python-list@python.org>
User-Agent: G2/1.0
MIME-Version: 1.0
Subject: Re: Any other screenwriters?
From: richarddooling@gmail.com
To: comp.lang.python@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: python-list@python.org
Precedence: list
Message-ID: <mailman.3106.1362782545.2939.python-list@python.org>
Lines: 71
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:40910

Thank you, Chris. I was trying to avoid the xcode since I know didley about=
 that too, but I'll download it and see if I can get it to run.

THANKS AGAIN

Rick

On Friday, March 8, 2013 3:51:44 PM UTC-6, Chris Angelico wrote:
> On Sat, Mar 9, 2013 at 8:07 AM, Rick Dooling  wrote:
>=20
> > To that end, I would like to take this Ruby script (which works pretty =
well, but throws errors in Mac OS X; some Ruby ones and some Prince ones) a=
nd convert it to Python so I can fix it myself, because I don't know Ruby a=
t all, and would rather work in Python.
>=20
> >
>=20
> > https://github.com/olivertaylor/Textplay
>=20
>=20
>=20
> Hmm. You're looking at a fairly detailed markup language, and a
>=20
> potentially buggy third-party implementation of it. Are you able to go
>=20
> from the https://github.com/nyousefi/Fountain code instead? Given that
>=20
> you don't know Ruby at all, you'd be no worse off there, and it seems
>=20
> to be the "reference implementation".
>=20
>=20
>=20
> Porting either version to Python is going to be a big job,
>=20
> unfortunately. However, given that the reference implementation seems
>=20
> to have been written for a Mac, you have a reasonable chance of being
>=20
> able to execute the code, run the tests, and play with it, while you
>=20
> develop your own version. That's a *huge* help in porting - you can
>=20
> implement piece by piece, comparing in detail both the code and the
>=20
> output of each subsection.
>=20
>=20
>=20
> Alternatively, can you get the xcode version to run directly? (I'm not
>=20
> a Mac person and have no idea whether this is at all possible.) Can
>=20
> you call on it, in some way, and thus write just a wrapper around the
>=20
> outside? Might be a smaller job.
>=20
>=20
>=20
> Ultimately, you're working with a markup format. That means it's all
>=20
> text in, fiddle fiddle, text out... a workflow that Python's pretty
>=20
> good at handling. But you may be letting yourself in for a fairly big
>=20
> job :)
>=20
>=20
>=20
> ChrisA