Jed, Thanks for your view here. I understand the complications you describe. I suppose I am hoping we can provide those "equivalent structures" a little more comprehensively and if possible in a systemic way so more of the html5 standards can be applied. Perhaps keeping it simpler.
Regards Tony On Tuesday, August 7, 2018 at 5:56:30 PM UTC+10, Jed Carty wrote: > > Tony, > > TiddlyWiki being able to display things in multiple places creates > problems for forms like you are suggesting. HTML forms are designed with a > very limited use in mind. You have a form and you have a submit button and > when you click on the submit button the form data is sent to a server and > it is the responsibly of the server to figure out what to do with it. > Adding javascript on top of this some things can be done in a browser, but > that leads to other issues. TiddlyWiki lets you display the same content in > multiple places, this breaks the assumptions used by html when using id > attributes. An id is supposed to be unique in a page so that you can use > getElementById to pick a unique element. If you have that in a tiddler that > is displayed in two places than the behaviour is not well defined. > > And anything that uses the html dom for storing the state the way that the > forms you mention do is going to be a problem if the tiddler gets > refreshed. For example if you have the form in a tiddler displayed using > the tabs macro and switch tabs after entering information that information > may be lost. Or if you have the form in a tiddler that is displayed > multiple times there is nothing to prevent you from entering different data > in it in each place. In a situation like that with html the error is in the > html and there isn't an expected outcome for when you try and use the form > because it is given bad data. > > And as a personal opinion, I think that the jquery approach of storing > everything in the dom is a bad idea. It leads to very difficult to maintain > systems where changing one part has unintended and unpredictable side > effects because there is nowhere to look to determine what actually affects > each component. TiddlyWiki already supports html, there are a few cases > like forms where the way that they are used doesn't work in the tiddlywiki > context but we have equivalent structures that do work. > -- 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 tiddlywikidev+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywikidev@googlegroups.com. 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/c535bdb2-b723-44c5-8678-fd912fdce76b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
