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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/7ea4cca2-c07a-486d-a60c-b59c9838c0bdn%40googlegroups.com.
