When we moved from subversion/trac to github we deliberately didn't move over all the tickets. The view being that if anyone was sufficiently interested in a feature or fix, then they would raise an issue in github.
I'm quite happy to put this in the next release. To answer your question about core development: in general the best way to get a feature or bug fix is to raise it as an issue on github, https://github.com/TiddlyWiki/tiddlywiki/ Postings in this group will normally be picked up, but can be more easily missed or overlooked (or could be subject to the "can't find the thread/discussion" problem). A +1 or +2, of course, indicates that the feature is wanted - but again it makes things easier if an issue is raised. And an issue with a patch or merge request and test code is even better. On Sep 30, 10:56 am, Måns <[email protected]> wrote: > +2 :-) > > On 30 Sep., 09:23, Tobias Beer <[email protected]> wrote: > > > > > > > > > This sounds like a very appreciated change. > > Much better than each individual plugin doing exactly that for > > tiddlyspace compatibility. > > Please get this rolling. > > > Cheers, Tobias. -- 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.
