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. That's why the
plugin library is based on loading the library in an iframe and communicating
with it via window.postMessage.
Best wishes
Jeremy
>
>> 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 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)
>>
>> You can use a JSON file as a container for multiple tiddlers. The format is:
>>
>> [
>> {
>> "title": "HelloThere",
>> "text": "Foo",
>> "type": "text/vnd.tiddlywiki",
>> "tags": "TableOfContents",
>> "modified": "20181206090053690",
>> "created": "20130822170200000"
>> },
>> {
>> "title": "GettingStarted",
>> "text": "Bar",
>> "type": "text/vnd.tiddlywiki",
>> "tags": "TableOfContents",
>> "modified": "20181206090053690",
>> "created": "20130822170200000"
>> }
>> ]
>>
>>> 3) I suspect github or Google pages or (whatever) will muck with the
>>> content-types and so on
>>> but it would be easy to just define "tiddlers over HTTP" - just send them
>>> as regular HTTP pages
>>> where the Body is tiddler (headers and all) - ie the .tid file verbatim.
>>
>> I’d like to be able to support the current range of tiddler file types,
>> either by specifying an override content type, or perhaps by sniffing the
>> file extension.
>>
>>> 4) It seems to me the creating an entire TW (as a single all-in-one file)
>>> is a job of collating and selecting
>>> which tiddlers you want to appear in the final TW.
>>>
>>> Of course, many users will not want this fine level of granularity - but I
>>> rather like the idea of 'remoting'
>>> individual tiddlers.
>>>
>>> Really this is a discussion about what I might call "the granularity of
>>> collaboration" - which I think is an individual tiddler.
>>>
>>> When I've written books most of the discussion with my editor has been over
>>> individual paragraphs and not the
>>> whole - put the parts together into the whole is a different exercise.
>>>
>>> It could be quite fun. See my
>>> https://joearms.github.io/tiddlers/A programmers introduction to the
>>> TiddlyWiki.tid
>> Excellent stuff, that’s a good perspective to write from.
>>
>>> I can image people pushing minor changes to this, or proposing alternatives
>>> - getting the individual tiddlers right
>>> seems a nice step *before* assembling the parts into the whole. Of course,
>>> this is an approximation and the two phases
>>> writing tiddlers and assembling them into larger parts cannot be separated
>>> - but the TW allow seamless flipping between these two modes.
>>
>> Indeed, the “twederation” dream is to be able to do all of this without
>> GitHub, too.
>>
>> Best wishes
>>
>> Jeremy
>>
>>>
>>> Fun stuff
>>>
>>> Cheers
>>>
>>> /Joe
>>>
>>>
>>>> On Sunday, 16 December 2018 18:18:50 UTC+1, Jeremy Ruston wrote:
>>>> 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 - but would be very convenient - can the
>>>>> remote tiddler be run in a
>>>>> iframe? or some other trusted mode?
>>>>
>>>> We can do that from Node.js (running in the browser we can only retrieve
>>>> from HTTP endpoints that are CORS enabled).
>>>>
>>>> There’s a “fetch” command that retrieves tiddlers over HTTP that ought to
>>>> be able to do the job:
>>>>
>>>> tiddlywiki editions/empty/ --verbose --fetch file
>>>> https://raw.githubusercontent.com/Jermolene/TiddlyWiki5/master/editions/dev/tiddlers/HelloThere.tid
>>>> '[!is[system]]' '' --build index
>>>>
>>>> It’s intended for exactly this kind of use case.
>>>>
>>>> https://tiddlywiki.com/#FetchCommand
>>>>
>>>> In particular, a useful arrangement is to save the URLs of the files
>>>> you’re importing in the URL field of tiddlers tagged, say,
>>>> “remote-server”, and then you can use a filter to specify a bunch of URLs
>>>> to read:
>>>>
>>>> tiddlywiki editions/empty/ --verbose --fetch files
>>>> '[tag[remote_server]get[url]]' '[!is[system]]' '' --build index
>>>>
>>>> However, it doesn’t work with GitHub at the moment because it returns all
>>>> files with the content type “text/plain” which confuses the import
>>>> mechanism. We could fix this easily enough by allowing an override content
>>>> type to be specified as an additional command parameter.
>>>>
>>>> Best wishes
>>>>
>>>> Jeremy.
>>>>
>>>>
>>>>>
>>>>> Cheers
>>>>>
>>>>> /Joe
>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google Groups
>>>>> "TiddlyWikiDev" 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 https://groups.google.com/group/tiddlywikidev.
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/tiddlywikidev/13edcef6-3cff-495b-a18f-4858855821ab%40googlegroups.com.
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "TiddlyWikiDev" 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 https://groups.google.com/group/tiddlywikidev.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/tiddlywikidev/0c3515a1-b957-4c66-b470-e9fd8c3ce85c%40googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWikiDev" 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 https://groups.google.com/group/tiddlywikidev.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywikidev/2a5a20bf-37e2-46c9-9285-ee343336409b%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" 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 https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywikidev/5C2DD622-6758-4AFF-B397-BC58BC8679CC%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
