Hi Jim Great progress, well done. It would be great to create an official "blogging" edition from your work.
Best wishes Jeremy On Wed, Dec 10, 2014 at 1:00 AM, Jim Lehmer <[email protected]> wrote: > > Thanks to Jeremy's help (tug o' the forelock in thanks), I now have the > TOC generating correctly in a static sidebar. You can see the very limited > results so far here <http://dullroar.com/Home.html>. > > Following is my "road map" from the other thread, with progress comments: > > 1. A *simple* sidebar - title, subtitle, simple TOC, a "tag cloud" *that > works* (more on that in a bit), some other fixed text (copyright, pointer > to TW, etc., so that isn't repeated in every tiddler). > > I have title, subtitle and TOC working. I have moved the fixed "IP" text > to a proper footer element in the template (instead of the sidebar), which > is also ultimately where the TW link will go. > > 2. Per the TOC, I am not looking for a fancy one that expands and > contracts - for now I am working on the idea that "static" remains just > that, and doesn't have any or much of the TW Javascript magic in it. I have > made some other tiddlers, like one called "Categories," that is actually an > auto list of tags, So, if the TOC has "Home," "Categories," and a few other > things, that's enough. I can hide the complexity behind tiddlers the TOC > then points to to do the "heavy lifting" that the expandable TOC does in a > "live" TW. > > This is working. The TOC is currently only two components - one pointing > to "Categories" (which are actually a tag substitute) and a link pointing > back to the Home page. > > 3. Get the tag buttons working, probably by generating them not as buttons > but as links that are styled the same as the buttons. Personally, I believe > the behavior of the current static template (which generates the buttons > with CSS that causes them to receive the "clickable" pointer when you hover > over them but that do nothing when you click on them) to be a bug in the > static CSS if nothing else. > > This is where I am concentrating now. I can already tell it is not going > to be easy. My ultimate goal is two-fold: > > 3.a Tag buttons in each tiddler/page should actually work. > > 3.b I would like a simple "tag cloud" in the side bar. > > 4. I already have a set of tiddlers that I ignore in the main > rendertiddlers via a filter and then "pass through" using savetiddler for > things like an .htaccess file, favicon.ico, CSS, Javascript I am going to > want to embed, etc. That all works just fine. The details are here > <http://dullroar.com/Static%2520Pages%2520How-To.html>, which are just an > expansion of the static example on the TW5.com site. > > The .htaccess file is to set Home.html as the default page, so I don't > have to have a lame "index" tiddler to be picked up as index.html. The > favicon works, etc. > > 5. I figure I will copy and adapt the alltiddlers template to generate an > ATOM/RSS file (I believe someone already did that for classic TW, but > haven't seen that for TW5). > > This is my lowest priority, but will still be a good thing to work out. > > If I can get all of the above working, I think that's a minimum for a good > static site generator that can be a simple blog engine aimed at the likes > of Pelican, Bloxsom, et al. > > Comments welcome. > > -- > 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. > For more options, visit https://groups.google.com/d/optout. > -- Jeremy Ruston mailto:[email protected] -- 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. For more options, visit https://groups.google.com/d/optout.
