Printable View
Yeah dude, feel free to modify it as you see fit. As for the license, according to the Sencha licensing terms here, I'm pretty sure that my code stays MIT. That said I'm not a lawyer and frankly got bored reading that page after the first few paragraphs.Quote:
Originally Posted by toorshia
You're welcome--glad you have found it useful!Quote:
Originally Posted by netlogic
I haven't looked through all of your changes, but since you have posted this I've added the ability to dock the menu to either the right or left side (thanks largely to a patch submitted by a fellow user). I'm considering adding the ability to have dual menus.Quote:
Originally Posted by netlogic
If I understand what you are going for, I think you're going about it the wrong way. The plugin doesn't require that you have a toolbar in the main container--if you want one, it is up to you to add it. The ``slideButton`` configuration is there simply to make your life easier if you choose to use a toolbar by adding a button with open/close functionality into your toolbar for you. So, in summary, create a toolbar in your container/panel as you normally would, position the buttons there as you desire and then use the ``slideButton`` config to have the button automatically added.Quote:
Originally Posted by rhytha1
Hope that helps.
As it is implemented now, this isn't possible. A ``Ext.dataview.List`` is explicitly created, so it isn't possible to change it (at least not easily).Quote:
Originally Posted by ThiemNguyen
1st of all thanks for the component.
few question:
1. can caching of views be disabled by config?
2. how should I use this component to achieve the following approach:
every click on the list creates its view dynamically and destroys the last displayed one (for DOM performance)
3. how can I choose the view to be displayed when loading the component? I want item number 6 to be displayed with application startup instead of the first item. tried activeItem property but apparently its not the way
thanks!
No, not currently. You can, however, manually delete items from the cache by removing them from the ``_cache`` object.Quote:
Originally Posted by gkatz
I'd do this by listening to the ``select`` event. For example (this is totally untested):Quote:
Originally Posted by gkatz
Code:slidenav.on({
select: function(slidenav, newItem, index) {
Ext.Object.each(slidenav.container._cache, function(idx, item) {
if (idx != index) {
delete slidenav.container._cache[idx];
if (Ext.isFunction(item.destroy)) {
item.destroy();
}
}
});
}
});
Again, currently there isn't an "easy" way to do this (it's been on the todo list for awhile). The best way currently would probably to make a subclass of the slide view and overload the initialize function, where you can then manually define ``this.list.select(6)``. Alternatively, you might be able to get away with listening to the ``select`` event on the slide view and checking for the _init boolean--if it is ``false``, then you can return ``false`` from the listener and select the desired item instead.Quote:
Originally Posted by gkatz
Hope that helps.
This seems to do the job! Thanks for the input.Quote:
Originally Posted by wnielson
Thanks wnielson, the library is really good!
Just wanted to know, how can I add new container to the SlideOut Navigation at run time.
I added a function to get the instance of the navigation list to change title and stuff on the go.
My requirement is based on application activation, I want to add one more option to the list.
The driver of the menu is a store. So you will have to manipulate the store to change the shown menu. That shouldn't be to difficult...Quote:
Originally Posted by urmilsetia
I did that by adding a function to return the instance of list, however simply adding an item to list store won't added a referenced panel, will it?Quote:
Originally Posted by ingo.hefti