Hi Albert, I think an actual scripts library is a great idea!
As for the space that actually holds those scripts and preferably showcases them ...it better not be @customize. There are a lot of these, especially for FET, and they probably need a bit of an explanation too, and we'd all surely benefit from it all being an easily searchable repository. However, @customize is not (intended as) a repository for actual stuff, like code, in-depth examples or even documentation. It would just become too big and showcasing scripts may even be problematic. However, I think we should use @customize as the listing of those snippets and a brief abstract of the problems they solve and how they do it. As for a general script "store", I would be more inclined to use another space for collecting script code. In fact, I just haphazardly created @scripts. Let me think about it for a moment what features and templates would be essential for it. A similar thing would be actual FAQ, actual Tutorials, or even actual Plugins. @Customize is *not* the place to hold them. It is only the place that references them and gives a brief abstract and meaningful categorisation. So as to easily find stuff... elsewhere. Tobias. -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/groups/opt_out.
