Creating a Custom Ext JS State Provider

In this article we will review how you can save the state of your Ext JS components on the server side. Let me give you an example so you can understand what this feature allows you to do.

Suppose that you created an Ext JS application where one of the screens renders an Ext JS grid with a set of records. You have set up this grid so the application’s users can sort, rearrange, hide or show grid columns as needed. And you want that when any user runs the app, the app remembers which columns of the grid were visible, what was the order of the columns, and how the grid was sorted the previous time the user ran the app, regardless of whether it was run on the same or a different computer or mobile device.

grid-stateful-1

Having an app that remembers the state of its UI for a given user makes users feel like the app is working for them and not the other way around. This feature is particularly important in large applications with complex user interfaces. It avoids frustration and saves users time by not having to rearrange user interface components every time they go in the app.

To illustrate this feature we will create a small sample application with an Ext JS grid that displays data related to a hypothetical model cars collection. We will give the grid the ability to save the state of its columns (visible or invisible, column order and sort) to the server, as well as load this state from the server when the application is launched.

Continue Reading →

Using Postman to Test an Express.js Router for a Mobile Application Endpoint

In this article we will implement and test the server-side endpoints that will route the user registration and user authentication HTTP requests from a meeting room booking mobile application. The endpoints will route these requests to the Node.js Controller module that we built and tested in the previous article of this series.

featured-2

This article is part of a series of mobile application development tutorials that I have been publishing on my blog MiamiCoder.com. In this series we are creating a Meeting Room Booking mobile application that has a Node.js and MongoDB backend.

In the preceding chapters we designed the user registration, logon and password reset screens of the mobile application. We also implemented and tested the Node.js Controller module that will provide the registration, logon and password reset services on the server side.

In this article we will create the router module that connects the HTTP requests triggered by the screens in the mobile application to the server-side controller. We are going to use the routing facilities of the Express Framework to create this router module, and we will be using Postman to test the router.

Continue Reading →

Ext JS Grid Search with .NET and MySQL Backend

Building a “live” search feature for an Ext JS Grid is pretty simple. This tutorial shows you an example of how to set up this search feature for an Ext JS Grid that is connected to a .NET and MySQL backend.

The Ext JS application that we will build in this article has a Grid that displays data about the albums of a hypothetical music collection. A search box in the Grid’s Toolbar will allow users to filter the albums by title or artist. As a user types in the search box, the Grid will pull filtered data from the server:

grid-search-1

Continue Reading →

Mocha and Node JS – Testing the Backend for a Mobile Application

This Mocha and Node JS tutorial shows you how to test a Node.js and MongoDB backend for a mobile application. This article is part of a series of mobile application development tutorials that I have been publishing on my blog MiamiCoder.com, where we are creating a Meeting Room Booking mobile application with a Node.js and MongoDB backend.

featured-1

In the previous article of this series, we built the server-side AccountController module that will handle the user registration, login and logout features of the application. We implemented the AccountController’s public interface, along with a number of helper Classes that will allow the Controller to do its work. Our goal for this article is to create a set of unit tests for the Controller’s public interface (public methods) that will prevent us from breaking the application if we need to refactor the Controller in the future.

Continue Reading →