One of the most important organizational rules to follow is keeping what is known as your user interface and business logic separate. We haven't written any user interface logic yet, but we will in upcoming lessons. In this lesson we'll explore what user interface and business logics are, and what each handles.
Consider a basic calculator application. Its code falls into two categories: Code that performs calculations, or code responsible for interacting with the user.
The code that handles arithmetic is the back-end, or business logic. It's the 'inner workings' of the application that performs calculations and returns a value. It's what takes the numbers
5, adds them together, and arrives at
9. The functions we've explored so far are all back-end logic.
The code that handles interacting with user is the front-end or user interface logic. It retrieves information from the user and provides it to the business logic to calculate. While buttons on a calculator may be labeled with numbers, they're just visual buttons. User interface logic is what translates clicking on this area of the page:
... into the number
4. After all, we cannot perform addition on buttons, but you can perform addition on numbers. The user interface logic registers that the user has pushed the button labelled "4". It then provides the number
4 to the back-end logic where we may perform calculations with it.
Let's say we also press the buttons labelled "+" and "5". The user interface logic also translates these interactions into the number
5 and recognizes it will need a method for addition. The back-end logic then adds the numbers
5 together, and returns
9. The front-end/user interface logic can then display this result to the user:
User interface/front-end logic handles interacting with the user; including displaying or gathering information. The business/back-end logic handles calculating or manipulation information 'behind the scenes'.
Remember, we want to write clean, well-organized code. Because user interface and business logics have separate purposes, their code should always be separate. So far, we've only written business logic, so we don't have much to worry about. But keep this rule in mind as we begin to explore user interface logic with jQuery in the coming lessons.