Re: 'Continued's in Celtx

268 views
Skip to first unread message

J Empson

unread,
Mar 18, 2012, 8:07:53 AM3/18/12
to tre...@googlegroups.com

Hi Anil

 

See attached examples.

 

BTW, I see you’re working on an undo feature, too – good! The lack of one is a bit of a dealbreaker for me. I like to experiment with rewrites and then go back to the original and start again – I might hit CTRL-Z 20 times.

 

Its other features I use: its notes, its scratchpad and the colour-coding of plot strands – that’s via the index cards, which I would probably use more if it wasn’t so clunky.

 

Cheers

 

Jonathan   

mercifullyshortreviews.wordpress.com

script - more.jpg
script - no more.jpg

Brad Kayl

unread,
Mar 18, 2012, 8:13:40 AM3/18/12
to tre...@googlegroups.com
Just in general, Mores and Continueds should probably be turned off anyway.  Unless in dialogue they are largely unnecessary.

And, although dual dialogue might make the program more complex, it's useful.  I've used it many times in a screenplay.  Yanking things like this out makes the program seem less useful to the casual user.  Just a thought.


B

Osku Salerma

unread,
Mar 18, 2012, 8:50:09 AM3/18/12
to tre...@googlegroups.com
Hi,

Dual dialogue has never been implemented, so it can't be described as having been "yanked out".

Many things in the world are "useful", yet do not exist because on the balance their benefits do not outweigh the costs. Dual dialogue is one of them. It would take a long time to implement and make the program's code much more complex and harder to maintain. So it would lead to fewer other new features, more bugs, make it harder for new developers to join the project, and make ongoing maintenance much harder. The benefit would be that an extremely rarely used feature would be supported. So, in the end, it's an easy decision not to do it.

"Casual users", as you call them, don't have to weigh these tradeoffs, so of course they want every imaginable feature: why wouldn't they? We as the developers have the unenviable task of having to decide where to allocate our meager resources to get the most bang for the buck, which in the end comes down to saying "no" to 90% of feature requests.
--
Osku Salerma

Brad Kayl

unread,
Mar 18, 2012, 7:05:19 PM3/18/12
to tre...@googlegroups.com
Understood.
Reply all
Reply to author
Forward
0 new messages