The immediate consequence is that plugin authors can start to use the
powerful facilities of jQuery to simplify and speed-up plugin
development. Over the next few releases we'll be refactoring the
TiddlyWiki core code to take advantage of jQuery too, which should see
a reduction in the size of TiddlyWiki, and improvements in performance
and flexibility.
There's more details about this move over on the TiddlyWikiDev list:
http://groups.google.com/group/TiddlyWikiDev/browse_thread/thread/c0711e68f7caa680
And there's also a roadmap here:
http://tiddlywiki.org/wiki/Dev:Roadmap
I should emphasise again that the addition of jQuery is the only
change between 2.4.3 and 2.5.0, and that the size of TiddlyWiki's
empty.html has consequently increased from 286k to 342k. That extra
space will be recovered as we refactor the core TiddlyWiki code (there
are substantial swathes of TiddlyWiki core code that can be rewritten
much more succinctly with jQuery).
Cheers
Jeremy
--
Jeremy Ruston
mailto:jer...@osmosoft.com
http://www.tiddlywiki.com
Generally speaking, jQuery makes it easier to write certain pieces of
code, because you don't have to worry about certain details.
There are plenty of existing jQuery plugins that could be turned into
TiddlyWiki plugins with minimal effort.
Right now, the only tangible example I can think of is my TiddlyViPlugin
experiment, which is not a spectacular example of jQuery power though:
http://fnd.lewcid.org/tmp/TiddlyViPlugin.html
As time progresses, plugin authors will certainly find great uses for
jQuery within TiddlyWiki.
-- F.
No - we'll continue to ensure backwards compatibility as much as
possible, with the existing APIs remaining functional.
The jQuery integration merely extends the functionality available to
plugin authors.
(While parts of the API will change eventually, that will be a gradual
transition - at the very least we'll keep the DeprecatedFunctionsPlugin
up to date.)
-- F.
It depends, really - if you want something TiddlyWiki-specific (e.g. a
macro), you'll most likely need at least a tiny bit of "glue" code.
Perhaps we'll figure out a common pattern eventually and provide a
generic macro to invoke jQuery functionality - but that remains to be seen.
Do you have anything specific in mind?
-- F.
> I love the TiddlyViPlugin. Even in it's present capacity.
Glad to hear that! (Sort of - see below... )
It's essentially two separate bits of functionality; keyboard navigation
and the command mode - which is the one that's interesting to you?
> please move the command line to the bottom of the window
That's not actually so easy - not with pure CSS anyway (among other
things, there's the issue of fixed positioning, page vs. viewport etc.).
However, you could use custom styles to change the position of the
element (see below).
Also, you might have noticed the to-do list in jQuery.CLI contains an
item "Quake-like dropdown console" - that would then combine the command
line and "output buffer" (also on that list).
However, it's a bit of a departure from the simple Ex-like command line,
so it might not be very compatible with your vision.
> it would be great if you could find a permanent home for it, where
> the future versions can be synced from
Well, I still consider this experimental, so I haven't properly released
it yet.
If/when I get to work on this again, I will find a proper location for it.
(As usual, any code contributions are welcome.)
> could you point out the CSS class that I should use to add z-index to
> the command line?
It's not a class (perhaps it should be?), it's an ID: "#CLI".
(FWIW, Firebug is a great help for this sort of thing.)
-- F.