Save attachments within Taskfile itself
It would be very helpfull if files (attachements) can be saved within a Taskfile in XML as CDDATA.
Drag & Drop would be a perfect addition to this function.
Please don't mark it as "completed" again, cause it's not implemented. The relative path is not the same.


We will leave this open, but please, everyone who wants files to just be moved or copied to a directory that could be paired with the .tsk file, move your vote to this:
http://taskcoach.uservoice.com/forums/26465-desktop-version-windows-linux-mac-of-task-coach/suggestions/991699-allow-real-attachments
This request here will be considered specifically a request for within the .tsk file itself. It is also unlikely that this request will be implemented. The other, which already has more votes, is more realistic.
-
Niklas commented
I would like to be able to link to a folder as an extra option to linking to separate files.
So - when you click the linked folder it opens that folder on your computer. -
tas commented
I don't use Python - that's the only Reason, why i don't code some features in a Taskcoach.
-
tas commented
Ok, i have two solutions for you:
1. TSK-File + StorageFolder which can be set in "Options", so that alle attachements can be stored there as normal files and the Filenames would be some kind of GUID's to avoid Problems.
2. If you want to have a All-in-One-File-Solution you can use ZIP-File, like OpenOffice.Org-Files (ODS / ODT ...) do and the compression level can be set by a user (size vs. perfomance).
In a second solution the TSK-Files would be much smaller (TEXT->ZIP) and you can avoid compatibility Problems with FileFormat if you just read a first bytes of TSK-File to detect XML vs. ZIP.
What do you think?
-
tas commented
-
I won't mark it completed, but I'm not convinced this is a good idea either. It's a lot of work, has the potential to corrupt the task file if we make a mistake implementing this and would create very large task files when you attach more than one or two files.