About Scrivener 3

[kewms]

Dear Mac Scrivener users:

Please read and bookmark the ongoing series of blog posts regarding changes in Scrivener 3. (http://www.literatureandlatte.com/blog/) Especially the ones about features you use often (like Compile). There *will* be a test later.

Thank you,

Your friendly Scrivener Support Team

[shrumpkin]

Chomping at the bit, as they say, for Scrivener 3. Can’t wait for an update or a release date. I’m trying to tame my inner beast.

[Daniela Wolfe]

I've read all the blogs and I must say I'm really stoked, but I'm curious are these being sent out in the newsletter? If so, I haven't been getting them. In fact, come to think of it I haven't received a newsletter in a long time.

[ScriverTid]

Mods - could you please move this topic to the Feedback forum? I cannot ever use Scriv3 because I won't upgrade past Mavericks, so it's offensive to me to have to read this kind of post here.

By the way, I'm perfectly happy with Scriv2, so what I don't know I can't miss.

Thank you.

[nontroppo]

Oh ScriverTid, you are very likely to get an F in the exam with that attitude...

[jcarman]

Taking offense is a choice as much as not upgrading.

I cannot wait for Scrivener 3! I'm all googly.

[JJSlote]

Reminder that an edit after the fact can remove ill-considered forum comments from the permanent record, until somebody quotes 'em. I've done this to a few of my own on occasion, edited not to improve the wording but to redact the dumbth. We've all been there. Just consider it part of the writing process.

[ScriverTid]

Reminder that an edit after the fact can remove ill-considered forum comments from the permanent record, until somebody quotes 'em. I've done this to a few of my own on occasion, edited not to improve the wording but to redact the dumbth. We've all been there. Just consider it part of the writing process.

Not only do I not consider my remark "ill-considered", I repeat my original request.

Requests for and slavering in anticipation about Scrivener 3 are NOT Technical Support, and therefore properly belong in Feedback, not here.

[JJSlote]

Requests for and slavering in anticipation about Scrivener 3 are NOT Technical Support, and therefore properly belong in Feedback, not here.

Yeah, maybe; I put my inquiry about a Scriv 3 feature into Feedback. But as a matter over which to take offense, it's a bit odd, even for one who will not be able to run the release.

Anyway, this thread was launched by a moderator who sounded like she was fielding too many support questions about matters covered in the blog posts. No gushing anticipation evident...though we can anticipate lots of Scriv 3 questions in Technical Support in the months and years ahead, so it's probably best to get used to them.

Cheers - Jerome

[kewms]

Consider this thread pre-emptive Technical Support.

Having seen the Scrivener 3 beta, I anticipate that a number of changes will require some re-learning among long time Scrivener users. (Myself included.) The blog posts are designed for this purpose, and reading them could save both you and us substantial pain and suffering. Hence my suggestion.

Should you find this thread offensive, feel free to ignore it.

Katherine

[ScriverTid]

I suppose, to be fair, it's not the thread itself which offends me, but the fact that Scrivener 2 has endured through so many releases of the Mac OS and now, all of a sudden, we have to have the latest (which is going to cut off any Mac user who hasn't upgraded - and I'm sure you realise from user statistics, that's a LOT of potential customers lost/alienated).

[kewms]

I suppose, to be fair, it's not the thread itself which offends me, but the fact that Scrivener 2 has endured through so many releases of the Mac OS and now, all of a sudden, we have to have the latest (which is going to cut off any Mac user who hasn't upgraded - and I'm sure you realise from user statistics, that's a LOT of potential customers lost/alienated).

This complaint would be more appropriately directed to Apple. We don't control their libraries.

Katherine

[ScriverTid]

This complaint would be more appropriately directed to Apple. We don't control their libraries.

Katherine

Nor did you through Snow Leopard to Sierra! Scrivener 2 worked all the way through...

[devinganger]

That was all 32-bit code, with an increasing amount of cruft in there to work around against various bugs in the 32-bit Apple libraries, with an increasing amount of cruft to permit code to keep working across a variety of OS versions.

Apple has, from what I understand, been giving less and less priority to fixing 32-bit bugs, and with High Sierra, that's it -- that's the last of the 32-bit code.

Scrivener *had* to move to 64-bit, which means a thorough re-write. New features (and by new features, from the blog posts and hints KB has dropped we're talking a complete rewrite of how Scrivener applies styles plus compiler) + change to 64-bit = not maintaining all of that patchwork of code that's there just to allow backwards compatibility for 32-bit bugs.

If Scrivener DOESN'T do this, they won't be able to go past High Sierra.

Yes, it sucks. I had to go scour eBay to find a used Mac mini so I could upgrade to Sierra (my previous Mac was just old enough hardware that, as far as I could tell, it couldn't upgrade to Sierra for entirely arbitrary reasons). That's Apple's fault, not L&L's. They don't want users hanging around on old hardware forever. They WANT you to buy new hardware. They are the ones who don't support older hardware and older OS versions. And you know what? They may have some valid reasons for doing so.

[scshrugged]

From Apple:

64-bit Requirement for Mac Apps
June 28, 2017
At WWDC 2017, we announced new apps submitted to the Mac App Store must support 64-bit starting January 2018, and Mac app updates and existing apps must support 64-bit starting June 2018. If you distribute your apps outside the Mac App Store, we highly recommend distributing 64-bit binaries to make sure your users can continue to run your apps on future versions of macOS. macOS High Sierra will be the last macOS release to support 32-bit apps without compromise.

https://developer.apple.com/news/?id=06282017a