@Devin. I like the sound of your idea, but I worry it will add to my workflow, and I'll end up 'not bothering' with the exporting, hence leaving my colleagues with a node.js version of my TW file(s). That doesn't mean I won't look to implement this, but I'll need to wait for when I have a bit more time on my hands (and the truth is the 'import' button works remarkably wekk, I just need to remember to do it on a semi regular basis.
@ Evolena. As I say for Devin, this sound interesting. I hope to find time to incorporation what you both propose into my workflow... Unfortunately right now I have more pressing things to do, I thought it would be simply a case of finding a way to call the import macro with a pre-set file name, and a grep to exclude all the shadow tiddlers. however the node.js version is interesting, and I guess I'll look into it in the future... David On Wednesday, April 13, 2016 at 2:20:05 PM UTC+2, Devin Weaver wrote: > > You're asking for two very different things. On one hand you want the > "single page" version and on the other you want "more than one" page > version. The two are mutually exclusive. > > That said I understand what you want to do and I have two conclusions. > First it is not possible in the current setup you are asking for. This is > for a few reasons. The single page version is a full HTML page. It would > have to download the entire HTML, Parse it, And then selectively import > what you need. To do this auto-magically would require a good deal of > custom code specific to just your needs. This is why the current > implementation relies on a drag and drop from the user and an import > confirmation dialog. The manual process is the best general solution to > this. > > I then did an experiment to see of I could externally include a tid file > using _canonical_uri Turns out this method attempts to embed the content > not import and so obviously a tid file is something the browser doesn't > natively support. > > This brought me to the final conclusion: Node.js with includeWikis > option. By structuring your content as a few Node.js tiddlywiki directories > you could (on your Node.JS dev machine) edit any one wiki in isolation. > Then when finish use the download button or the tiddlywiki --rendertiddler > command to build the final single page wiki which would include what you > want in a single HTML that could be emailed around. > > I use the later solution for my home page (and several other single page > static sites). https://tritarget.org/ (source > https://github.com/sukima/dev-tritarget-org/) My work flow is simple. I > execute the node server (tiddlywiki --server) and then open my site in my > browser (http://localhost:8080/). Then in the browser I add/delete/edit > content to my hearts desire. Then I shutdown the Node.js server, clean up > the tiddlers directory, and save the changes to my version control > software. Then I simple run a build command which creates my main HTML file > (index.html), all the static versions of the pages ( > https://tritarget.org/static.html), and any external images. Then I > simply upload the output (compiled) content to my web server. With this > setup you could separate content by multiple wikis or simply separate them > in directories since each tiddler is represented as a tid file instead of > embedded in a HTML document for storage. > > On Wednesday, April 13, 2016 at 7:42:39 AM UTC-4, David Myers wrote: >> >> I wasn't aware that the Node.js version gave this functionality. However >> I personally like the 'all in a single file' that is TW's main strong point >> for me. This means I can send a sigle TW file to a colleague (or post it to >> a web page) and it will function in place, as it does on my local pc. I now >> my colleagues will copy the main file around, and break all the links ! >> >> I did some more reading, and found the import button is actually a macro >> call, but can't find any details on the macro. >> >> I would be happy if I could pass it a 'default' location to pick up the >> external references file, this would be a reasonable work around for my >> problem, even better if I could get it to select only a certain tiddlers (I >> clearly don't want to import the titile and subtitle, and a bunch of the >> other shadow tiddlers, I could add the button and perform the import all in >> a single mouse click... >> >> >> On Wednesday, April 13, 2016 at 1:21:03 PM UTC+2, Evolena wrote: >>> >>> I don't know how to do that for the standalone version of Tiddlywiki. >>> >>> But, if you want to give a try to Tiddlywiki on Node.js >>> <http://tiddlywiki.com/#TiddlyWiki%20on%20Node.js>, you could then >>> define inclusion of your citation wiki into each notes wiki (cf >>> includeWikis <http://tiddlywiki.com/#TiddlyWikiFolders>). For an >>> example of the configuration, see the tiddlywiki.info >>> <https://github.com/Jermolene/TiddlyWiki5/blob/master/editions/prerelease/tiddlywiki.info> >>> >>> for the "prerelease" edition, which only has tiddlers with new >>> functionalities, and includes the main tw5 wiki. >>> >> -- 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 https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/576dcfdf-3a98-4869-bcf6-a19656b37569%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
