Current capability for adding binary files to TW under node.js?

[Shane_Ashby]

This worked, thank you! Now the only thing left is, how do I make it so when I first open the tiddler it shows the “this tiddler contains binary data” banner in view mode? This is how other office files work. With Project files, I see that in edit mode, but in view mode it shows the gibberish text.

The practical result is that I have an extra click or two to open the Project file, versus other Office files.

[jeremyruston]

@Shane_Ashby

How do I make it so when I first open the tiddler it shows the “this tiddler contains binary data” banner in view mode?

Try changing the tiddler text above to:

exports.after = ["startup"];
exports.synchronous = true;

exports.startup = function() {
	$tw.utils.registerFileType("application/vnd.ms-project","base64",".mpp");
	$tw.Wiki.parsers["application/vnd.ms-project"] = $tw.Wiki.parsers["application/octet-stream"];
};

[Shane_Ashby]

This solved it, thank you very much!
And thank you to everyone that responded on this thread. I’m amazed by how quick everyone was to help.

Because the complete solution includes input from two different posts, I’m combining it here for others to reference more easily. Special thanks to TW_Tones and Jeremy Ruston for their help (and to everyone that responded). And of course great thanks to Jeremy Ruston for creating Tiddlywiki itself!

PART 1

@TW_Tones

I don’t have the answer but have some related material from my research, Sorry, I don’t have time to study further, especially since I don’t have project manager installed / in use.

• Have a look at ContentType
  
• the is Operator has a binary option,
• see Control Panel > Info > Advanced > Editor Type
  • Look for tiddlers with the prefix $:/config/EditorTypeMappings/ perhaps clone and make a new one? set to binary for your new content type?
• Note the use of Base64 for binary tiddlers
• Tiddlers that are not binary make use of the editor and the editor toolbar buttons available, vary according to the type field ie content type
• Instructions for adding new types to tiddlywiki

PART 2

@jeremyruston

Hi @Shane_Ashby the instructions that @TW_Tones gave pertain to the configuration for determining which editor should be used for a given content type. However, inside TiddlyWiki’s JavaScript code there is a bunch of more fundamental configuration data for each of the known content types, and it is here that the information for Project files is lacking. For those interested, the code can be seen on GitHub. Without that information, TW doesn’t know that Project files are binary, and so doesn’t correctly base64-encode the content of the file.

The mechanism for the registration of these file types is not currently fully extensible, and so from time to time we add file types that are of general usage. I’d be happy to add support for modern MPPX Project files, given that we already support other MS Office formats, but I’m not so sure about adding support for the older MPP format given that we support .docx but not .doc.

Instead, a custom JS module can be used to register the file type. Create a new tiddler with the following fields:

title: $:/_RegisterProjectFiles
type: application/javascript
module-type: startup

Copy the following text to the “text” field of the tiddler:

exports.name = "register-msproject";
exports.after = ["startup"];
exports.synchronous = true;

exports.startup = function() {
	$tw.utils.registerFileType("application/vnd.ms-project","base64",".mpp");
	$tw.Wiki.parsers["application/vnd.ms-project"]
};

Then save and reload the wiki before trying to import an MPP file.