> TiddlyWiki suffers from something that might be called the tyranny of
> the legacy[1]. It's captured in the idea that it is up to the maintainers
> of the core to go out and search for plugins that might be harmed by
> changes to the core.
There is no "tyranny" of the legacy. But there *is* a w
> To get back to what I took as FND's original point, the issue here is
> not this one bug about jQuery, but rather how long it is taking it,
> as an example of many bugs, to get resolved. A healthy open source
> project "should move more rapidly and be more responsive".
That was indeed my main
Note that this is just a first pass - I intend to move further tickets
into the "won't fix" category as well. I also hope that others will do
likewise, or at least suggest tickets that are candidates for "won't
fix".
Martin
On 8 February 2011 12:19, Jeremy Ruston wrote:
> I've reviewed the list,
On Tue, 8 Feb 2011, Eric Shulman wrote:
However, the same may not be true for other, non-TiddlyTools plugins
that are still constructing their own tiddler element IDs. I suggest
that, before releasing any fix for #472, we should perform a simple
text search through as many known, published plug
I'd favour sticking with the underscore escaping, and not attempting
to pursue XHTML compatibility.
Cheers
Jeremy
On Tue, Feb 8, 2011 at 12:21 PM, Paul Downey wrote:
>> The problem is not finding a fix, indeed the proposed solution is
>> escaping spaces with underscores (and underscores with do
> The problem is not finding a fix, indeed the proposed solution is
> escaping spaces with underscores (and underscores with double
> underscores).
I'm not mad about legitimate underscores becoming doubled, and it
seems a reasonable work-round for a HTML document:
http://www.w3.org/TR/html5/e
I've reviewed the list, and am happy with the 13 tickets currently
proposed for closure,
Cheers
Jeremy
On Tue, Feb 8, 2011 at 9:07 AM, Martin Budden wrote:
> I'm reposting this, because the original posting is in the middle of a
> long thread and so may not be that visible.
>
>
> Taking to hear
The problem is not finding a fix, indeed the proposed solution is
escaping spaces with underscores (and underscores with double
underscores). The problem is that this or any fix will break plugins,
so time was allowed for the plugins to be fixed.
I've just heard from Eric to say that he has fixed
> (http://trac.tiddlywiki.org/ticket/472). Although the fix
> is simple to implement, it breaks a number of Eric's plugins so we
> didn't put the fix in release 2.6.2 so that he would have time to fix
> those plugins.
There were a small number of places where TiddlyTools plugins were
using:
sto
Hi,
if spaces are a problem, what about escaping them? Something like url-
escape possible or a html code.
url escaping would be: space%20
and for html something like:
en space
em space
thin space
If spaces in titles could be html escaped, I think not too much would
Hi,
Please keep the code history. Once the tw core becomes a separate
repository on github, it will be a lot smaller than the current svn
repository for tw ,plugins, cook etc.
Keeping the history allows (in principle) to test and bisect the
repository when a new major tw version is coming.
I also
Hi Folks,
3 years ago I even didn't know that TW exist. IMO this issue should
have been fixed 3 years ago. Or may be 2 years ago, after a one year
beta. I started programming TW about one year ago. Not fixing this
issue, now causes trouble, for everyone, that have made the mistake to
use a function
> There is a specific reason we are lagging jQuery: upgrading to a
> jQuery version later than 1.4.3 requires fixing ticket 472 - spaces in
> tiddler ids (http://trac.tiddlywiki.org/ticket/472 ).
Oh, 472 has been one of my big bones of contention, and not just for
jQuery, but for CSS and XSLT -- s
There is a specific reason we are lagging jQuery: upgrading to a
jQuery version later than 1.4.3 requires fixing ticket 472 - spaces in
tiddler ids (http://trac.tiddlywiki.org/ticket/472 ). Although the fix
is simple to implement, it breaks a number of Eric's plugins so we
didn't put the fix in rel
I'm reposting this, because the original posting is in the middle of a
long thread and so may not be that visible.
Taking to heart your suggestion of "cleaning up the cellar" before we
move house, I've created a new milestone in Trac "2011.cleanup". I,
and other members of the Osmosoft team, will
Thanks for the detailed explanation, Eric. I'm now convinced.
Martin
On 7 February 2011 22:20, Eric Shulman wrote:
>> From a personal point of view I practically never look at source code
>> history, other than immediate history (that is the bit of history I've
>
>> I personally find that there
16 matches
Mail list logo
