v.0.9.9b on its way - not sure if this is a bad or good thing - bug list

[vakata]

Hi everyone,

It turns out I was too excited about the new features and a few bugs
were found even in 0.9.9a.
I am terribly sorry, but on the other hand - this rapid bug reporting/
fixing really pushes jsTree forward.

Thank you for your patience!

As the fixes are minor all using 0.9.9 and 0.9.9a will be able to
transparently upgrade to 0.9.9b when it is released.
Here are the fixed in 0.9.9b so far:

fixed theme_path bug (if setting was used it caused no theme to
load)
fixed Ctrl+Click on Mac
fixed type icons in IE7 (now they work in IE7)
multitree bug (Array conversion) fixed
fixed drag helper images not showing when using custom icon image
in data
still working on checkbox plugin enhancement - rebuild state (if
three-state) on move/copy/create/delete
still waiting on further info about two reported bugs that I cannot
reproduce
will install ubuntu today and possibly fix context menu not showing
issue

Once again - thank you all!

[koo9]

can't wait for 0.9.9b come out! good job!

[vakata]

UPDATE:

all callbacks are fired within the tree scope (this is a reference
to the tree instance)
added _create, _rename, _remove, _load_branch
changed oncreate, onrename, onremove callbacks
static becomes staticData
fixed oncreate callback to fire AFTER the node is renamed
fixed JSON datastore get method
fixed multilanguage in IE8
context menu plugin - removed flicker on two consecutive right
clicks
added repair function to checkbox plugin to handle move/copy/create/
delete

[Smart Kenny]

vakata:

Could you please at least paste the diff file for fixing the theme
path bug? I really need to use theme path in my project now. Thank you
very much.

And I am also curious about how the svn is used in jstree. I think
branching and tagging can help a lot on managing the codes.

[Brian]

Any idea when these changes are going to be released?

[Chrazy]

Are you still planning on releasing a 0.9.9b or will you go straight
to 1.0?

[vakata]

Hi,

1) I will most likely be migrating to github and utilizing the
wonderful branching functionality, so - yes - there will be a branch
for each release that will be updated only with hotfixes and a DEV
branch for the work in progress

2) I will be moving straight to 1.0 and I hope to have it ready by the
end of next week, I just started cleaning it up again.

Cheers,
Ivan

[Andy]

Hi Ivan,
thank you for your excellent work! After comparing various tree
plugins for jQuery I found yours to be the best one. However, the
issue with anchors stands in the way. Somewhere in this group you
stated that 1.0 will remove the issue, so I'm looking forward to the
release. Are there any more or less reliable estimates? Is there some
alpha- or beta-quality code available, or the API is still unstable?

Thanks again!
Andy

[Jeff Chan]

On Oct 8, 6:38 pm, vakata <ivan.bozha...@gmail.com> wrote:
> UPDATE:

>
>    fixed oncreate callback to fire AFTER the node is renamed

Hi there, please make sure "onrename" is still fired to provide
backward compatibility.
My reason is that people like me implementing an ajax sync for every
action to the remote database now depends on this. Otherwise, lots of
us will have to update the "oncreate" handler to include the "node
name" in the AJAX call. Thanks!

[vakata]

Hi,

I am still heavily modifying the code each day - so it is not yet
stable, nor backward compatible - the reason I am not commiting is
that it is TOO unstable and will most likely be changed further. It
would be a waste of time for anyone to try and figure the new code
out, because it is changing rapidly.

I will think of a backward compatibility - thank you for noticing.

Cheers,
Ivan