I checked in some changes over the past few days to support both horizontal menus (aka MenuBar) and vertical menus statically appearing on a page, rather than popping up. i.e., menus that are always visible.
Give it a whirl. For now, see the test_Menu.html test file for a demo. (Eventually we'll get the demos into the new doc.)
A week or two ago I checked in a bunch of updates to ContentPane. The goal was to make "hidden" initialization work better, i.e., if a TabContainer had a ContentPane with some markup, including some widgets like Grid or Editor that won't initialize correctly when hidden.
The original plan was to use visibility:hidden rather than display:none, but that proved problematic on IE.
Dojo 1.2 has a lot of great new features. There are two in dijit I'd like to (very briefly) mention:
The first is all the look-and-feel improvements. We've changed colors, margins, etc. to make things look better, and look/work more like users expect, and perhaps mainly we've fixed a bunch of visual glitches There were almost 100 things fixed with visual issues with the widgets.
Now that we're on the verge of releasing Dojo 1.2, it seems like a strange time to talk about the next release,
but I want to anyway :-)... I won't be at this year's DDD so I want to get people's feedback virtually about future Dijit development...
Dojo 1.2 will sport a nice API standardization for widgets. Widget.attr() is now the standard interface for setting/getting all widget attributes. For example:
// set title
myTitlePane.attr('title', 'hello world');
// find out if button is disabled
var dis = myButton.attr('disabled');
// set to the current date
myDateTextBox.attr('value', new Date());
It also supports a hash API like dojo.attr(), for setting multiple attributes:
myInput.attr({ tabIndex: 3, disabled: true, value: 'hi'});
We've released Dojo 1.1 beta, on the download site. It incorporates a bunch of bug fixes from beta2, and is another step closer to our release...
We're expecting to do a release candidate soon (maybe in a week?) so this is really the time to help us test the beta and see if there are any new bugs not already listed in the bug database, or bugs that we marked as fixed but really aren't.
I've done some work on dijit.Tree since my last blog post. (These changes that went into the 1.1 beta 2 release.) Basically, decided that it was too difficult to force everyone to present a dojo.data model for the tree's data, especially w.r.t how to query the children items (and getting notifications about changes to the children items).
In version 1.1 I've fixed the Tree architecture to be able to handle DnD correctly. I've had to deprecate (not remove) some version 1.0 APIs because they didn't work with DnD, and I've listed them here, along with some general discussion about what it means for a tree to connect to a data store. Hopefully some will find it useful.
Hi everyone, I hope you've all had a good Thanksgiving (if you are in that part of the world).
Now that 1.0.1 is out the door, it's time to look forward to the 1.1 release and beyond. I'd like to do this for all of dojo but I can't boil this ocean, so I'm looking at dijit. I've gone over all the bugs against dijit, and especially the bugs marked for 1.1.
Many months ago I posted a widget wish list request to my blog. The response was overwhelming. I'm sorry I haven't gotten a chance to respond to that thread (until now).
