Delve into Marionette.js for building JavaScript applications. Gain insights into class objects, views, templates, event handling, collections, routing, and web storage for interactive client-server development.

Backbone.Marionette.js- A Gentle Introduction.png

myapp.tar.gz

marionette_app

run_index

run_index_appjs

run_app_index_contact

run_app_contact_list

run_app_contact_list-copy

run_app_contact_list-template

run_app_contact_list-show

run_app_router

run_app_common_view

run_app_edit

run_app_new_view

run_app_AboutApp

run_app_HeaderSubApp

run_app_HeaderSubApp-list

marionette_app-copy

Marionette is an extension of Backbone that is very popular in building various JavaScript applications with a client-server system. It introduces a method for creating applications where you can define a class object that handles the entire application and acts as its root. 

You’ll learn the differences between views and templates. Next, you will cover displaying a model with a default value and use events to generate alerts. Then you’ll cover collectionView and CompositeView, to list contacts and display the column headers on the application’s main page, respectively. You will also learn to add routing to an application for quick navigation and implement web storage persistence. Then, you will learn how to add navigation and highlight menu items on the application’s main page.

This course will help you build highly interactive JavaScript applications as a web developer. It will further empower you to develop your applications by understanding Marionette.

Introduction to Marionette.js – The Backbone Framework

**(Fill in the blank.)** According to the ________, the edit view shouldn't be used to create new contacts.

(Fill in the blank.) According to the ________, the edit view shouldn’t be used to create new contacts.

**(True or False)** We use a `triggers` hash to make Marionette match an event selector with an event to trigger.

(True or False) We use a <code>triggers</code> hash to make Marionette match an event selector with an event to trigger.

We use a different form template that doesn't require attributes.

We check for the attributes within the template.

We set the required attributes on our new contact before instantiating the view.

How can we solve the problem where an empty object behaves as a contact model instance?

How can we solve the problem where an empty object behaves as a contact model instance?

A `layoutView` can also act as a composite view to aggregate multiple views and sub-application areas of the screen, allowing applications to attach multiple region managers to dynamically rendered HTML.



A <code>layoutView</code> can also act as a composite view to aggregate multiple views and sub-application areas of the screen, allowing applications to attach multiple region managers to dynamically rendered HTML.

Which function defined by the `Collection` views is used to determine how child views should be added to their container?

Which function defined by the <code>Collection</code> views is used to determine how child views should be added to their container?

Complex Views and Base Views

Complex Views and Base Views

Check your understanding of complex and base views.

Introduction

Displaying a Static View

Displaying a Model

Displaying a Collection of Models

Structuring Code with Modules

Creating Tables in Views

Events, Bubbling, and TriggerMethod

Displaying Contacts in Dedicated Views

Implementing Routing

Dealing with Persisted Data

Handling Data Latency

Managing Forms

Displaying a Modal Window

Complex Views and Base Views

Managing Dialogs with a Dedicated Region

Filtering Contacts

Addition to Sub-Application

Conclusion

Appendix: Using Web Storage for Persistence

Appendix: Creating a FilteredCollection

Quiz: Complex Views and Base Views