Re: [tw] Re: Progress on static site generation with TW5

2014-12-15 Thread Jeremy Ruston
I've created an issue to cover enhancing static HTML generation of the interactive widgets: https://github.com/Jermolene/TiddlyWiki5/issues/1237 > An alternative to have widgets that work in a tiddlywiki and in static pages is to have another set of widgets prefixed 'static' - then changing the n

Re: [tw] Re: Progress on static site generation with TW5

2014-12-13 Thread BJ
An alternative to have widgets that work in a tiddlywiki and in static pages is to have another set of widgets prefixed 'static' - then changing the name of the widgets when building a static site - eg reveal becomes static-reveal. The static widgets could be put in a plugin. I think that separ

Re: [tw] Re: Progress on static site generation with TW5

2014-12-13 Thread Arlen Beiler
Of course, that could also go in static.template.css, which is the css template in my server mod. Also, about the JQuery, most dropdowns, tabs, etc. which would need JQuery to be used right are in wrappers with CSS classes. These could be used to identify them and then guess what's what. Just a tho

Re: [tw] Re: Progress on static site generation with TW5

2014-12-13 Thread Arlen Beiler
The server.js file uses static.tiddler.html for the template. The following code would be at the end of the head element in that template. JQuery could be used to link buttons to the associated reveal, but I don't know how that would work for everything. .tc-reveal { display:none; } On Thu, Dec

Re: [tw] Re: Progress on static site generation with TW5

2014-12-11 Thread Jeremy Ruston
Hi Arlen On Wed, Dec 10, 2014 at 11:16 PM, Arlen Beiler wrote: > > Here is a modification to the RevealWidget that allows for other methods > of hiding the reveal section, including Javascript in static HTML. It > should be noted that EVERY reveal on the page will reveal. A little CSS > will fix

Re: [tw] Re: Progress on static site generation with TW5

2014-12-10 Thread Tobias Beer
Hi Arlen, > Here is a modification to the RevealWidget that allows for other methods > of hiding the reveal section, including Javascript in static HTML. > I take it, such a "forceRender" variable would be a global variable set when rendering static pages, correct? I would not even specifica

[tw] Re: Progress on static site generation with TW5

2014-12-10 Thread RichShumaker
I wanted to let you know that I tried to drag and drop one of your 'tiddlers' and it just copied across the URL to TW. So that works well as it is functioning more like a static site and not a TW based Site. I really like it. Rich Shumaker -- You received this message because you are subscrib

Re: [tw] Re: Progress on static site generation with TW5

2014-12-10 Thread Arlen Beiler
Here is a modification to the RevealWidget that allows for other methods of hiding the reveal section, including Javascript in static HTML. It should be noted that EVERY reveal on the page will reveal. A little CSS will fix that. This is a first step toward allowing tabs to work. If the core devs t

[tw] Re: Progress on static site generation with TW5

2014-12-10 Thread Tobias Beer
What I would also find interesting is to load some tiddlers.json into each static file (the same for all) ...with tiddler meta-data, or even the body if anyone thinks it worthy, even the required helper functions to access the beast, and then use some jquery magick to do stuff with it, e.g... do

[tw] Re: Progress on static site generation with TW5

2014-12-10 Thread Tobias Beer
Great work, Jim! 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 think you should definitely render the entire sublists, even if