Archizona V You site is impressive and extraordinary it is in tiddlywiki, I would love to know more, incidentally I am building a WordPress / Divi / WooCommerse Shop right now.
*Thomas,* I am grateful for your answer and see no problem with your English. I am quite happy to be set strait and will change my mind on evidence (incidentally I am a modern skeptic, who works hard to be a critical thinker). I do not want to seem like I am hijacking the thread. To clarify I understand what you have told me, Interestingly I have being involved with computers since before 1980, and I am aware that the key to the internet is the same as mainframe computers of the past, basically the server sends and it receives (get and Put), and these can be moments or hours between, so each put and get needed to somehow stand on their own, and a server does not care if you respond except in so far as it may maintain a session status, basically a server gets on with other work and only looks at what you ask it to, when we ask the server to do something (a Put).. I understood that in TiddlyWiki, that the terminal / browser and code in tiddlywiki are feature rich and and can do a lot on their own between put and get (this occurs every save for single files, and every tiddler under nodejs or noteself with couch db). Most of the interaction / response a user gets in tiddlywiki is from the local environment responding, not the server. In my case I have equated a tab in a browser with a session, what you seem to be suggesting is the session is in the browser behind the tabs, and that the browser back and forward, and history are ways of jumping around urls within that session even if the tab changes in some way? What is not clear to me is as long as I make a change and it has not saved yet, when I do save it (except for NodeJS and Noteself), tiddlywiki writes the whole wiki back to the server, If you edited and saved something in between me I would overwrite your changes. like wise if I try and navigate to any other address, and I took this to mean also asking the browser to go to a new address outside the tiddlywiki (and inside for that matter) It will not permit me to leave if I have a save outstanding. Of course If I remain in one tab, where I use tiddlywiki to navigate, and it updates the address bar, I am not actually leaving the tiddlywiki session, and I am not forced to save. It remains in the save session. Of course we can add to this the ability of modern browsers to maintain a website session across browser restarts in some cases (like noteseff without a db). Now back to Archizonas first question why would tiddlywiki maintain a scroll state etc... for every url in a browsers session, when it needs to respond dynamically to the users input? Or is this just a fault of the way we change focus within the tiddlywik? I hope my English is clear enough, and its my mother tongue. Regards 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/09119427-dde6-4f87-b7ac-9da47fd4ed0a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
