Hi! Actually I had a regression with that as I’m not very happy with the markdown editor and going back and forth with some tests. In essence I’m stuck now in deciding if the attachment should be serialized in base64 inside the doc as before, or do a proper attachment database, which will allow the users to sync any kind of binaries, even outside of the scope of the GDD text (a video file could be a GDD entry for example,,)
This however, brings the question if it is worth the effort, or the potential performance implications (using a db as a file repository ins not the best idea) and if it is, maybe it would make sense to migrate to a file based repository instead of the database approach…
With this idea, drafft could support any “file” and a simple file/folder hierarchy. Multi user sync would be done with third party apps like dropbox, git or similar… Integration with the game engine would be easier, even the game assets could be centralized and taken directly from the workspace…
Sorry for the brain dump!
As for reference, I have a version in dev which allow to reference any drafft object with a internal link (drafft://actor/actorname drafft://script/id_or_alias) etc, but I got a bit stuck with the previous topic that is related