Martin: Thank you for explaining the reasons behind reverting the macro handling changes. It makes sense not to rush that mechanism if we are unsure as to the consequences.
With regards to code development being ticket driven, I'm afraid this isn't entirely true in my experience and there are exceptions. Eg: I can't remember having seen, nor can I find, a ticket for the macro handling changes that had been proposed. So all I saw in the Trac timeline was the changes being made and the post explaining them, and then the changes being reverted... which was rather confusing. Whilst monitoring Trac usually works well for specific and small changes, more information is usually required for larger scale changes. Also quite often keeping abreast of Trac only allows one to offer an opinion on suggestions made and patches submitted etc., but not to be a part of the deliberation process that lead up to them (especially when it pertains to larger issues since the meat of the discussion now takes place elsewhere and not on Trac or on this group). All of which is why I really appreciate the time you and Jeremy have taken today to provide us with this information and reply to questions. Thank you. I'll look forward to the Trac ticket/ group post for the core review and refactoring that's planned for after the 2.5.0 release. Cheers, Saq On Mar 3, 5:01 pm, Martin Budden <[email protected]> wrote: > Saq, > > to answer your questions: > > 1) We took out the jQuery macro handling. The implementation was a bit > clumsy and rather than lock ourselves into something sub-optimal we > decided to take it out altogether. There are some fundamental clashes > between jQuery and tiddlywiki macros and it may not be possible to > combine them in a way that does not compromise one or the other. One > hope is that this might be possible when we get a bit more jQuery > experience, or if a person with jQuery experience learns enough about > TiddlyWiki to help us resolve the problems. > > 2) You are right, careful review of the code will be required. We'll > start this once the 2.5.0 release is out. And yes more eyes are > welcome. Especially from people who know jQuery well > > The plans for core development are pretty simple: > > i) more jQuery integration, as in (2). The main priority for this is > that compatibility is maintained. Our plans are mainly to replace > tiddlywiki core code with jQuery equivalents where possible. What we > will do will be influenced by feedback we receive and what we learn > about jQuery. > > ii) Fix tickets as specified in trac. > > Core development is pretty well ticket driven. Which tickets get in a > release is somewhat arbitrary, it depends on how important the > bug/feature is, how easy it is to fix, whether someone has submitted a > patch and if anyone in the community has expressed a particular need > for a feature or bug fix. > > Martin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
