Mat Actualy I do not find html and css limited too much in tiddlywiki except as I believe we both acknowledge, they are limited in such a way the tiddlywiki platform needs to deliver its promises. A Quine, its ui, its tiddlers, tag and fields.
As I learn more I can see how even if we need to build a plugin we can use any JavaScript html and css feature and technology we want. It just must conform to the platforms requirements and then it can thrive in the tiddlywiki ecosystem. The compliance cost is much less than the advantages gained by participating in the tiddlywiki environment because tiddlywiki delivers in many different ways. File server ui data models interface software development file and server hosting and other plugins and macros. This is a win win exponential. Tony -- 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 https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/20f81eeb-fe26-46f6-aaa7-61706e570e36%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
