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

**(True or False)** Triggering routing events and updating the URL are the same thing.


(True or False) Triggering routing events and updating the URL are the same thing.

Doesn't need any router to be instantiated

Only once *all* routers have been instantiated

Even when *one* router has been instantiated, to ensure no routing events get lost


When should Backbone’s routing be started via a `Backbone.history.start()` call?

When should Backbone’s routing be started via a <code>Backbone.history.start()</code> call?

The server doesn't necessarily need to respond to the URL, it should only send the application to the client.

There is no prerequisite required, the pushState functionality doesn't need any.

The server must respond to the URL and send the application to the client. 

What is the prerequisite to using the pushState functionality in your application (via `Backbone.history.start({pushState: true})`)?

What is the prerequisite to using the pushState functionality in your application (via <code>Backbone.history.start({pushState: true})</code>)?

It encourages bad app design. However, it enforces a proper separation of app behavior but not of URL management.

The back and forward buttons do not work while the URL still works.

It encourages bad app design since the proper separation of app behavior and URL management is no longer enforced.

 Why is it not recommended to set `trigger: true` when calling `Backbone.history.navigate.()`?

Why is it not recommended to set <code>trigger: true</code> when calling <code>Backbone.history.navigate.()</code>?

**(True or False)** All views in a web app require a routable URL.

(True or False) All views in a web app require a routable URL.

Implementing Routing

Implementing Routing

Check your understanding of implementing routing.


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: Implementing Routing