Am Samstag, 22. März 2014 09:50:45 UTC+1 schrieb Jeremy Ruston: > > Hi Stephan > > > What I'd like to create is a means to save the static HTML of a tiddler. > At the moment I did it by > > 1. Adding a new route to the SimpleServer by patching server.js > 2. Adding a "Publish" button to the view toolbar > > Just to be clear, is your intended use case that one clicks "publish" on a > tiddler in the browser and that triggers the server to save an HTML > snapshot of that tiddler into a folder on the server? >
Yes. More explanation below. > > Moreover the path where the static html is saved is, at the moment, > hard coded in server.js. > > This is the part that confused me; server.js doesn't save static HTML > files. > Yours not. My added route does. Did I say my attempts are an awful hack? > > And is your eventual goal to be able to edit a TW in the browser with the > server automatically updating a folder of static HTML copies of certain > tiddlers? > > Most of the pieces required to do this are now present, but not connected > together. > sever.js at the moment does not save to the filesystem - yes, that's correct. As I said: What I did is an awful hack and now it does save ;) Okay… More information… Here is what the request to me was, why I created that stuff. A colleague of mine knew that I like TiddlyWiki (maybe I mentioned it once to often at work?) and asked me whether TW could help him. He needs to create monthly reports where he needs input from some managment guys. At the moment those guys use Confluence (or is it Sharepoint?) to create the input files and they constantly play around with nice stuff like bold, italics, underline... you name it. Additionally my colleague needs to fetch those information manually. So his idea was to give them TiddlyWiki so that they can create the stuff on his server, where he needs the information and not on some other servers where he needs to pick it up. Additionally he will get rid of the formatting nightmare. My first idea was to simply use the .tid files the server edition creates. But they have no formatting at all, so we need to have the "publish" step which should transform the tiddler to html files (not full html, but html with body, head etc, but snippets) and put the files into a certain folder on the server for his process to pick them up. I'd prefer an automatic process, which should be configurable. I thought of a kind of filter mechanism where the publish would check whether the currently saved tiddler has a certain tag, field, fieldvalue... which triggers then the conversion to HTML. But now that I write it… This wouldn't trigger a publish when a transcluded tiddler changed. Maybe a manal approach is really better. I'd like to programm all that stuff, but need some guidance where I can find proper examples or what I can reuse. You already said: Everything should be there. -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" 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/tiddlywikidev. For more options, visit https://groups.google.com/d/optout.
