GitHub user robertkowalski opened a pull request:

    https://github.com/apache/couchdb-fauxton/pull/279

    Remove raf

    Garren and me tried to use the latest layoutmanager in summer
    2014 - the experiment lead to performance improvements regarding
    the rendering of our application, but we had to disable it as we
    as it lead to timing issues.
    
    As we are moving to React it does not make sense to me to invest
    further time into the issues we had in summer.
    
    This commit removes the leftovers of the experiment that are not
    needed any more and cleans up.
    
    See apache#29

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/robertkowalski/couchdb-fauxton remove-raf

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/couchdb-fauxton/pull/279.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #279
    
----
commit afc3ed6032b96b00312f5488ad5488c469ba0d5c
Author: Robert Kowalski <[email protected]>
Date:   2015-02-20T13:12:35Z

    [email protected]
    
    src: 
https://raw.githubusercontent.com/tbranyen/backbone.layoutmanager/0.9.5/backbone.layoutmanager.js

commit f7dec4064bfafe45faa19b4dfee1b3dd64d24dbe
Author: Robert Kowalski <[email protected]>
Date:   2015-02-20T13:14:56Z

    cleanup: remove useRAF leftovers
    
    Garren and me tried to use the latest layoutmanager in summer
    2014 - the experiment lead to performance improvements regarding
    the rendering of our application, but we had to disable it as we
    as it lead to timing issues.
    
    As we are moving to React it does not make sense to me to invest
    further time into the issues we had in summer.
    
    This commit removes the leftovers of the experiment that are not
    needed any more and cleans up.
    
    See https://github.com/apache/couchdb-fauxton/pull/29

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to