simple page construction that is WYSIWYG
It’s well commented upon at this point, but just to hammer the nail in a little further, and smooth a little putty over the top if it: if anything, that is the opposite direction we would go in, in the future. I consider one of Scrivener’s greater weaknesses is that it confuses people into thinking it’s a weak word processor that should be improved (the second is maybe that it would replace desktop publishing software).
That has nothing to do with a Mac perspective, by the way. It is a fundamental, and very broad, difference of opinion on software environments for writers. There is a world out there beyond Word and its ilk, and you’ve managed to bump into perhaps one of the more visible and accessible forms of that. If you want to see where the rabbit hole goes, start searching for writers who use org-mode, Markdown, LyX and so on. Page layout is not some pinnacle everyone should be striving toward, in other words, it’s a much bigger world of preference than that.
support for using external editors especially Word
We do have a feature for that. Refer to §14.3, Synchronised Folders, for more information.
Research support – weblink management and integration; better document imports and export formats. Way, way better table support.
We’re kind of limited by our lifespans on that one. We support what we can through the toolkits we program with, and the third-party libraries we can find. ![]()
Allow for shared (static) Research files that now need to be replicated in each project. That’s just a start…
I may not be entirely understanding all of this, but have a look at what exists already. It sounds a lot like what you’re describing.
Sharing – giving, in first incarnation, other user(s) read-only access to a project…
Sure, it’s something that comes up now and then as a request. But the monumental effort involved in taking a program with thousands of writable inputs and shutting them down to read-only, vs those that would actually want to share their entire project with advance readers (or whatever) is probably not so big. What’s the harm in just compiling and giving your readers something they will be way more familiar with, than a huge program with all of your inner thoughts coiled around every feature in a confusing array?
I’ll admit, there are a few authors where I’d love to see their Scrivener projects, but in most cases I’d be content to read their PDF. You don’t hand out your Adobe Premiere project files and raw footage over to advance screeners, you sit them down in front of a proper cut and show them a movie.
Better support for the Windows community…
We’ve been working on another project for a bit now, which is another way doing just what you want, just for a different program. It’s an understandable confusion, especially if you missed the blog posts and a few forum threads. But I’m guessing from your comment you didn’t look at the Mac change log, where you would have seen similar gaps, for the same reasons, just at different periods of time.

