An application idea
Yesterday I wrote that I have too many ideas. Ok, here's another one:
A word processor for writers. And when I say writers, I mean novelists, technical book writers, script writers, playwrights...
Word is not very good for a writer. OpenOffice is not good. KWord is probably worse (because of the emphasis on page layout). LyX is probably as good as it gets, and it's not exactly perfect.
A writer actually needs a simple-ish word processor with a bunch of ancillary gadgetry.
How many words/chars/pages a day is he writing
A live word/char counter
A live word frequency monitor (put the cursor on a word and see how often it's used)
Live counter of document/chapter/section/scene size.
Real live outlining. The kind where you drag stuff around and the text follows.
An editable full-text outline view
Multiple files per project
Linking files to places on the text in other files
Associating index cards to places on the text
Grouping index cards (for example, per character, or per location)
Placing them on a timeline or a storyboard
Live Thesaurus / Dictionary
Show definitions and alternatives as the pointer crosses a word.
One click replacement
Per fragment/paragraph styles
There are a bazillion things he does not need, though, like detailed page layouting, or grammar checking.
It would be nice if it could later be easily imported (styled!) into something like Scribus so a decent page layout could be done, but it doesn't need to be in the same app at all.
The text engines in Qt4 are good enough for all this app needs graphically.
RestructuredText is good enough to provide a backend, a parser, an exporter, a reader, a transformer, whatever.
So there it is, another idea I will most likely not implement. Someone please run with it, you can probably make it a rather expensive GPL shareware on Mac ;-)
One of the many not-even-alpha quality apps in my local CVS is just such an app from when I was on a big creative-writing kick a year ago or so.
It actually all started when I realized that I preferred writing in KMail over any word processor. I had line count, "draft" functionality, inline spell checking and easy to read wrapping.
I think a lot of the things that you listed are just there because they're things that you don't not need. In a creative-writing program you want to keep things minimal because the main goal of a writer is to keep writing -- your goal is a suped-up spiral-notebook. Things are presumably a bit different with non-fiction.
A constant word-count I suspect would distract me, though it'd be nice in a dialog. (Incidentally I found myself pasting stuff into KWord just for that.) Index cards, references and styling are also right out.
Sections and version control are important though. "Outlining" is just a matter of having your sections not filled in yet and having a way to list them.
The direction that I considered going was hooking things into a wiki backend for colaboration and version control. That would also make it possible to edit outside of the app. Bonus points if it could then generate and RDF stream of latest changes. As you mentioned, export of a finished work for layout and styling to a proper editor / layout tool is desirable, but if the formatting is minimal, RTF is probably suffecient.
So, yeah, this has also been on of the things in my never-going-to-happen queue. I think it is noteworthy that the work flows for fiction and non-fiction are rather different.
Why do you need a whole new application? Would improving on the already existing programs (Koffice/Openoffice) not be in everybody's interest?
The developer doesn't have to start from scratch.
The user can have a more "professional" text processor, in one application
Why a whole new application? Because the end result is very different from a "regular" word processor.
Which, to be honest, I am not sure are the right UI for almost any sort of writing other than letters to be printed and mailed.
I'd say that those goals overlap for a huge partition with KWords goals.
If you find these things exciting, please join us in the creation of KOffice2.
And if you actually wrote a book in KWord you'd see that there is little to no emphasis on page layouting. At least, thats what real authors told the KOffice crew :)
Very interesting and I've been thinking about something like this myself, as well as a DocBook editor in Qt.
However I agree with previous commentators that it's a huge overlap with a regular word processor, and that the future KOffice2 code should be used as much as possible.
Very good for translators of books too.
There is a huge problem for me in hacking Koffice. Or rather two.
1) I can't get my head around the code. That's surely a limit on my head, not the code :-)
2) It's C++. Which I am really tired of :-(
As for page layouting... if I open Kword, I see page layout everywhere. I am sure it can be hidden but by default it's far from the blank page that leads me to "just start writing"... It's **busy looking** maybe I feel forced to use all those shiny knobs and buttons, and I am distracted by the pretty lights :-)
But: it has those rules, it shows the margins, a gray area around the page, it has that weird tree-that-is-not-an-outline-and-I-don't-understand on the left, and about 45cm of toolbars.
Then again, I have never tried writing something long in kword, much less customaizing it to look the way I think it should. But I did try that on other word processors, and it was just frustrating.
Maybe some easily-selectable views, like a Tech Writer view, a Novelist view, Layout view, etc., would be a good idea for KOffice 2.0? Allow for customizeable views?
Hi! Your idea is one of the cool apps I'm missing on Linux (I don't know about other OS's, since I don't use them). I've found something SIMILAR to what you're talking about wich is great for movie script writers and based on mozilla, as far as I know. It's called Celtx and you can get it here:
Unfortunately I'm searching for a more Comics Scripting oriented tool and I haven't find it yet! If you ever start a project...let me know! :)