Hi Jed > The local information about available plugins didn't update when there were > updates in the library.
Do you mean that you made updates to the library and that they didn’t automatically show up in the browser? I think it’d be a hard problem to make it make it do that without some kind of explicit reload (either of the page, or within the plugin library UI itself). > Since I am so inconsistent about when I update things this is a problem. I > had looked into a way to solve this a while ago and made an attempt to create > something that closes and re-opens a library to refresh it but I didn't know > how any of it worked so I stopped. This was a few months ago, now that I have > a better idea of how things work I maybe able to make something but I am > attempting to limit myself to only a few projects at a time (currently the > simple TWederation work, the SnapSVG tool and the resume edition). Hopefully > since Tobias is being much more active with the plugin libraries than I ever > was he will create clean ways to reload a library and take care of the > problems I had. For plugin libraries, I think it’s not a huge problem for end users to have to reload their TW in order to see updates made to a library. I can see it’s an issue in development for plugin library maintainers, but for end users I’m not sure that updates to plugin libraries are frequent enough for it to be a problem. For me, it’s only when we look at TWederation that we need to fix the problem by providing a means to reload an embedded server (which is what we might call the contents of an iframe in TWederation; it’s not necessarily a TiddlyWiki, as the plugin library shows). I think it’s a critical part of the mechanisms that we need to introduce to implement TWederation. To be clear, when we’re done, the existing plugin library will be a thin layer over the top of a generic federation layer. In other words, we need to refactor the existing plugin library code for the ultimate implementation of federation. That’s not something we need to worry too much about now, it’s more important to speed up the experiments you’re doing on the UI around federation. Best wishes Jeremy. > > -- > 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] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at https://groups.google.com/group/tiddlywikidev > <https://groups.google.com/group/tiddlywikidev>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/tiddlywikidev/a1fecdbd-67c8-4c9c-8c2d-1eab56ec9eb7%40googlegroups.com > > <https://groups.google.com/d/msgid/tiddlywikidev/a1fecdbd-67c8-4c9c-8c2d-1eab56ec9eb7%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <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/CDC11B5E-4D2B-407A-84FC-C71FCF6376DD%40gmail.com. For more options, visit https://groups.google.com/d/optout.
