Archive for August 10th, 2013
It appears the folks that have brought us Scrivener also have another product avaialble now: Scapple. It looks like a form of mind-mapping/idea-mapping software, but I haven’t had the chance to explore it enough to get a feel for it, or to compare it with features already present in Scrivener, to see how well it works. Nor have I had the chance to watch the intro video they have on the site.
What I can tell, however, is that it looks like it could be useful for outlining and timelining projects. I’m also wondering how integrated it might be with Scrivener (ie – could I drop and entire “map” in as a “research” element, or would only the individual notes copy over?). Something interesting to explore through their trial version. I’m currently looking at their Manual to see if I can get a concept feel for how it works.
If you’re on a Mac, check out the page. It might be something that could be useful.
I think I’ve mentiond before that I have been using Scrivener for most of my long-form writing. While I envision switching completely over, it’s a debatable point for short fiction, especially the way I work (writing longhand, then typing it all up). Sometimes it’s just easier to dump it all in Word and keep going it the story is only ten to twenty pages.
That might change when the iOS version finally happens. No, it’s not out yet, but as mentioned before, it is in the works, and it’s release will make me happy for other reasons. Chief among them? I won’t have to haul my Laptop around if I want to type up pages for the Novel-in-Progress. Since that first post, back in March 2012, i’ve sporadically gone back to the company’s site to check for updates, with nothing new.
Then I found this the other day. (Yes, it’s been out since April. Sporadic visits, remember?)
The frustrating part for us is that, for the past four or five months, we have had a version of Scrivener for iPad that is in many ways so nearly there and yet still not ready for beta-testing. We hit snags with the rich text system (or iOS’s lack of one) and building the synchronisation code is incredibly complicated because of Scrivener’s package-based file format, but we had most of the other basics in place and felt we were really making good progress.
But they had some other issues to address, which involved having to bring in a second iOS developer.
For those that haven’t been by the L&L site for a while (like me), I wanted to spread the news… It’s still one I will definitely be looking into when it finally rolls out.