Forum

Certainly not. There are new applications around that get rid of old paradigms of which kind of software has to do which job. Instead new software is created while listening to users thus serving their needs. When people on this forum offer their experience and tell what they need, no other user sh...

(…) basically I consider it a suped-up version of TextEdit that is wonderful for writing a nice letter or even an article but not something for doing book layout in. But that’s exactly the point: Text processor is not something anybody should use to create book layouts! Word tried to follow that pa...

Just an update: The export system could also give access to other file formats Mellel can save, so that I could write an export script to save (for example) into Mellel and PDF at once. This would solve the issue with people wanting a save+export feature.

I think the objections to this idea are a little pedantic. Save and Export are conceptually different, but there is a practical problem here. This might be already too esoteric, but: ignoring conceptual differences because of “practical problems” could easily lead to even more practical problems. I...

AFAIK OpenOffice uses two file formats, the OpenOffice XML (used by OO 1.0) and OpenDocument (used by OO 2.0). Which one are you talking about? OpenDocument support would be great – I’d even go as far as making it the default document format if that is possible, because then we would be (at least th...

Well the Yes/No does not mean “I want this feature to be in Mellel” and “I don’t want this feature to be in Mellel” – I think it’s a bit more like “I need this” versus “I do not need this”. Therefore I voted No, because I do not need such a feature. Maybe it would be better to be more explicit in th...

Oh yes and I think it could be wise to wait how the Time machine API looks in Leopard? It sounds like it could bring an easy way to implement the versioning, it would be done the “system way” and have a cool interface on top of it.

A note by: Keeping Mellel documents in a Subversion repository is currently a huge pain, because the .svn directory gets lost when you save the document. I’ve talked about this with Eyal and the conclusion was that there is nothing Mellel is going to do about this, so I guess we have to count on Sub...

I’m sorry to say that, but this poll is IMHO an excellent example of how things should not be done. First, the subject (“Need in Mellel”) does not say much, so that it makes the forum harder to read. Second, it joins three separate issues into one, so that it is not possible to vote nor discuss them...

While I appreciate your work, I think Pointyhead would rather output the text between the auto-titles and get rid of the outlines instead of exporting them (if I understood him right). I should have quoted, I was replying to the last sentence of the post. But the export system ad applies to the aut...

I have created a simple Mellel outliner you can use until something like that gets implemented. You could also vote on the Export system feature request, because that would also bring the outliner into Mellel.

Currently the XML information can be accessed directly, because the file format is actually a directory with an XML file and all the data inside. This is a huge advantage, because all the data can be easily processed in a traditional Unix way – you can transform Mellel documents using a simple shell...

Phil82 wrote:I agree. This feature would be amazing, especially as it will guarantee that your documents will still be readable 20+ years down the road.

That’s already granted by the current XML file format.

I’d like that too, maybe FA1 could create a poll so that we do not all have to write our yeses to the forum? :)

I have created the poll for customizable keyboard shortcuts, so that we can vote there.