> I wonder if it might be worth considering TiddlyWiki 2.x as stable, > give it a maintainer [...] with regular bug fixing releases. > And send all these jquery hopefuls off on a 3.x path that is > considerably more radical and accelerated than the current plans.
Similar approaches have been discussed for quite a while. Fact is, TiddlyWiki has a lot of legacy issues, often preventing significant innovation due to backwards compatibility concerns. While more or less every big project has to deal with that, the issue is more severe in the TiddlyWiki universe because the line between data and code (or user and developer?) is often blurry. One example might be the UI; clearly it needs some work. However, any attempts to improve it are stopped dead in their tracks because even slight changes are likely to lead to complications for existing documents. That situation makes it somewhat frustrating to be a core developer. Having said that, I'm not sure whether a 3.x reboot is a realistic prospect, both in terms of developer commitment and community acceptance. While this response might seem only marginally related to the questions raised by Eric, it appears to me these issues need to be sorted out first, explicitly. That is, do we accept TiddlyWiki as more or less feature complete and continue to maintain it, or do we also want to advance the basic concepts based on the knowledge and experience we've gained in the last few years? -- F. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
