![]() ![]() Optionally: encrypt the files, add tags, notes, color-coded labels, and other metadata.EagleFiler stores them in an open format: regular files and folders that are fully accessible to your other applications.With a single keypress, import Web pages, mail messages, or any file on your Mac.Since EagleFiler stores its library in Finder format, you can use it in concert with the other tools in your Mac ecosystem. ![]() ![]() Organize them into folders and annotate them with tags and notes, or leave everything in one folder and pin-point the information you need using the live search. Browse different types of files using a standard three-pane interface. Use it to collect information from a variety of sources. It lets you archive and search mail, Web pages, PDF files, word processing documents, images, and more. Once it is in a file, Sublime Text gives me quick access to all of the files in my site and I can work across them more efficiently with that, at that point.EagleFiler makes managing your information easy. Round tripping back to Drafts at that point gives me no benefit, but I have actions that can help me populate the initial draft version of a page pretty well, so there is benefit at the start. out on my locally served site before publishing it. This is because at that point I’m then working with a file, and I can test all my site links etc. ![]() I typically push the initial content out to a file in my local site repository on my Mac, and then edit in Sublime Text. I create a lot of my initial web site content in Drafts, but I rarely publish from Drafts (though I can). For example, I don’t use BBEdit any more, but instead I use Sublime Text (I work cross-platform). Drafts is good for capturing thoughts and information, building it out through writing, and then either storing it away, or passing it on elsewhere. Web pages, coding, sorting out files of data, editing text files. In that sense it shares similarities with a developer tool chain, but is probably more suited to the sort of work carried out for writing, productivity, and knowledge management related tasks.īBEdit to me is good for where you are working with files. This could be internally, or through passing off to other services (local or online). As a ‘text processor’, what Drafts provides is quick access and an incredible expanse of tools for manipulation of the text. But it is suited to short and medium form writing (again I would say pulling together your memoirs is going to be easier using Scrivener or the like). It is something that isn’t suited to working with files, or for building a coding environment. It isn’t a text editor, and it certainly isn’t a word processor. My personal view of Drafts is as a text processor. Longer form you would probably be better off with a more specialised writing tool like Scrivener. They aren’t meant to support coding, but they are there to help you produce short to medium form writing. Word processors don’t allow you to manipulate the text as much, but they do tend to allow you to structure and format the layout. Those advanced text editors also often give you ways to work in batch with such files and perhaps even build out to wider tool chains to build yourself a development environment for coding. Text editors allow you to quickly edit text in files (a wide variety of files) and the more advanced text editors give you tools to manipulate that text. To give some additional context on the above, the following is based on my own views (/personal, rough, definitions): On the assumption that you put the content into Drafts, what is it that Drafts does not do for you that BBEdit does do for you? Let me rephrase things a little differently. I want to use BBEdit as an editor and Drafts as a processor. Then I’m back to my current mess.Įaglefiler lets you edit in BBEdit while transparently hosting the doc in-app, but it’s a beast, tricky to synch to mobile, and doesn’t have Drafts’ flexibility/agility. Problem with the latter is if I get distracted in mid-edit, the text may remain stuck in yet another BBEdit unsaved doc and never make it back to Drafts. looking for a way to edit individual Drafts in BBEdit without lots of cut/paste. I’d like to use Drafts to hold (and tag, and manipulate, and route to different outcomes) my many in-progress docs, while somehow using BBEdit to individually edit. So I have dozens of in-progress BBEdit docs saved to a gutbucket folder, and many more docs that are unsaved (BBEdit’s auto-save eliminates the risk…and enables my sloppiness!). Problem is that BBEdit relies on Finder for doc storage and org, which feels archaic (I know some make it work, but it’s not for me). I’m a writer, and do all my work in BBEdit because of great grep, Markdown/HTML support, etc. ![]()
0 Comments
Leave a Reply. |