- Please - Keep up the good spirit. It's almost like experiencing Gandalf and Dumbledore having a fight about who's the one having the true recipe for saving the world... On the other hand, when great TwWizards argue - it should make some noise - if it didn't it would be dissapointing ;-) - so - again... Please keep up the good spirit - and thanks for your great contributions - both of you!!
Cheer up - Best wishes Måns Mårtensson On 3 Aug., 12:02, "Paul Downey (psd)" <[email protected]> wrote: > Hi Eric! > > > For example.... here's a use-case that is very common and causes a > > VERY bad **loss-of-data** outcome: > > oh? That indeed would be VERY bad! > > > 1) edit a tiddler > > 2) make changes (but don't finish editing yet!) > > 3) click any link in the page > > 4) tiddler being edited is closed (without warning) and changes from > > (2) are DISCARDED WITHOUT WARNING! > > But that doesn't happen. The new tiddler is added to the story, > so you end up with two tiddlers in the story. > > http://whatfettle.com/2008/07/SingleTiddlerPlugin > > > Another example.... the "scrolling problem".... > > 1) document has lots of tiddlers, so sidebar tabs display is very long > > 2) open a long tiddler (one that doesn't fit on a single screen) > > 3) read that tiddler (scrolling to the bottom as needed) > > 4) without scrolling back up to the top of page.... click any link in > > the sidebar > > 5) current tiddler is closed, new tiddler is opened, but... > > 6) this does NOT cause the browser to scroll back and, while the new > > tiddler IS displayed, it is SCROLLED OUT OF VIEW, and there is *NO* > > visible tiddler until the user *manually* scrolls the page back to the > > top > > That could be an issue, but luckily doesn't apply to my use-case of > fixed length tiddlers slideshows and index-cards. > > > Another example... the browser's BACK/FORWARD buttons.... > > > Most people who use 'one at a time' tiddler display are attempting to > > recreate the familiar page-transition experience of a 'normal' web > > site. Included in that experience is the expectation that the > > browser's BACK/FORWARD buttons can be used to quickly navigate between > > the visited 'pages' (i.e. tiddlers). > > In fact, this particular expectation is reinforced by the plugin code > > because the URL in the browser IS being updated to show the current > > "#TiddlerName" permalink. However, while the brower's history does > > include each permalinked URL, pressing the BACK/FORWARD buttons does > > nothing, because there is no real page transition occuring even though > > the URL in the browser *does* change. > > Honoring the browser's history is indeed be a useful feature! > > [snip] > > > In conclusion: while I also prefer 'minimal' code when appropriate, > > Cool! I think you've explained carefully how your plugin is far more > complete than mine, and we know has helped many others, so it's > great you wrote it, and continue to help people out and meet their > specific needs. My specific needs are less complete. > > > TiddlyWiki is not an exercise in software engineering principles.. > > Heh, I don't think anyone would disagree with that, which is in > part why we all love it! > > > it's a practical tool for helping real people to accomplish their > > goals, > > Agreed! The fun of development comes from watching other > people use your software. > > But, the plugin as it stands does work well for me so obviously I'm > not "real people" and need to avoid the Voight-Kampff machine ;-) > > > and a 'solution' that does not meet those goals is not a > > solution at all. > > I think that was a /little/ harsh, but hey-ho! > > Best, > -- > Paul (psd)http://blog.whatfettle.com -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
