October 17, 2012 at 14:20

Video of the report “All the salt of single-page applications” with 404fest

    Fedya Shumov and Arseniy Zarechnev, front-end developers from the Ostrovka team , talked about the
    “All salt of one-page applications” at 404fest in Samara.

    Report Content:



    Single-Page Apps. All the salt.
    1. Backbone.js
    2. MVC on the client
    3. JS Testing
    4. Model-View Bindings
    5. Lighting Batman.js

    Extranet.Ostrovok.ru (administration system for hotels). The most salty.
    1. Navigation and management through the address bar. Loosely connected router events. Caching payloads from the requested URL.
    2. DOM related data. Expando Do not clog the namespace with temporary or other people's data. Using third-party libraries using this technology.
    3. The view is built 1 time. When leaving for another page, it is torn out through Parent.removeChild (Child) or jQuery.detach () and lives with binders. When re-accessed, it is inserted assembled.
    4. Refusal of Delegate. The increase in speed due to the lack of event listeners on the parent view element.
    5. Knockout Clear logic of the template. Auto change UI. Changes in the DOM of only those attributes and elements that really require it. Secure interface. Multiuser mode.
    6. Backbone + Knockout = Router + CRUD + MVVM. Two-way dependency: methods for changing the model of each framework synchronize related objects and trigger the necessary events from each other. Gradual transition from Backbone to Knockout views.
    7. Pages that work with really large collections and models may require deep optimization. For example, abandon $ .extend or _.extend, which actively use models and collections of frameworks during initialization, to break the bundle in memory.




    The presentation of the report can be found here: Arseny Zarechnev and Fedor Shumov - One-Page Applications
    Tags:

    Also popular now: