The state of the Mellel (a road map of sorts)
Moderators: Eyal Redler, redlers, Ori Redler
-
- Knows everything, can prove it
- Posts: 87
- Joined: Mon Feb 06, 2006 6:38 pm
- Location: Bowling Green, OH
Re: The state of the Mellel (a road map of sorts)
I'm not thrilled about the crossplatform Reader idea. I thnk it diverts development time for little benefit. I can't ask collaborators and readers to install (!) and learn (!!) a new software because I happen to use something different than word. Even in all its apple glory I've never used Pages collaboratiom tool.
Two proposals, which do not exclude each other:
1) What this user wants is good (style preserving) roundtrip conversion to de-facto standards (docx, odf, but more realistically rtf) so that my readers and collaborators can comment and edit on the document. I think that Redlers-supported and Redlers-supplied transformation scripts (XSLTs) are essential.
2) What about embedding some kind of code in the PDF that uniquely connects the PDF file with a Mellel file (e.g. some internal snippet declaring that this file produced by Mellel File 0214324324). Then Mellel could import the comments and markup added to the PDF to that Mellel document. Papyrus even adds its document as a binary stream to the PDF.
Better XSLTs, format documentation and creative interaction with the existing standard for document sharing and commenting (PDF) seems a better way of devoting development time than creating a standalone application.
Two proposals, which do not exclude each other:
1) What this user wants is good (style preserving) roundtrip conversion to de-facto standards (docx, odf, but more realistically rtf) so that my readers and collaborators can comment and edit on the document. I think that Redlers-supported and Redlers-supplied transformation scripts (XSLTs) are essential.
2) What about embedding some kind of code in the PDF that uniquely connects the PDF file with a Mellel file (e.g. some internal snippet declaring that this file produced by Mellel File 0214324324). Then Mellel could import the comments and markup added to the PDF to that Mellel document. Papyrus even adds its document as a binary stream to the PDF.
Better XSLTs, format documentation and creative interaction with the existing standard for document sharing and commenting (PDF) seems a better way of devoting development time than creating a standalone application.
-
- Knows everything, can prove it
- Posts: 677
- Joined: Thu Oct 20, 2005 2:55 pm
- Location: Oslo
- Contact:
Re: The state of the Mellel (a road map of sorts)
Aechallu, I don't think that a cross-platform reader application is what is envisaged, nor do I think that the idea is to produce a reader application that your colleagues would have to install. Ori said:
I think you are right, though, that support of de facto standards -- full-featured export to pdf, full-featured import/export of rtf -- is the best way to make Mellel useful for collaboration.
On a side-issue mentioned in your post: you don't need to ask anything special of your collaborators if you use Pages for tracked changes and comments, because they are preserved perfectly in import and export of doc files. I do all of that kind of commenting in Pages rather than Word these days (Pages seems more stable than Word and the comments are easier to read because the layout is better). This workflow has been seamless since Pages '08, although it's best to keep Word around to convert rtf and docx files into the doc format that Pages prefers, and to sanity-check documents before sending them back.
So I don't really need Mellel for collaboration, this late in the day, and I'd rather that the limited development time was spent on giving it the missing features required for its primary purpose: to properly layout long, structured documents -- e.g. endnotes per section, hanging indents, marginalia, text tracking, better handling of small caps -- and export all of that as nice interactive pdf files (and maybe epub or whatever the e-reader crowd settles on).
But I'm glad the Redlers have a road-map, even if it's not the one I would have wanted.
It sounds as though each such file exported from Mellel would include a standalone viewer application, so that your colleagues can simply double-click it to view the document. I imagine it would only work on OS X (Mac, possibly plus iOS).An "embedded Mellel": you will be able to send Mellel files to others, and they will be able to read them even if they don't have Mellel.
I think you are right, though, that support of de facto standards -- full-featured export to pdf, full-featured import/export of rtf -- is the best way to make Mellel useful for collaboration.
On a side-issue mentioned in your post: you don't need to ask anything special of your collaborators if you use Pages for tracked changes and comments, because they are preserved perfectly in import and export of doc files. I do all of that kind of commenting in Pages rather than Word these days (Pages seems more stable than Word and the comments are easier to read because the layout is better). This workflow has been seamless since Pages '08, although it's best to keep Word around to convert rtf and docx files into the doc format that Pages prefers, and to sanity-check documents before sending them back.
So I don't really need Mellel for collaboration, this late in the day, and I'd rather that the limited development time was spent on giving it the missing features required for its primary purpose: to properly layout long, structured documents -- e.g. endnotes per section, hanging indents, marginalia, text tracking, better handling of small caps -- and export all of that as nice interactive pdf files (and maybe epub or whatever the e-reader crowd settles on).
But I'm glad the Redlers have a road-map, even if it's not the one I would have wanted.
-
- Knows everything, can prove it
- Posts: 87
- Joined: Mon Feb 06, 2006 6:38 pm
- Location: Bowling Green, OH
Re: The state of the Mellel (a road map of sorts)
Nicka-- I agree with your point about Pages. I meant that the share feature in Pages is inconvenient (imo) and that roundtrip support of the word format (including formatting, document features and comments/track changes) makes it even more irrelevant. Word support is one of the main reasons that today I mostly use Pages for my work, but Mellel still rocks in stability, speed, organization features and bibliographic management, all key for long manuscripts. (The omission of styles is intentional
-
- Got the styles thing figured out
- Posts: 9
- Joined: Mon Nov 03, 2008 1:56 am
- Location: Tucson
- Contact:
Re: The state of the Mellel (a road map of sorts)
This is tremendously exciting: if you go through with it, I could begin using Mellel for 80% of my writing instead of 40%, because the people with whom compatibility most matters could edit my documents.* Track changes and comments: this feature is already running (in an Alpha). It was written to play nicely with track-changes features with other word processors (we also intend to add, though I'm not sure if it will be with this release) the ability to export and import track changes, so you will not have to lose formatting and other niceties and continue to work on changes within Mellel).
More at The Story's Story and Grant Writing Confidential
Re: The state of the Mellel (a road map of sorts)
Of course, this solution applies only to Left-to-Right documents.nicka wrote:if you use Pages for tracked changes and comments, because they are preserved perfectly in import and export of doc files. I do all of that kind of commenting in Pages rather than Word these days (Pages seems more stable than Word and the comments are easier to read because the layout is better). This workflow has been seamless since Pages '08, although it's best to keep Word around to convert rtf and docx files into the doc format that Pages prefers, and to sanity-check documents before sending them back.
I use NeoOffice to read "doc" files with track changes, but that will continue to be a partial solution for as long as PC users continue to rely on buggy fonts for their Right-to-Left work.
[Times New Roman is the cause of at least half the RtL problems reported by users on this forum.]
Janet
Re: The state of the Mellel (a road map of sorts)
+1ealvarez wrote:Hope it's just a small feature and it's the reason it was not listed : line numbering.
Line numbering was the only reason I bought Nisus Pro (which turned out to not work well with complicated documents with many (i.e. 50+) footnotes).
Re: The state of the Mellel (a road map of sorts)
I totally agree. Line numbering is required for scientific publications. Therefore this feature would be a great improvement of Mellel, since the software itself already seems to be tailored to the desires of every scientific writer (e.g. in terms of it's implementation of text structuring and bibliography support as well as it's speed and stability when dealing with long and complicated documents)ealvarez wrote:Hope it's just a small feature and it's the reason it was not listed : line numbering. I just ask for this! For scientific publications, it's essential. I need to switch to Word for that.
+1 from me
Re: The state of the Mellel (a road map of sorts)
I would also agree. I use Mellel on a daily basis in a patent firm. Line numbering is a requirement when drafting patent applications in certain countries. It is also desired by some of my clients.2chevaux wrote:I totally agree. Line numbering is required for scientific publications. Therefore this feature would be a great improvement of Mellel, since the software itself already seems to be tailored to the desires of every scientific writer (e.g. in terms of it's implementation of text structuring and bibliography support as well as it's speed and stability when dealing with long and complicated documents)ealvarez wrote:Hope it's just a small feature and it's the reason it was not listed : line numbering. I just ask for this! For scientific publications, it's essential. I need to switch to Word for that.
+1 from me
BTW, I really look forward to the tracking feature. I'm presently simulating tracking manually using character formatting. I need to make changes apparent to my clients. I remember when tracking was introduced in MS Word ages ago and how I liked it. Let's have it soon in our favorite word processing
Re: The state of the Mellel (a road map of sorts)
"I had need for them today: both a document wide watermark ("draft") and a single image placed under some text, not next to it."
These at least are already possible in Mellel. I suggest you read the chapter titled "Images and Figures" in my Tutorial on Mellel's provision for these things.
Don Broadribb
These at least are already possible in Mellel. I suggest you read the chapter titled "Images and Figures" in my Tutorial on Mellel's provision for these things.
Don Broadribb
Re: The state of the Mellel (a road map of sorts)
Thanks, Don, I hadn't realized we could use background images for watermarks.donb wrote:"I had need for them today: both a document wide watermark ("draft") and a single image placed under some text, not next to it."
Unfortunately, the process is still a bit complex.
I would like Mellel to offer a built-in watermark option. If I want to mark all pages of a document as "Draft" I'd rather not have to create an image, size it, adjust the "Alpha" setting and then position it -- I'd simply like to click the draft setting in a watermark option.
Janet
-
- Got the styles thing figured out
- Posts: 11
- Joined: Sat Sep 12, 2009 11:32 am
- Location: Eger, Hungary
Re: The state of the Mellel (a road map of sorts)
Hi!
I don't know if I may only be hallucinating but I think when I came across Mellel a couple of years ago, it was being promoted (in reviews etc.) as a word processor meant for academic purposes. I have already put down a number of feature requests in an other thread, so I don't want to go into lengthy details. My suggestions were all related to capabilities I believe Mellel should have to better cater to scholarly needs (e.g., tables spanning over a single page etc.). Even if it was never an intention to market Mellel as an "academic" word processor, maybe it could be. I have a feeling --although of course I may be totally wrong-- that in the market of word processor, filling this niche could actually work. Why compete with general purpose word processors which may have a huge development team working in the background and so they can have all the glitter and fancy (often unneeded) features.
csaba-
I don't know if I may only be hallucinating but I think when I came across Mellel a couple of years ago, it was being promoted (in reviews etc.) as a word processor meant for academic purposes. I have already put down a number of feature requests in an other thread, so I don't want to go into lengthy details. My suggestions were all related to capabilities I believe Mellel should have to better cater to scholarly needs (e.g., tables spanning over a single page etc.). Even if it was never an intention to market Mellel as an "academic" word processor, maybe it could be. I have a feeling --although of course I may be totally wrong-- that in the market of word processor, filling this niche could actually work. Why compete with general purpose word processors which may have a huge development team working in the background and so they can have all the glitter and fancy (often unneeded) features.
csaba-
-
- Knows everything, can prove it
- Posts: 120
- Joined: Thu Aug 10, 2006 1:48 pm
- Location: Boskovice, Czech Republic
- Contact:
Re: The state of the Mellel (a road map of sorts)
I find it embarrassing that every single post about the future state of Mellel gets overwhelmed with feature requests. It would be such a perfect thing if Redlers could set up some tracker to take care of the feature requests so that (1) people know what’s been suggested before and we don’t have to go over the same things again and again, and (2) we know how many users want some particular feature. This could be something as simple as Get Satisfaction or some other similar hosted service and in my opinion it would make the future of Mellel much more clear and open.
Re: The state of the Mellel (a road map of sorts)
it's been already a few months since the redlers laid down the roadmap to mellel's immediate future. Are we going to see a new version very soon (?)
Re: The state of the Mellel (a road map of sorts)
Or anything else other than crickets?ppnkg wrote: it's been already a few months since the redlers laid down the roadmap to mellel's immediate future. Are we going to see a new version very soon (?)
-
- Knows everything, can prove it
- Posts: 83
- Joined: Tue Oct 25, 2005 5:37 pm
Re: The state of the Mellel (a road map of sorts)
*bump*
Any news on this front? I was excited to hear the pace of Mellel development was picking up again, but so far it's only be as many words. Although it's not as bad as *some* software I use (I'm looking at you, TextMate) there are some features in Ori's original post that I've been waiting for for years. Track changes is chief among them.
Like others, I'm not so worried about the embedded Mellel features, or an iPad version, or Mellel Reader, or any of these "nice to haves." Track changes would have an immediate and direct impact on how I work, and I'd willingly pay for an upgrade for this feature.
Ori: Any updates since your post in August? Are you still not "slacking off?" Have you hit a speedbump or roadblock development issue? Any releases, major or minor, in the pipeline?
Thanks!
Any news on this front? I was excited to hear the pace of Mellel development was picking up again, but so far it's only be as many words. Although it's not as bad as *some* software I use (I'm looking at you, TextMate) there are some features in Ori's original post that I've been waiting for for years. Track changes is chief among them.
Like others, I'm not so worried about the embedded Mellel features, or an iPad version, or Mellel Reader, or any of these "nice to haves." Track changes would have an immediate and direct impact on how I work, and I'd willingly pay for an upgrade for this feature.
Ori: Any updates since your post in August? Are you still not "slacking off?" Have you hit a speedbump or roadblock development issue? Any releases, major or minor, in the pipeline?
Thanks!