The 1.0 version
vakata
I just decided to inform everyone interested on the progress of the
project. I have been working hard on the 1.0-beta for the last 2 weeks
and things are finally looking up.
The 1.0 version will be VERY plugin friendly (as an example - even
selection is now a plugin). There will be no such thing as datastore/
plugin - it is all plugins now.
A quick heads up to plugin authors - there is a `$.jstree.plugin`
function which lets you register your plugin (using an init/destroy
function, defaults and functions which will extend jstree instances).
You can even overwrite existing functions, but will still have access
to the old function.
No more $.tree, jsTree or jstree - all classes are prefixed "jstree-"
and the plugin itself will be accessible as $.jstree (instead of
$.tree). Even events fired by the trees are now namespaced.
As for events - there will be no more tedious function writing and
attaching to the callbacks config section - the tree now fires events
on the container. This means you can now use standard jQuery code to
work with tree events:
$("container-here").bind("jstree.select_node", function(event, data)
{ });
the data variable will contain the arguments passed to the function
and the result of that function, along with some other custom jstree
data.
NOTE: there will still be some callbacks in the config, but a lot less
and only where really needed. Also - I am doing my best not to stop
any events that fire within the tree - so you will be able to receive
all the clicks, mousedowns, etc.
Speaking of standard jquery code you will be able to manipulate with
the tree using a selector:
$("select > container + here").jstree("select_branch", "#phtml_1");
After a lot of thinking I decided not to drop all IE6 support, but to
package it out of the core - as a plugin. It will add some CSS
classes, some of the stuff won't work, but in the end after a bit of
performance loss IE6 users WILL get a functional tree, and users of
all OTHER browser will get a faster tree, which does not include IE6
specific fixes.
As a result of the major core rewrite and optimizations execution is
now a lot faster AND the filesize will be a lot less. (I have
reenabled most plugins and jstree core + plugins are now about 60K -
uncompressed and with quite a few comments). Whatever the changes from
here on I expect the final 1.0 version to be at least 20% smaller than
0.9.9a.
1.0 will depend on jQuery 1.4. I believe this to be not such a bad
move, as experience shows that new versions of jQuery are adopted
quickly. 1.0 utilizes the changes in the event system, along with
using some of the optimized functions.
Having this in mind - the final version of 1.0 will be available AFTER
jQuery 1.4 is released (sheduled for the 14th of January). Still, I
will release a public beta in early January. Then a RC after jQuery
1.4 has landed and hopefully a very stable and almost bug free 1.0-
final at the end of January.
Of course - this quality of the final version will depend on extensive
testing, which is why I am thinking of creating some test scripts, but
still - there is nothing more valuable than the test you guys do. So
thank you for all bug reports, ideas and feature requests - keep them
coming.
Kindest regards,
Ivan
Tom Wu
Best Regards
Tom Wu
--
You received this message because you are subscribed to the Google Groups "jsTree" group.
To post to this group, send email to jst...@googlegroups.com.
To unsubscribe from this group, send email to jstree+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/jstree?hl=en.
Roland Bock
sounds like I will need to do some rewrite, too, in order to use the new
version, but I am really looking forward to doing so! Sounds wonderful!
Faster, smaller, more flexible? Awesome!
I'll try to do some more work on the tree-table idea whenever the first
version is ready for testing.
Regards,
Roland
Chrazy
I'll get started with the testing as soon as the beta is out and do my
usual testing. :)
Gert Vrebos
oobi
While you're in there you might consider a small tweak to allow use of
the YUI compressor
Currently the use of "opts.static" in jquery.tree.js causes errors in
some JS compilers (including YUI). Changing that var to something else
or referencing it like opts["static"] fixes the prob. There are only 3
instances of it.
cheers
CC
jarrowwx
performance comparison before you commit to going down that path. In
some work I did, $.trigger() was very slow on FireFox under certain
circumstances, so it might be worth testing.
vakata
Already done :)
@jarrowwx
I noticed the same thing and am using triggerHandler instead, which
has some limitations but is very fast indeed :)
Cheers,
Ivan
John Arrowwood
I'm in process of building something, learning how to use your module. It looks like EVERYTHING is changing in the next release, so I was wondering if I could get a head start by just learning with the 1.0 beta?
Also, question for you: If the object that you pass in to represent a node of the tree is an instance of a class, and the properties are actually methods, will the tree handle that? For example, if data.title is a function, will it call it and use the return value? Especially 'children'. It would be awesome if children was a function that every time called returned the latest and greatest child nodes, in the right order. If it doesn't CURRENTLY do that, how hard would it be to MAKE it do that? :) Or is that best implemented as a plugin?
--
You received this message because you are subscribed to the Google Groups "jsTree" group.
To post to this group, send email to jst...@googlegroups.com.
To unsubscribe from this group, send email to jstree+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/jstree?hl=en.
--
John Arrowwood
John (at) Irie (dash) Inc (dot) com
John (at) Arrowwood Photography (dot) com
John (at) Hanlons Razor (dot) com
--
http://www.irie-inc.com/
http://arrowwood.blogspot.com/
vakata
no this is not currently possible, but it is a good idea - this calls
for a plugin :)
I will see what I can do.
Cheers,
Ivan
> > jstree+un...@googlegroups.com<jstree%2Bunsu...@googlegroups.com>
Patrick Wolf
Thanks for your hard work
Patrick
a2h
jQuery 1.4 rc1 has already landed
Chrazy
vakata
will be quite busy at work today, so I will shift all my efforts for
later tonight (or in the night).
Kindest regards,
Ivan
Maxime
You're doing an amazing job with the JsTree component. I just visited
your website today and noticed that you are just on the verge of
releasing version 1.0 which uses JQuery 1.4. Do you have an estimated
date when this will be released?
I would like to start some development, but if the new 1.0 version is
about to come out, I might be able to wait a little bit.
Kind Regards,
Max
vakata
setting and missing them, but I am really close so ... I guess the
fully functional beta will be out in max 3-4 days.
Kindest regards,
Ivan
Chrazy
It's good that you're taking time to make sure it's as bug-free as
possible. I guess others like me are just eager to get it since we (I)
can't upgrade to JQuery 1.4 until you're done.
Thibault D
I'll use it intensively in my CMS ( http://diem-project.org ), you can
rely on me to report all bugs I'll find.
Thanks a lot and keep up the good work!
Cheers
Thibault
TheCelavi
Thanks, cheers,
TheCelavi
On Jan 23, 12:44 am, Thibault D <thibault.duples...@gmail.com> wrote:
> I can't wait to see it :)
>
> I'll use it intensively in my CMS (http://diem-project.org), you can
Chrazy
problems at all since it's just a bug fix of v1.4.
Roel
Very nice project. I really like jsTree.
Is a new releasedate set for jsTree 1.0?
Because I'm pressured with my own deadline and want to use jquery
1.4.1.
Roel
I need the new jsTree because my own deadline is coming closer and I
can't change back to jquery 1.3.2 because of the usage of new
functions of jquery.
P.S.
Nice Job, your tree is by far the best tree out there!
Genius
v1.4.1 (at least drag-n-drop feature).
Do you or anybody else know what we can do to make a fast fix for the
current version of 0.9.9?
Thanks,
ibo ochen' nado ;)
vakata
Cheers,
Ivan
vakata
not all is working but the foundation is good and I will reenable
search/checkboxes/contextmenu/etc in a day or two. Also most of the
stuff is not throughly tested.