Just some thoughts. For anyone looking into this, reminder that there's a problem with using the "export" (I call it an export when you move embedded pictures into a separate file directory) and the _canonical_uri function under node.js
The export process is fairly straightforward. BUT, node.js can't serve up external images. To serve up the external images you need a second server that knows how to handle images. AFAIK, the two servers have to run at a different port or a different address. Which means that simple canonical addresses won't work. Instead you'll need to alter the $:/core/templates/canonical-uri-external-image <http://tiddlywiki.com/#%24%3A%2Fcore%2Ftemplates%2Fcanonical-uri-external-image> tiddler to create a long path for the image (e.g. http://127.0.0.1:8084/myimage.jpg). You would need to change the paths for all images anytime you change image server address or port, or if you create a stand-alone version. Remember also that if some of the _canonical_uri's tiddlers already have a custom path inside the existing file structure they will be overwritten by the externalizing process. In that case, you might need to set up an additional flag field and filter to prevent those custom tiddlers from being over-written. For these reasons, it might be preferable to abandon _canonical_uri entirely and display images via a global macro. The macro would provide the path infrastructure and could be quickly changed depending on how the TW is being used (stand-alone, local server, remote server). Different macros could be used for custom images outside the standard file paths. Mark On Sunday, October 11, 2015 at 5:33:20 PM UTC-7, Edward Del Grosso wrote: > > I have a tiddlywiki running TW 5 under node.js. My problem is that I > created about 300 graphics .tid files that force it to run too slow to be > useful. Also have a few .pdf files that I would like to add to it as > individual toddlers without bogging it down. Since I only know enough > about Tiddlywiki to be dangerous it is not complicated. I have tried > numerous times over the last year or so but just lack the basic knowledge > even though otherwise tiddlywiki suits my needs perfectly. > > I am looking to hire someone to do the conversion to canonical url or > whatever it would take to make it responsive. I also would like versions > that would work as standalone, node.js and under my own web server. > > Please feel free to contact me directly at [email protected] <javascript:> > if you might be able to help, along with a feasible timeline and cost. > > Thanks in advance. > > ED > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/44dc0d6d-f84c-4228-be58-f1f0f59507b8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
