> I just read Jeremy's post announcing the pre Alpha of TiddlyWiki 5 (a > little late to the party).
Thanks for the comments. TiddlyWiki5 has taken a back seat while we've been focussing on TiddlySpace, with some of the innovations from TiddlyWiki5 (like SVG handling) being brought over TiddlySpace. > As you consider WYSIWYG solutions, I hope you will consider getting > rid of edit vs view mode, changing the model a little to "what you see > is what it is." The Aloha editor is seeming to do this with jquery > and html5 (I think), and seems like an elegant solution.Getting away > from modes would make it a step quicker as a note-keeping device. Yes, I like the idea of modelessness, and TiddlyWiki5 is intended to support that way of working. > For myself, I would gladly be rid of wikitext and would make the non- > reversible upgrade in a second! I just want to write -- not code -- > in TW, even if it is only wiki markup. This is the nub of the matter. In TiddlyWiki5 I was trying to simplify the editing environment by switching from wikitext to HTML. The advantage of HTML being that it is native to the web, and therefore better for interoperability, and that browsers offer (primitive) facilities for building rich text editors. However, the feedback from the group was loudly that losing wikitext was too high a price to pay for that ease of use. I believe now that the goal should be to offer direct editing of HTML that has been generated from wikitext, with the edits automatically updating the wikitext. When TiddlySpace has settled down a little more, I hope to return to the topic. > I may be setting myself up for flammage here, but I think it > worthwhile to take a look at what MS's OneNote is doing on several > fronts that TW5 intends to head for: incorporating images and sound > files as drag and drop, hypertext, (OCR of image text!) and most of > all WYSIWYG with no modes. What they are getting wrong is that the > format is not cross-platform, and is not legible to most search > engines. KDE's basket is making a stab at being a OneNote knockoff, > getting most of both the right and wrong parts down, but KDE acts like > a virus on my system, fouling up everything so it is unusable. I was > using Tomboy, which is great for ease of use, but it is a pain to get > at notes cross-platform. I sync to dropbox, but I cannot read the > files on a phone browser like I can TW. THey have a sync service as > part of ubuntu one, but it makes you store your local copy in a preset > location that is not part of my indexed search area. I keep returning > to TW, but keep disliking it because of the lack of WYSIWYG and the > edit mode. > > I would like to see the ease of use of Tomboy, the feature set of > OneNote, the cross-platform compatibility, portability, and user > configurability of TW2, and the html/css direction you are going with > the pre-alpha. I think the roadmap in your announcement bodes well > for all of this. This is a useful articulation, thank you. > I think embracing html5 and css is an important step in the right > direction. One of the limitations of TW I run into at present is that > my desktop search (Google Desktop) does not find any of my TiddlyWiki > text because it skips the JS content. I have been trying, with > limited success and lots of setbacks, to keep all my content (email, > word proc, text files, html. pdf, databases, image headers, audio > tags...) indexed in one search engine. Solutions happen, then go out > of commission (altavista desktop) or "upgrade' themselves out of > usefulness (x1), or don't index everything (google desktop). Getting > my TW content visible as html would be great. I believe that Google Desktop allows for pluggable modules to extend it's search capabilities to other storage media. It would perhaps be possible to write such a module that enabled Google Desktop to search TiddlyWiki files properly. The other side of the HTML visibility problem is the need to present HTML to search engines. TiddlyWeb has facilities for generating HTML on the server, but currently it isn't as capable as the HTML generation that takes place inside the TiddlyWiki client code. > Finally, I still find the opening of linked tiddlers confusing in the > default behavior. Always opening on top would be less disorienting, > and tabs would give the best of both worlds, which is how I have my > TW2 set up presently. The tabs keep the story idea by opening in > order, but keep more info (current tiddler + all titles to other > tiddlers) on the main screen for quick access. The key for me is that TiddlyWiki allows people to choose between these different presentations. > I use notetaking apps every day, and have just arrived back at TW2 (my > FiddlyWiki version of it anyway) after a sojourn through the above > mentioned ones. I am really looking forward to the development of TW5 > and wish I could code so I could contribute more, but that probably is > not happening any time too soon.. Thoughtful contributions like this from prospective users are incredibly valuable, and fundamentally shapes our work. > Anyway, thanks for giving me a listen. Many thanks Best wishes Jeremy > -- > You received this message because you are subscribed to the Google Groups > "TiddlyWikiDev" 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/tiddlywikidev?hl=en. > > -- Jeremy Ruston mailto:[email protected] http://www.tiddlywiki.com -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" 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/tiddlywikidev?hl=en.
