I'd like some feedback on some tiddlers I've been writing.
If I publish the tidders on github (ie the individual tiddlers and NOT an
entire TW)
is there a syntax that can be used that can yank in and view the tiddler
from any other
TW?)
I realise this breaks security - but would be very
Do you have an addess?
On Sunday, 16 December 2018 11:43:26 UTC+1, joearms wrote:
>
> I'd like some feedback on some tiddlers I've been writing.
>
> If I publish the tidders on github (ie the individual tiddlers and NOT an
> entire TW)
> is there a syntax that can be used that can yank in and
A couple of comments
1) I like the idea of collaborating at the level of "single tiddlers"
All I have to do is put a single tiddler on github and publish the
address and off we go.
2) Bundles of related tiddlers could be published with names like
Tiddler.tid.zip (or something)
3) I
I made a couple of tiddlers here:
- https://joearms.github.io/tiddlers/SharedTiddlers.tid
- https://joearms.github.io/tiddlers/A programmers introduction to the
TiddlyWiki.tid
These pages are made automatically when I push to
Hi Joe
> A couple of comments
>
> 1) I like the idea of collaborating at the level of "single tiddlers"
> All I have to do is put a single tiddler on github and publish the
> address and off we go.
>
> 2) Bundles of related tiddlers could be published with names like
> Tiddler.tid.zip (or
Hi Joe
> I'd like some feedback on some tiddlers I've been writing.
>
> If I publish the tidders on github (ie the individual tiddlers and NOT an
> entire TW)
> is there a syntax that can be used that can yank in and view the tiddler from
> any other
> TW?)
>
> I realise this breaks security
As followup - suppose I had a long list of tiddlers given by URLs
say
[http://some.web.site/path/to/MyTiddler.tid,
...]
This could be quite long. It's rather easy to programmatically gather these
and store them locally (and check for updates)
If I gather all of these -
Hey all,
Is this not a good way to keep plugins and even the core auto-updated?
On Sunday, December 16, 2018 at 12:09:06 PM UTC-6, Jeremy Ruston wrote:
>
> Hi Joe
>
> A couple of comments
>
> 1) I like the idea of collaborating at the level of "single tiddlers"
> All I have to do is put a
On Sunday, 16 December 2018 15:30:02 UTC+1, @TiddlyTweeter wrote:
>
> Do you have an address?
>
> On Sunday, 16 December 2018 11:43:26 UTC+1, joearms wrote:
>>
>> I'd like some feedback on some tiddlers I've been writing.
>>
>> If I publish the tidders on github (ie the individual tiddlers and
Not yet - I'll make a GitHub project and add a few tiddlers later today.
I've started writing up a guide to the TW which I'd appreciate some
feedback on. See if I've
correctly described how things work.
/Joe
On Sunday, 16 December 2018 15:30:02 UTC+1, @TiddlyTweeter wrote:
>
> Do you have an
Hi JoeI can see the files but but they don’t import at the moment because of the content-type problem mentioned above.I’ve attached a quick and dirty patch that gets things working.tiddlywiki editions/empty/ --verbose --fetch file https://joearms.github.io/tiddlers/SharedTiddlers.tid
Hi Diego
> Is this not a good way to keep plugins and even the core auto-updated?
The fetch command only works under Node.js and not within the browser.
As noted above, we can make HTTP requests in the browser but we're restricted
to endpoints that are CORS enabled, which GitHub Pages is not.
Hey Jeremy,
I could imagine the node version (requiring "extra" steps anyway)
supporting auto-updating of plugins/core, while the single-file version is
more like a "frozen" wiki you have to manually upgrade.
On Sunday, December 16, 2018 at 1:22:12 PM UTC-6, Jeremy Ruston wrote:
>
> Hi
I constantly test an adjust filter runs in the Advanced Search tiddler. Also,
if you plug the filter into a $list widget, you can set a custom emptyMessage
value, which will display if the filter returns no results. Good for when you
know what to expect from your filter but it returns no
Josiah,
I think your comment is little unfair. I listed the key components to
learning what Joe wanted, ultimately supported by the content that Mario
was able to post.
Sometimes such broad questions can not reasonably be fully answered, hence
my request for more info, and some guidance
As Mario says, the silent failure is ultimately part of html's
philosophical approach. There is some interesting histories of html that
explains this.
We may expect a debug mode however I think this has being outsourced to
Browser inspect tools.
Regards
Tony
On Sunday, December 16, 2018 at
16 matches
Mail list logo
