-
6 Feb 2013 4:14 PM #161
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.
-
6 Feb 2013 4:19 PM #162
You're welcome--glad you have found it useful!
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.
-
6 Feb 2013 4:27 PM #163
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.
Hope that helps.
-
6 Feb 2013 4:30 PM #164
-
13 Feb 2013 4:14 AM #165
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!
-
13 Feb 2013 10:06 AM #166
No, not currently. You can, however, manually delete items from the cache by removing them from the ``_cache`` object.
I'd do this by listening to the ``select`` event. For example (this is totally untested):
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.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(); } } }); } });
Hope that helps.
-
15 Feb 2013 5:27 AM #167
-
17 Feb 2013 1:46 AM #168
Awesome Lib.
Awesome Lib.
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.
-
17 Feb 2013 5:53 AM #169
-
17 Feb 2013 6:21 AM #170




Reply With Quote