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 2009/3/3 Saq Imtiaz <[email protected]>: > > Thank you for that insightful and detailed explanation for the new > beta release and where we go after it Jeremy, it's very much > appreciated. I think adopting jQuery could be a huge boost for > TiddlyWiki if done right. > > I haven't had the chance to look at the new beta in much detail yet, > but I do have some immediate questions: > > 1) Have the changes to the macro handling described in the last post > ( http://tinyurl.com/bxnde5 ) about TiddlyWiki-jQuery work been > dropped? I can't seem to find them in this release. It would be > helpful to know if these changes will now be introduced in a future > release or if they have been dropped altogether, and if so why? Being > privy to such information provides a better insight as to where the > TiddlyWiki code is headed and allows plugin writers to plan ahead. > > 2) In Steps 2 & 3 of the jQuery integration process that you describe, > it seems like a careful review of the entire TW code would be needed > to affect a proper re-factoring with jQuery in mind. What if any plans > have been made for this? Do you have some kind of mechanism in mind to > facilitate this? I do hope that whatever method is chosen, that it > will be done in a completely transparent and open manner which would > allow the community to contribute to the process rather than limiting > it to the few that work at Osmosoft. Whilst I have the utmost respect > for everyone there, the more eyes on this the better! > > As of late I as a plugin writer have really struggled to understand > what's happening with regards to TiddlyWiki core development despite > monitoring Trac very closely and a little more communication like > today's post would go a long way towards helping with that. > > Many thanks, > Saq > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
