Multiple Pages
Typically, whenever you move from one page to another page in a browser, the browser loses all state apart from the set cookies. This means that all JavaScript code, any DOM elements and ongoing animations are lost. This makes moving between pages slower than it could be.
This is solved in single page applications (SPA) using history.pushState. For instance, GMail allows the user to bookmark emails and use the navigation buttons (back and forward) while, technically, everything is going on on a single page. In this way, the user gets the best of two worlds, the speed of SPA and the expected behaviour of a multipage application. Starcounter has built in support for creating SPA applications that supports multiple pages.
Example
Let's assume that we have an email application. On the left is a list of all emails and on the right is a single focused email. You can use an URL to navigate to any particular email (i.e. /MultiplePagesDemo/emails/123). In this way, each particular email works as a separate web page. However, when you step between the emails in the list on the left, you don't want the browser to load a completely new page. This would make the email application slow and any DOM that is outside of the email page (i.e. the page inside the main page) would be reset.
In Starcounter, you can create master pages and sub pages that are handled on the browser side. In this way, the part of the master page that does not change between pages is actually the same DOM when you move in-between pages. The JavaScript instance is the same and any ongoing animations work fluently. Above all, performance is stellar.
Example source code
View-model
{
"Html": "/MultiplePagesDemo/views/MailsPage.html",
"Mails": [
{
"Title": "",
"Url": ""
}
],
"Focused": {}
}The Mails element is used to display a list with links to their corresponding email. The Focused element is filled with a single Focused.json.
{
"Html": "/MultiplePagesDemo/views/Focused.html",
"Title": "",
"Content": ""
}The Focused.json has its own Html file which will be inserted into the MailsPage in a SPA manner.
Application Code
using Starcounter;
using System.Linq;
namespace MultiplePagesDemo
{
[Database]
public class Mail
{
public string Title { get; set; }
public string Content { get; set; }
public string Url =>
"/MultiplePagesDemo/mails/" + this.GetObjectID();
}
public class Program
{
static void Main()
{
Application.Current.Use(new HtmlFromJsonProvider());
Application.Current.Use(
new PartialToStandaloneHtmlProvider());
Handle.GET("/MultiplePagesDemo/mails", () =>
{
if (Session.Current != null)
{
return Session.Current.Data;
}
Session.Current =
new Session(SessionOptions.PatchVersioning);
var mailPage = new MailsPage()
{
Session = Session.Current,
Mails = Db.SQL<Mail>(
"SELECT m FROM MultiplePagesDemo.Mail m")
};
var focused = new Focused()
{
Data = mailPage.Mails.FirstOrDefault().Data
};
mailPage.Focused = focused;
return mailPage;
});
Handle.GET("/multiplepagesdemo/mails/{?}", (string id) =>
{
var mail = Db.SQL<Mail>(
"SELECT m FROM mail m WHERE objectid=?", id)
.FirstOrDefault();
var mailsPage = Self.GET<MailsPage>(
"/multiplepagesdemo/mails");
mailsPage.Focused.Data = mail;
return mailsPage;
});
Db.Transact(() =>
{
var mails = Db.SQL<Mail>(
"SELECT m FROM Mail m");
if (mails.FirstOrDefault() == null)
{
new Mail()
{
Title = "Hello Mail",
Content = "This is my first email!"
};
new Mail()
{
Title = "Greetings",
Content = "How are you? Regards jack"
};
}
});
}
}
}The program defines two Handle.GET operations. One to retrieve the master, MailsPage, and the other to retrieve specific emails.
The first, Handle.GET("/MultiplePagesDemo/mails"..., returns the master json MailsPage. It checks if there is a current session and if so uses it instead of creating a new. It uses the first mail, if any, as the focused mail.
The second, Handle.GET("/multiplepagesdemo/mails/{?}"..., returns a MailsPage as well. It does however specify which email should be focused. By relying on Self.GET we call the first handler which includes the functionality to check for exisiting sessions.
View
<link rel="import" href="/sys/polymer/polymer.html">
<template>
<template is="dom-bind">
<h3>{{model.Title}}</h3>
<hr />
<article>{{model.Content}}</article>
</template>
</template>The Focused.html referenced by Focused.json simply displays the title and content of a email stored in Focused.json. It does not have to care about the rest of the page and would work even as a stand-alone page.
<link rel="import" href="/sys/polymer/polymer.html" />
<template>
<style>
.multiplepagesdemo-content {
display: flex;
}
.multiplepagesdemo-content__item {
flex: 1;
border: solid;
padding: 10px;
}
</style>
<template is="dom-bind">
<h1>MAIL CLIENT</h1>
<div class="multiplepagesdemo-content">
<div class="multiplepagesdemo-content__item">
<h5>Mails</h5>
<hr />
<ul>
<template is="dom-repeat" items="{{model.Mails}}">
<li>
<a href="{{item.Url}}">{{item.Title}}</a>
</li>
</template>
</ul>
</div>
<div class="multiplepagesdemo-content__item">
<h5>Mail Content</h5>
<hr />
<div>
<template is="imported-template" model="{{model.Focused}}" content$="{{model.Focused.Html}}">
</template>
</div>
</div>
</div>
</template>
</template>MailsPage.html contains the full page to display. It lists all the mails as linked text. The most important part is the <template is="imported-template" which loads the Focused element of MailsPage.json with its own html file.
How it Works
When a client visits /MultiplePagesDemo/mails the system will create a session and return the MailsPage.json. When a user then clicks on a specific mail the system will retrieve the MailsPage.json once again but as the client already has it cached there is no need to send it again and the page will not reload. The only differing element, Focused, will just be replaced.
This works just as well if a client is directly accessing a specific mail using it's URL. This means that a client can bookmark specific mails without any problems as if it were a multiple pages application.
Last updated