1. #91
    Sencha Premium Member lorezyra's Avatar
    Join Date
    Dec 2007
    Location
    Japan -- 日本
    Posts
    634
    Vote Rating
    13
    lorezyra will become famous soon enough lorezyra will become famous soon enough

      0  

    Default


    //I agree, can we push this for consideration at Sencha?
    vote++;
    Perfection as a goal is a nice idea that can point one in a specific direction. However, since "perfection" is an ever changing (evolving?) and moving target, one must admit that perfection can never be obtained...

    When in doubt, check the d4mn source code!
    ================================================
    And here are my terms...
    1. I don't care if you use my source code. (Known as "Code.")
    2. I don't care if I get any monetary compensation.
    3. I do care to receive credit for Code provided. So, please keep my name in the comments for Code provided.
    4. Code is provided without warranty "AS-IS" and I claim absolutely no warranty nor liability to the quality, security, and run-ability on any platform.
    5. By using Code, you accept all risk inherit with Code regardless if Code has known and yet to be discovered bugs.
    6. You are welcome to change and improve the Code to best meet your needs.
    7. I don't care if you use the Code in a commercial or open-source project.
    8. You are not required to contact me prior to using the Code.
    ================================================
    Simple. Enjoy.

  2. #92
    Sencha User eirik.lorentsen's Avatar
    Join Date
    Aug 2011
    Location
    Santiago, Chile
    Posts
    33
    Vote Rating
    7
    eirik.lorentsen is on a distinguished road

      0  

    Default


    Quote Originally Posted by devtig View Post
    I think replacing all instances of me.hide() with me.close() in the code is the way to improve it (I haven't tried it). The default closeAction of a window is destroy. So, when you close() a window, the instance is destroyed.

    I don't know either why hide is being used.
    If I understand it right, then close() is just an alias for hide() or destroy(), depending on what closeAction is set to. In previous versions I always destroyed the Notifications, but in the last version I changed the behavior. The default closeAction of a window is 'destroy', but it can also be set to 'hide' if reusing the window is desirable. The latest changes I made make it possible to reuse a notification object the same way.

    For example if you check out the latest demo (http://www.eirik.net/Ext/ux/window/Notification.html) there is a button that says "BR - reuse". This shows the reuse of the component and the dom. A nice side effect in the example is that this automatically restricts the number of notifications to only one.

    And the script actually does not call hide() more than once. From inside the overridden destroy() function. The reason for this is to make sure the notification fades out with an animation not only when the script closes it after the delay (autoClose), but also when the close button in the top right hand corner is clicked. There might be a way of achieving this without touching the destroy() function, but I felt it made sense to always hide the notification with the animation before it is destroyed.

    After the hide animation is finished a new call is made to destroy() and the second time around a call is made to me.callParent(arguments) inside destroy(). So I am under the impression that this means all other destruction that windows normally perform will take place. The dom certainly is destroyed and I figured that was mostly what the destroy() functions did in Ext (take down the related dom). If there is a memory leak caused by the overriding of the destroy() function, then maybe that is because something else, like a pointer or circualar reference, should also be destroyed before exiting the overridden destroy() function. But since hide() calls removeFromManager(), then I can't imagine where those pointers are.

    When it comes to memory management I'm on thin ice. Both JS and Ext wise. So maybe somebody could help out with some more insight? Or simply tell me a procedure I could use to test/visualize the leak, providing me a way to debug it.

  3. #93
    Sencha User eirik.lorentsen's Avatar
    Join Date
    Aug 2011
    Location
    Santiago, Chile
    Posts
    33
    Vote Rating
    7
    eirik.lorentsen is on a distinguished road

      0  

    Default


    Quote Originally Posted by lorezyra View Post
    //I agree, can we push this for consideration at Sencha?
    vote++;
    Great idea. I wouldn't mind at all!

  4. #94
    Sencha User eirik.lorentsen's Avatar
    Join Date
    Aug 2011
    Location
    Santiago, Chile
    Posts
    33
    Vote Rating
    7
    eirik.lorentsen is on a distinguished road

      0  

    Default


    Quote Originally Posted by jonathan999 View Post
    I need to use this for my application.
    can you please explain how to use it after the notification.js file is downloaded and included in the application.

    br,
    jonathan
    View the source from the demo page:
    http://www.eirik.net/Ext/ux/window/Notification.html

  5. #95
    Sencha User
    Join Date
    Jan 2008
    Location
    Levittown, PA
    Posts
    316
    Vote Rating
    2
    mjhaston is on a distinguished road

      0  

    Default


    Great extension. I apologize if this was noted already, but how do I make a notification stick until it's manually closed or I close it programatically?

    Thanks.

  6. #96
    Sencha User eirik.lorentsen's Avatar
    Join Date
    Aug 2011
    Location
    Santiago, Chile
    Posts
    33
    Vote Rating
    7
    eirik.lorentsen is on a distinguished road

      0  

    Default


    Pass the following parameter to the constructor and the notification will not go anywhere:
    autoClose: false


    Quote Originally Posted by mjhaston View Post
    Great extension. I apologize if this was noted already, but how do I make a notification stick until it's manually closed or I close it programatically?

    Thanks.

  7. #97
    Ext JS Premium Member
    Join Date
    Jan 2008
    Posts
    378
    Vote Rating
    2
    silcreval is on a distinguished road

      0  

    Default Stop notifications from stacking up

    Stop notifications from stacking up


    Is there a way to either reuse or prevent multiple notifications appearing (that are the same)?

  8. #98
    Sencha User eirik.lorentsen's Avatar
    Join Date
    Aug 2011
    Location
    Santiago, Chile
    Posts
    33
    Vote Rating
    7
    eirik.lorentsen is on a distinguished road

      0  

    Default


    Quote Originally Posted by silcreval View Post
    Is there a way to either reuse or prevent multiple notifications appearing (that are the same)?
    Yes. In the demo there is a button called "BR - reuse" demonstrating exactly how to do this.

    In short you store the pointer to the notification when you create it. This can be done in advance as long as you don't call the show() immediately. And then you only call update/show every time you want to notify something. If the notification is still visible when the next updtae/show is called then all that happens is an update of the notification's content.

  9. #99
    Sencha User
    Join Date
    Nov 2011
    Posts
    2
    Vote Rating
    0
    Refus is on a distinguished road

      0  

    Default


    in 4.2 fails to destroy the component.
    so it works again:

    Code:
     hide: function () {
            var me = this;
            // Avoids restarting the last animation on an element already underway with its hide animation
            if (!me.isHiding && me.el) {
    
    
                me.isHiding = true;
    
    
                me.cancelAutoClose();
                me.stopAnimation();
    
    
                me.el.animate({
                    to: {
                        opacity: 0
                    },
                    easing: 'easeIn',
                    duration: me.hideDuration,
                    dynamic: false,
                    listeners: {
                        afteranimate: function () {
                            me.removeFromManager();
                            me.readyToHide = true;
                            if(!me.destroying){
                                me.hide(me.animateTarget, me.doClose, me);}
                        }
                    }
                });
            }
      ...

  10. #100
    Sencha User wemerson.januario's Avatar
    Join Date
    Nov 2008
    Location
    Brazil, Goias, Goiânia
    Posts
    427
    Vote Rating
    6
    wemerson.januario is on a distinguished road

      1  

    Default


    Animation fails in ExtJS 4.2.1 beta 1
    Wemerson Januario
    Twitter:
    @wemersonjanuar
    Skype:
    wemerson.januario
    Email: wemerson.januario@gmail.com
    Fone:
    62 9106-6689
    From: Goiânia, Brazil
    Desenvolvedor ExtJS/ ExtJS Developer

Turkiyenin en sevilen filmlerinin yer aldigi xnxx internet sitemiz olan ve porn sex tarzi bir site olan mobil porno izle sitemiz gercekten dillere destan bir durumda herkesin sevdigi bir site olarak tarihe gececege benziyor. Sitenin en belirgin ozelliklerinden birisi de Turkiyede gercekten kaliteli ve muntazam, duzenli porno izle siteleri olmamasidir. Bu yuzden iste. Ayrica en net goruntu kalitesine sahip adresinde yayinlanmaktadir. Mesela diğer sitelerimizden bahsedecek olursak, en iyi hd porno video arşivine sahip bir siteyiz. "The Best anal porn videos and slut anus, big asses movies set..." hd porno faketaxi