1
0
mirror of https://github.com/Jermolene/TiddlyWiki5 synced 2025-01-11 09:50:27 +00:00

Roadmap updates

This commit is contained in:
Jeremy Ruston 2013-07-21 21:09:34 +01:00
parent ea8556bb1f
commit 657da6a457

View File

@ -1,50 +1,37 @@
modified: 201305132202 modified: 201307181215
title: RoadMap title: RoadMap
modifier: JeremyRuston modifier: JeremyRuston
tags: docs planning tags: docs planning
TiddlyWiki5 is currently an alpha release, meaning that it is incomplete and subject to change. TiddlyWiki5 is under rapid development at the moment, moving through a series of stages from alpha, via beta into a stable release.
! Alpha Release ! Alpha Release
There has already been a series of alpha releases of TiddlyWiki5. The goal of these releases is to test the new technical architecture and to explore user interface features. The one significant piece of work required before TiddlyWiki5 can move out of alpha into beta is to upgrade the ReleaseProcess so that end users can more easily keep track of the new features.
Some of the features and fixes required before the beta is declared include:
* ~~Synchronisation via HTTP in the browser~~
* ~~Synchronisation via direct file access under node.js~~
* ~~Preliminary integration with TiddlySpace~~
* ~~Preliminary integration with TiddlySpot~~
* ~~Saving changes to a file URI using Firefox~~
* ~~Lazy loading~~
* ~~Better handling of binary tiddlers~~
* ~~Usability improvements to sidebar~~
* A decent ReleaseProcess
! Beta Release ! Beta Release
TiddlyWiki5 will progress to a beta release when it is practical for cautious everyday use. During the beta TiddlyWiki5 will be practical for cautious everyday use but as we perfect the product there will occasionally be situations where we have to make changes that are not backwards compatible. These occasions will be clearly marked in the release notes.
Some of the additional features under consideration during the beta include: The following additional features are under consideration for implementation during the beta:
* Warning when attempting to close window without saving * Warning when attempting to close window without saving
* Use browser local storage to preserve changes in case browser crashes before saving/sync * Use browser local storage to preserve changes in case browser crashes before saving/sync
* Multilanguage support * Multilanguage support
* Ability to ~~inspect and~~ edit tiddler fields * Aliases
* Seamless editing * Search and replace
* Aliases/inheritance * Tiddler renaming
* WikiText ~~table and~~ block quote support * Link tooltips
* More user interface widgets, including: ~tabs~, popovers, toolbars, carousel, ~dropdown~, * Keyboard shortcuts
* ~~Checkbox support~~ * Proper use of ARIA roles
* ~~Search~~ * Import wizard allowing individual tiddlers to be selected for import
* Tiddler themes and ~~wiki themes~~ * Switching to more MarkDown-like syntax for basic formatting such as headings and lists
* Text references: slices and sections, JSON references * `[img[url]]` for remote image embedding, and `[ext[url]]` for explicit external links
* ~~Timed refreshed relative dates (eg, 'last modified 30 minutes ago')~~ * Further WikiText features including block quotes
* Encrypted tiddlers and ~~encrypted TiddlyWikis~~ * Facebook, Twitter, G+ and LinkedIn widgets
* Facebook, Twitter, G+ and LinkedIn macros
* Integration with the browser back and forwards buttons * Integration with the browser back and forwards buttons
* Minification of plugins (JS and CSS) * Minification of plugins (JS and CSS)
! 5.0 Release ! 5.0 Release
Hopefully, TiddlyWiki5 will leave beta and become a full release while we're still in the middle of 2013. This is the point at which it is declared stable enough for general use. It will continue to improve and evolve after this point, although constrained to remain backwards compatible so that plugins and content created for version 5.0 will continue to work into the indefinite future. Hopefully, TiddlyWiki5 will leave beta and become a full release while we're still in 2013. This is the point at which it is declared stable enough for general use. It will continue to improve and evolve after this point, although constrained to remain backwards compatible so that plugins and content created for version 5.0 will continue to work into the indefinite future.