> This is GREAT news :-) > "An important macro is displayTiddler, which creates a tiddler frame > (marked with the class "tw_tiddlerFrame") that displays a tiddler > complete with a UI for editting, and switching between revisions." > ?1 > The revisionstory: > Is it limited to a "session" (reset when document is saved) or is it a > story following a tiddler for life? (Is revisionstory available for > "standaloneTWs"? and what are the consequences speaking of filesize > etc..? )
The full revision history of all tiddlers can be retained in the local file TiddlyWiki. We'll need some controls to manage filesize (eg only keep the last 2 days revisions, or the last 10 revisions). We could also explore some highly compressed representations which only store the diffs between consecutive versions of tiddlers. The motivation is to be able to work on a TiddlyWiki offline, and then sync it to the cloud without losing your revision history; I think of the revision history as being both an escape mechanism to get out of trouble when you mess things up, and as a way of giving users access to the provenance of information. >> you get a proper WYSIWYG editor, and that when Google looks at a >> TiddlyWiki5 file it will also see the content properly. > ?2 > I sort of like that Google search can't digg what's under the hood, > and I'm the one who is in charge, giving direct links to material... Tiddlers can be stored in the TW5 file in several different formats, some of which will not be crawled by Google, and some of which would be. So, one could arrange things so that ones actual content was visible, but plugins and other plumbing were stored, say, in an x-tiddler script tag so that Google would ignore them. >> Firstly, it will support the existing TiddlyWiki wikifier, so >> people can continue to use and edit tiddlers in wikitext if they want to. > Will the Wikifier edited text be read as easily as html by > searchengines? Tiddlers in wikitext would be stored in the file as wikitext, so Google would see wikitext, just as it goes with current TiddlyWiki. > ?3 > Will transclusions and referring to sections in a tiddler as if they > were individual tiddlers still be available? Yes, although it's not there now. > ?4 > My first instinct when viewing TiddlyWiki5 was to try to drag a > tiddler to the right (second storycolumn?) expecting the next tiddler > to pop up from underneath - something like "rearrange tiddlers" just > in two panes.... That's what I'm aiming for. Essentially, the functionality that one expects from things like NetVibes >> for instance, almost everything is a macro, including tiddler >> containers (aka a TiddlyWiki "story"), and tiddler frames. It uses >> jQuery and jQuery UI properly, leading to much more concise and clear code. > Do you have any specific intentions implying some kind of zui/gui > instant rearranging of tiddlers? Cecily was my testbed for exploring some of this stuff: http://www.osmosoft.com/cecily/ and http://www.osmosoft.com/~jermolene/zoombox/ (Best experienced in Chrome or Safari) I'm interested in being able to right-click on any icon in TW5 and click "edit", and then have the image zoom up to fill the page, with editting controls sliding in. I like the Tiddly960 thing, I've also been getting interested in columnar grid layouts. I like the idea of grids that you can zoom into, and that reveal additional information when you do. I like zooming because it allows you to progressively reveal affordances for direct manipulation. > I would love to see some kind of jquery implementation of Eric's > moveable panels - but that might be a plugindev question?? .. As I say, this should be built in. Furthermore, the tiddler container mechanism makes it easy to, say, arrange that any tiddler link clicked within a story should appear in a moveable popup. > !5 >>I'm specifically interested in the little edge case of being able to >>migrate some decent percentage of foreachtiddler incantations. > I'm glad to hear that - as I wouldn't be able to do most of the things > I'm doing with TiddlyWiki, hadn't it been for fForEachTiddlerPlugin.. > I believe it is needed in some way or another, not to (FND > citation):"... perpetuate reliance on a small group of established > experts. " if TiddlyWiki should be as tweakable for nonprogrammers > (like me) in the future... Yup, I agree: the appetite for FET is one of the big learnings for me about TiddlyWiki. > I wouldn't use TW today if I couldn't solve most problems myself.. > ForeEachTiddlerPlugin gives me the buildingblocks... > On the other hand fET needs an overhaul/update of documentation to > reflect what it is actually capable of in terms of using other params > than "just" text and tags - fields,slices sections and datafields are > currently available as well... > 6 >> I appreciate that this might be a bit out of the blue, but I hope it's a >> pleasant surprise. > Very much indeed - Thanks for sharing the prototype. > I get a feeling that getting to know TiddlyWiki, as a newcommer, in a > year or so - will be a less frustrating experience that it has been. > WysiWyg "out of the box" - will most certainly make guests and > newcommers feel confident from the start.. Many thanks for the kind comments, much appreciated, Best wishes Jeremy > > Regards Måns Mårtensson > > > > On 27 Jan., 19:36, Jeremy Ruston <[email protected]> wrote: >> For the last couple of years, I've been quietly working in the >> background planning for a proper overhaul of TiddlyWiki itself, doing >> some little proof-of-concept experiments, and tracking browser >> developments. I was hoping that we'd get to the point where the >> advantages of completely rebuilding TiddlyWiki from the ground up >> would outweigh the disadvantages of losing backwards compatibility. I >> think that we've now reached that point, thanks mainly to the >> accelerated development of the major browsers. >> >> Over Christmas and New Year, when the office shut down, I finally had >> the chance to spend some sustained time in coding-space, and stitch >> some of these thoughts and experiments into a proper prototype. I've >> kept it completely to myself up until now, partly for fear of >> distracting efforts away from other things. >> >> http://www.tiddlywiki.com/tiddlywiki5/ >> >> It's status is that it's just a prototype, and it's not in a fit state >> to be used in anger; I've focussed on the things missing or broken in >> the original TiddlyWiki, and not paid too much attention to areas that >> don't need to change much. So, it's not currently structured as a >> single file, nor is it capable of saving changes. However, it does >> demonstrate some key new features and capabilities. There are three >> areas I'd like to focus on: >> >> - Embracing HTML >> By default, tiddlers are stored and edited as HTML. This means that >> you get a proper WYSIWYG editor, and that when Google looks at a >> TiddlyWiki5 file it will also see the content properly. It's been >> clear for a long time that wikitext is both a strength and a weakness >> of classic TW, it gives users great power, but it's incredibly >> off-putting for people who expect to type ctrl-B for bold. My goal in >> bringing WYSIWYG to TiddlyWiki is to maintain the ability to type >> macros and formatting directly, without going into weird sub-dialogs. >> This is because I believe that the real power of wikis is the way that >> they elevate linking to becoming part of the punctuation, and hence >> the writing process, instead of an operation performed afterwards. >> Anyhow, it's not all implemented yet, but in edit mode macros are >> represented as special "proxy" visual objects that can have custom >> interactions, but can be selected/copied/pasted just as if they were a >> single character of text. >> >> - Graphics as First Class Citizen >> Both bitmap and vector graphics are now a first class citizen, with >> image tiddlers embedded directly in the TiddlyWiki file, even in IE6. >> There's support for SVG vector graphics (with a plan to cross-render >> to VML for IE support). The idea is to be able to associate icons with >> tiddlers (and hence tags), and use the icons to represent those >> tiddlers in the UI. My mum is busy creating a library of a few hundred >> little conceptual graphics to ship with the thing. >> >> - Cleaning up >> But the real benefit is that the design is now much smoother top to >> bottom. TiddlyWiki originally evolved in fits and starts, and bears >> the scar tissues of me learning JavaScript as I went. In TiddlyWiki5, >> for instance, almost everything is a macro, including tiddler >> containers (aka a TiddlyWiki "story"), and tiddler frames. It uses >> jQuery and jQuery UI properly, leading to much more concise and clear >> code. It properly matches the capabilities of TiddlyWeb, with revision >> history retained for each tiddler and support for different >> MIME-types. >> >> I should say that although TiddlyWiki5 will break backwards >> compatibility, there will be a migration path for existing TiddlyWiki >> content. Firstly, it will support the existing TiddlyWiki wikifier, so >> people can continue to use and edit tiddlers in wikitext if they want >> to. Secondly, you will be able to perform a one-way upgrade of your >> tiddlers from wikitext to html format. There'll be no going back at >> that point, but in exchange you'll be able to use the WYSIWYG editor. >> >> I stress that there's a lot to do before this thing is properly >> usable, but I'm hoping it's at the point where the development >> community can see how it's supposed to fit together, and we can start >> to think about it as a group. >> >> Very roughly, I was thinking of the following roadmap: >> - Declare "alpha" when it works (ie, editting and save changes work properly) >> - Declare "beta" when it's more or less feature complete >> - Declare "release" when it's reliable >> >> I'd hope that we could be at alpha in a couple of months, and release >> sometime in the (northern hemisphere) summer, but it all rather >> depends on what we decide as a group. I'll publish the code in GitHub >> in the next couple very few hours. >> >> I appreciate that this might be a bit out of the blue, but I hope it's >> a pleasant surprise. Do please feel free to ask questions, >> >> Best wishes >> >> Jeremy >> >> -- >> Jeremy Ruston >> mailto:[email protected]://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. > > -- 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.
