> > Just to give you some user feedback about your new chooser. > It work very nice on an Ipad/safari machine, but when I try it on > android with the Dolphin browser, it's a real pain .... because the > Dolphin creator had the same idea before you. > Menu, bookmark, history are accessible with a left slide, and tools > are accessible with a right slide.
Ha! Does the right hand side of the screen have a similar function defined? > So the idea itself is very interesting for mobile/tablet user, but i > think you need also to implement it through a basic menu Yes, the sideswipe thing wont be the only way to access the chooser; I'm hoping to be able to swoosh out from any link to explore the link in the context of related links. The menus exposed by the chooser will in turn be generated by macros that can be used outside of the chooser context. I'd like to make it easy to explore other navigation approaches. > You are doing a fantastic rewriting of my favorite info container, and > like many others I'm waiting the first stable release to use it > intensively. Thank you. It's an honour to have an appreciative audience. Building TiddlyWiki is a bit like making a bracelet; it's not until the loop is complete that it becomes usable for its intended purpose. I'm trying hard to strike a balance between racing to complete the loop and taking the time to ensure that I've got a solid enough foundation to withstand wear and tear. Thanks for your patience as it unfolds. Best wishes Jeremy > > ph Koenig > UnclePhil tc.unclephil.net > > > > On Mar 14, 4:04 pm, Jeremy Ruston <[email protected]> wrote: >> I wanted to give the group a brief progress report on the TiddlyWiki5 >> development work. You can see the latest code >> athttp://tiddlywiki.com/tiddlywiki5 >> >> The heart of TiddlyWiki is a representation transformation engine that >> converts tiddlers between different forms (for example, wikitext to >> HTML) and can selectively update the representations if the underlying >> tiddlers change. This engine has to satisfy many constraints in order >> to be flexible enough to run on the server under node.js or within the >> browser, and to be efficient enough to serve as the basis for the >> interactive features of TiddlyWiki. >> >> There are still quite a few features to be implemented, such as >> slices, sections and filters, but the basic design of the engine is >> now complete. Over the last few weeks I've been gradually adding more >> experimental interactive features, notably the slider and chooser >> macros, so that I can verify that the design is adequate to support >> the interactivity I'd like. >> >> Over the next few weeks I'll be filling out the available macros, >> matching all of the core TiddlyWiki ones. The next big area is to >> implement editing, which I'm thinking through now. I'm hoping to have >> something usable by the early summer. >> >> Some characteristics of the new engine compared to classic TiddlyWiki: >> >> * Everything is a macro. In classic TiddlyWiki the main story column >> and individual tiddler links behave somewhat like macros, but are >> treated completely differently. Now, they are both implemented as >> macros. This change makes the design easier to hack and change, and >> makes TiddlyWiki easier to comprehend, because it reduces the number >> of entity types one has to learn about. >> * No cookies. The idea is to store user interface state data in >> tiddlers instead. You can see this in the story and slider macros. The >> story macro takes as a parameter a reference to a tiddler containing a >> list of tiddlers. To display a new tiddler one just adds it to the >> list, and the story macro will automatically refresh to display the >> newly added tiddler. Similarly, the slider macro can optionally store >> its state in a specified tiddler. One can then flip the slider open or >> closed by setting the text of the tiddler to "open" or "closed". See >> the tiddlers SliderTests and StoryTiddlers to see these features. >> * Efficient sliders. The content of sliders isn't rendered until the >> slider is opened for the first time >> * Base64 embedded images and SVG tiddlers >> * Syntax highlighting for JavaScript tiddlers and fragments. Tiddlers >> of the MIME type application/javascript are parsed to an abstract >> syntax tree which enables syntax elements to be colour coded. In >> addition, comments are treated as wikitext. See the tiddlers >> TypedBlockTests, SampleJavaScript and SampleJavaScriptWithErrors, and >> the TiddlyWiki source code tiddlers whose titles start "js/" >> * Syntax highlighting for JSON tiddlers and fragments. The CSS is >> pretty terrible at the moment; see SampleData >> * Safe inclusion of tiddlers containing untrusted JavaScript. There >> would be a lot of work to fully implement and verify this feature, but >> the idea is that by parsing and recompiling the JavaScript code we can >> use a combination of static analysis and code injection to ensure that >> it doesn't do anything bad. >> >> Under the covers, the API for creating and saving tiddlers is much >> simpler than before. For example, here is the code that updates the >> ClockTiddler: >> >> window.setInterval(function() { >> me.store.addTiddler(new Tiddler({ >> title: "ClockTiddler", >> text: "The time was recently " + (new >> Date()).toString() >> })); >> },3000); >> >> Finally, my approach to the user interface of TiddlyWiki5 is to try to >> design it for touch and mobile first (see the tiddler >> UserInterfaceSketches). With that in mind, I've been experimenting >> with a pervasive new 'chooser' that makes it quick and easy to locate >> and open tiddlers. Right now it's just an alphabetical list of tiddler >> titles, but it's going to evolve into a full hierarchical menu. I made >> a short video to demonstrate it on the ipad here: >> >> https://vimeo.com/38496125 >> >> You can follow the development along >> athttps://github.com/Jermolene/TiddlyWiki5 >> >> 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. > -- 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.
