Hi all, hi Eric,
sorry for my impatient double post, but I'm a bit frustrated. I just started to switch from my heavily used Tomboy to TiddlyWiki in order to use my huge note collection with mobile devices like my android tablet. As most of my notes are really long with lots of subheadings and TiddlyWiki doesn't have an easy to use and sophistcated WYSIWYG solution like Tomboy, it is difficult to make little changes to these notes. The only solution I came around is the EditSectionPlugin from Eric, as I don't want to slice these huge notes into several tiddlers in order to transclude them in a "meta-note". But with the annoying bug I described below this plugin is a bit useless or at least difficult to use. Does nobody have the same problem? Or is there an alternative to EditSection?
<div class='toolbar' macro='toolbar [[ToolbarCommands::ViewToolbar]]'></div> <div class='title' macro='view title'></div> <div class='subtitle'><span macro='view modifier link'></span>, <span macro='view modified date'></span> (<span macro='message views.wikified.createdPrompt'></span> <span macro='view created date'></span>)</div> <div class='tagging' macro='tagging'></div> <div class='tagged' macro='tags'></div> <div class='viewer'><span macro='view text wikified'></span>, <span macro='editSections bearbeiten "diesen Abschnitt bearbeiten"'></span></div> <div class='tagClear'></div>
All these attemps are working like a charm but only with the annoying bug. However it's interesting that after saving a tiddler
or all tiddlers with "save changes" ES puts its standard labeled button rather than my customized version as you can see on the
following screenshot – taken without ES macro code in the tiddler itself but the modified ViewTemplate and after
clicking four times on the "save changes" button:
Is it possible that this behaviour has something to do with my browser (Firefox 10.0.2), Java (???) or even
my operating system (Ubuntu 11.10)?
I've just tried my TW on Android (ICS) with Firefox ... and voilà ... no bugs!
So now I think we have the reason why you're not able to reproduce my bug. I have to install another version
of firefox or maybe I'll try to update Java or something else. But good to know that it is not the plugin.
Offtopic: Is there already a working solution for using TW with Chrome?
Kind regards,
Albert