I use DT and DTTG. I am storing my meeting minutes in there in markdown. I’ve never really used DT to work in, rather, it’s been a storage unit for all my documents. However, DT is a solid app and with internal links is pretty awesome. My only problem is that writing markdown notes in DTTG on the iPad is not a pleasant experience.
The editing window font size does not resize elegantly and often leaves text chopped off at the end of the window if you zoom in. There is little code highlighting, so you need to switch from edit to preview, no simple ui themes. In general it doesn’t hold muster to Obsidian, iA Writer and other markdown editors.
I find that I can edit an EXISTING document in DTTG to be fine, not great, on the iPad. I was thinking about new documents using DTTG on the iPad in my reply. For some inexplicable reason, DTTG has a small editor window when creating a new document. However, editing an existing document is fine, it is a full size window.
I agree. One can do that with DT on the desktop but not the iPad @svsmailus PS, this problem is solved if one indexes files in DT rather than importing them. In that situation, you can use any MD or plain text editor/application.
DT synces both ways with the indexed folder so that all files are available on all devices. It will sync imported or indexed files but if imported one cannot, to my knowledge, open the imported DT files in an external editor on the iPad whereas one can open indexed files in an external editor because the files reside outside of DT.
Regarding the indexing of Files with DT, while it is of course a possible option, and there are for certain a lot of reasons to do so, I would always recommend to import the files rather than indexing them.
With indexing, you have to observe a couple of “rules” how to handle the documents in the future, to not run into some kind of trouble, because the Docs where moved, or deleted, and get lost, or lose the connection with its depends within DT. The DT-Forum has some threads about this.
The discussion about indexed files is almost right, here, but to clarify/confuse further…
Indexing and syncing creates a four-point “sync” for a file. The same file is accessible from the (1) the macOS file system, (2) DEVONthink on Mac, (3) the iOS file system (assuming the indexed files are synced), and (4) DEVONthink on iOS.
This creates a “U-shape” sync. DEVONthink will sync between iOS and macOS, and the sync service you use will sync between iOS and macOS. The “bridge” of the U is on the Mac: while DEVONthink is open, changes between the file in DEVONthink and the file on the file system are kept in sync.
Ergo, I strive to:
only edit an indexed file from one “arm” of the U, and;
always keep DEVONthink running on the Mac (or at least don’t expect to edit a file from the file system on iOS and then see those edits show up in DEVONthink on iOS if you don’t have DEVONthink open on the Mac).
The simplest way of thinking about it is to treat DEVONthink on iOS as read-only.
I’ve been doing this for years, though. It works well.
I don’t say, that indexing is not possible, or that there might not be good reasons, to do so, but you have to be aware of the problems you might put into your basket on that way.
And the problems you have with moved or deleted files within DT and/or the filesystem, the lack of syncing with the filesystem, and so on, are still the same, as far as I can tell.
And I also don’t see, how this could be “fixed” in the future, as it is less a “Bug” within DT, but more a general problem of the “method”.