Folks,
I have long sought something similar, and wonder if the following approach
would help with remote tiddlers, loading/importing and performance.
- Provide a utility to save filtered tiddlers (json) to another filename
on the host, not index.html or wikiname.html, a bit like rss
- This is the source wiki publishing a subset of tiddler for remote
load, it can be added to the save process.
- Provide a plugin that given a url (inc file://) to the above address
will silently import (although log it) the tiddlers found in the JSON file
if they have changed, in the current wiki.
I am confident this is possible, I have seen the various requirements
satisfied previously I just to not have the skills to code it, needing a
saver etc...
This same mechaisium could be used to generate multiple files to use a
filter to publish a library. If necessary this can be done through a zip
file, however it would be nice if the remote wiki could unzip and import. I
am a strong believer that a library or importing remote tiddlers would be a
far simpler way to intergrrating tiddlywiki than other suggestions so far,
which with all due respect to those at the leading edge can be hard to
follow.
My current workaround is a package Icon (tiddlers in a json format) that I
can drag from one Wiki in an iFrame to another to install or update.
Tones
On Sunday, 18 April 2021 at 00:09:09 UTC+10 Jan wrote:
> Hi Saq,
> thank you very much for this widget! This is a great help, I have looked
> for something like this for a long time.
> This is a very important puzzlepiece to use TW as an interactive Learning
> Management System.
> For this usecase it is great that it has a silent mode, which makes it mor
> unobstrusive than the fetch-function of Twederation.
> For the interactity of an LMS I would love three other features:
>
> -Can it handle filters to import only certain tiddlers? So far I could not
> see how to implement them in the action-widget.
> -It would be great if it could tag them imported tiddlers like "temp" or
> "imported"
> -It would be very important to have an "Overwrite Filter" determining
> which tiddlers can be overwritten by the imported tiddlers. (For example al
> those whose modifier is not the current user).
>
> Best wishes and nany thanks for this great improvement!
> Jan
>
>
>
>
>
> Am So, 4. Apr, 2021 um 10:49 VORMITTAGS schrieb Saq Imtiaz <
> saq.i...@gmail.com>:
>
> Hi Jeremy,
>
> A little background: I have a couple of ideas in mind for projects to do
> with education with some of the organizations I work with, for which I am
> considering TiddlyWiki. One of them would be very similar to the syncing
> educator and student notebooks project that was based on TiddlyWiki classic
> over 10 years ago. The other involves providing a sandbox for exploration
> and developing skills to do with using and potentially creating/customizing
> digital tools to aid one's own learning. While TiddlyWiki sounds like a
> good fit, it will also be essential that it is hard for the students to
> break the tool itself.
>
> Both projects, if they proceed, will entail quite a bit of custom coding
> to get the user experience just right, so as a first step I wanted to
> understand what was possible today in terms of browser restrictions and
> loading content dynamically in TW5. As mentioned in my original post, I
> realize the use case for this particular prototype is very narrow. However
> I find that sharing ideas and prototypes is rarely a bad idea as it can
> often inspire other ideas in the community, so I try my best to do so
> whenever possible.
>
>
>> Those restrictions still exist. For example, the XMLHttpRequest approach
>> described here generally won’t work from a file: URI, which was a major
>> design goal for the plugin library and Twederation.
>>
>
> That's interesting as I've found it to work without problems to fetch
> content into a local file wiki as long as the remote content is served with
> the correct CORS headers (and the request is made without the
> X-Requested-With header). Or do you mean when the remote content is also
> accessed via a file: URI ? I have not tested that scenario.
>
> Hosting all the wikis with CORS support is an easy requirement to satisfy
> for the projects I have in mind.
>
>
>> It’s definitely time we explored dynamic content loading via
>> XMLHttpRequest in more detail. The constraints get less onerous as we gain
>> better HTTP/HTTPS solutions.
>>
>
> Agreed. I quite miss the possibilities offered by the quite rich ecosystem
> of adaptors that we had in TiddlyWiki Classic and even the sync mechanism,
> despite all the clunkiness inherent in the design and the later
> difficulties imposed by greater browser restrictions.
>
> Regards,
> Saq
>
> --
>
> You received this message because you are subscribed to the Google Groups
> "TiddlyWiki" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to tiddlywiki+...@googlegroups.com.
>
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/7ea4cca2-c07a-486d-a60c-b59c9838c0bdn%40googlegroups.com
>
> <https://groups.google.com/d/msgid/tiddlywiki/7ea4cca2-c07a-486d-a60c-b59c9838c0bdn%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
>
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/af807d81-8ae7-402d-8cc1-71066feac241n%40googlegroups.com.
