Jeremy,
Is this the same problem as raised in the innerwiki iframe refresh? It seems to
point once again to enabling a no, or manual refresh on a given tiddler(s) and
leaving the designer to address it. An example in a video tiddler could be a
button "reload from start" that does a refresh.
Very good.
Its a concern to me as I'd like to be able to make really reliable showcase
sites for film students.
Best wishes
Josiah
On Saturday, 16 February 2019 18:08:48 UTC+1, Simon Huber wrote:
>
> Hi Simon
>>
>> The interruption of playing videos is definitely an issue and I've
>> thought
>
> Hi Simon
>
> The interruption of playing videos is definitely an issue and I've thought
> along similar lines. I'd be interested to see your hack.
>
> I like the idea of supporting a playlist of videos that play one after the
> other so that we could use TW to assemble fragments of video,
Hi Simon
The interruption of playing videos is definitely an issue and I've thought
along similar lines. I'd be interested to see your hack.
I like the idea of supporting a playlist of videos that play one after the
other so that we could use TW to assemble fragments of video, using TW as a
On Sat, Feb 16, 2019 at 3:51 AM Jeremy Ruston
wrote:
> Hi Stefano
>
> I think you've got it exactly right. The details tying the mechanism
> together are in the wiki.parseText() method.
>
>
Thanks Jeremy,
now I finally get it. Inturn, it is the wiki.initParsers() method that sets
up the mapping.
FWIW, I built a plugin using Tinka on TW5 (Tinka 0.4.0) and while it built
the plugin successfully, the build process generated an internal javascript
error "Uncaught TypeError: Cannot read property 'ownerDocument' of
undefined". When it happens I stop and restart the TW5 nodejs server,
though
Hi there,
the following is the same for audio content (+anything heavily depending on
the time-dimension)
I often embed videos in my wikies, mostly youtube, music and educational
stuff.
There's a problem when we want to play a video without interruption...
Anytime the tiddler containing the
Jeremy,
I can see having subWikis, may be part of the answer but critical to many
of the ideas I suggested is they are interactive, thus I favor your idea of
somehow removing the iframe from the refresh tree. Could it be so simple as
tagging a tiddler to be "ignored" (no need to explain why
Hi Stefano
I think you've got it exactly right. The details tying the mechanism together
are in the wiki.parseText() method.
Best wishes
Jeremy
--
Jeremy Ruston
jer...@jermolene.com
https://jermolene.com
> On 15 Feb 2019, at 20:04, stefano franchi wrote:
>
> How does the addition of new
Hi Tony
Good stuff!
The fundamental issue that would prevent most of those applications working
today is that innerwikis are volatile: if the tiddler containing an innerwiki
gets actively refreshed then the innerwiki will be deleted and recreated. I
think that the only way to get around that
Tony,
Thanks for the insights and ideas.
Ref: The list of missing tiddlers in the Sidebar > More > Missing
This area is of almost no interest to a visitor of the tiddlywiki.com
website. What happens in there is not important to the points I am trying
to make, so perhaps we should not spend
11 matches
Mail list logo