Hi Jeremy (and Martin?),
Thanks for this great announcement and the way you elaborated on this
and explained the way forward with TW. Will be very interesting.
What I would like to bring forward is the timely attention for the
consequences for the translators and translations of TW. I think e.g.
On Mar 3, 5:02 pm, FND wrote:
>
> Those plans have indeed been dropped.
> You're right that we should have posted an update in that previous
> thread - and we'd be happy to elaborate on the reasons there.
> To be fair though, we never got much of a response to those proposals,
> so there didn't
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 exc
This tight integration of macros into the jQuery namespace has been
dropped for now - details in this post from another thread:
http://groups.google.com/group/TiddlyWikiDev/msg/fcdf6000125249f6
-- F.
--~--~-~--~~~---~--~~
You received this message because y
> 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.
Those plans have indeed been dropped.
You're right that we should have posted an update in that previous
thr
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 p
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 ha
On 3 Mar 2009, at 14:39, Eric Shulman wrote:
> [snip]
> Starting with TW250b2, the main() function immediately
> invokes jQuery.noConflict(), right at the start. This prevents jQuery
> from re-defining the $(...) function, so that other definitions of $
> (...) (e.g., InlineJavascriptPlugin) wil
In case anyone else is wondering what the link to the beta is...
http://tiddlywiki.com/beta/
Saq
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" group.
To post to this group, send email to TiddlyWikiD
> "I have used Eric's inline javascript and a TW2.5.0 (with jQuery)
> I'm working through a book and thought I would try and add what I
> leaned to TW. "
>
> There is an error with 2.5.0 (beta 2) with inline javascript.
The problem is with the use of jQuery's $(...) function... here's why:
There
"I have used Eric's inline javascript and a TW2.5.0 (with jQuery)
I'm working through a book and thought I would try and add what I
leaned to TW. "
There is an error with 2.5.0 (beta 2) with inline javascript.
"TypeError: id.replace is not a function" is writen at the bottom of
the BehaviorShe
Previously on TwGroups
Highlighted table looses highlights after editing: why?
( http://tinyurl.com/cgvj4g )
I have used Eric's inline javascript and a TW2.5.0 (with jQuery)
I'm working through a book and thought I would try and add what I
leaned to TW.
Its working!
BUT
when I edit the
I'm happy to announce the beta of TiddlyWiki 2.5. It's a big milestone
release for TiddlyWiki because it marks the first introduction of
jQuery into the TiddlyWiki code base, which we think will first make
life much easier and more productive for plugin authors, and
ultimately lead to a much sleek
13 matches
Mail list logo
