[twdev] [TW5][REQUEST] window fullscreen - applying CLASS on

2018-01-15 Thread Simon Huber
Hello Developers, could TiddlyWiki apply a class like "*tc-fullscreen*" to the node when the browser is in fullscreen with F11 or TW's fullscreen button? that would increase the number of possibilities for addressing elements with css I've seen how the tc-dirty class gets toggled in

Re: [twdev] Proposing a plaintext parse & render mode for attributes & more

2018-01-15 Thread Evan Balster
Hey, Jeremy — > The trouble there is that the plaintext vocabulary wouldn't permit > widgets, which would rule out using the list widget. So we would need to be > able to select the output mode between HTML and plain text (that's a > setting that we already support for transclusion). > A

[twdev] TiddlyWiki 5 Dev Hangout #104 will be on Wednesday 17th January at 3pm GMT

2018-01-15 Thread Jeremy Ruston
There will be another developer-oriented TiddlyWiki 5 hangout this Wednesday 17th January at 3pm GMT. At Evan's request, we'll spend some time discussing the optimisations and architectural improvements that he's been exploring, but hopefully we'll get to some other dev-focussed topics — I'm

Re: [twdev] Proposing a plaintext parse & render mode for attributes & more

2018-01-15 Thread Jeremy Ruston
Hi Evan > Vocabulary as a general concept seems like it fits the bill. At that point, > "smart" attributes would just be treated as wikitext with the "plaintext" > vocabulary. The trouble there is that the plaintext vocabulary wouldn't permit widgets, which would rule out using the list

Re: [twdev] Proposing a plaintext parse & render mode for attributes & more

2018-01-15 Thread Evan Balster
Vocabulary as a general concept seems like it fits the bill. At that point, "smart" attributes would just be treated as wikitext with the "plaintext" vocabulary. I have to confess I'd forgotten about typed blocks when I wrote the OP, and by running at parse-time they solve some of the

[twdev] Re: Timer plugin, and iterative computation in TiddlyWiki

2018-01-15 Thread coda coder
On Monday, January 15, 2018 at 11:22:31 AM UTC-6, Evan Balster wrote: > > Hey, Coda — > > Yeah, I'm lazy and write unterminated widgets quite often. > > > General warning about the timer plugin: I'm still working out the > design. In particular, it's possible for a "time=X" timer to be set

[twdev] Re: Timer plugin, and iterative computation in TiddlyWiki

2018-01-15 Thread @TiddlyTweeter
I hope this comment doesn't stop the clock Evan Balster wrote ... > > Elsewhere in the wiki you'll find an "auto-map" also based on the formula > plugin: https://evanbalster.com/tiddlywiki/formulas.html#Auto-Map This > was implemented before element-wise calculations were possible in

[twdev] Re: Timer plugin, and iterative computation in TiddlyWiki

2018-01-15 Thread Evan Balster
Hey, Coda — Yeah, I'm lazy and write unterminated widgets quite often. General warning about the timer plugin: I'm still working out the design. In particular, it's possible for a "time=X" timer to be set after it's supposed to go off, in which case the event will never happen. On Monday,

[twdev] Re: Timer plugin, and iterative computation in TiddlyWiki

2018-01-15 Thread TonyM
Looking good, Perhaps TiddlyWiki could be everything ? Thanks Tony On Monday, January 15, 2018 at 4:25:17 PM UTC+11, Evan Balster wrote: > > Hey, all — > > Show-and-tell time! > > Here's the (undocumented) first draft of my timer plugin, and a simple > simulation I've implemented with it as a