March 13th in Code Organization Guidelines by . no comment .

How to Refactor a Mess into an Organized Web Application (Part 3: the Client Side)

In part 2 of the series, we organized the server-side of our vcard demo application. Today, we will be dealing with the client side: We will be progressively enhancing our initial application to get vcard data without refreshing the page; We will be strictly diving our application into four tiers; …

Continue Reading
March 4th in Code Organization Guidelines by . 2 comments .

How to Refactor a Mess into an Organized Web Application (Part 2: the Server Side)

Overview In the former post of our series, we started to refactor a simple vcard application, which initially was a total mess. In the first part, we defined a skeleton folder structure for our application; and we laid out the foundations of the BPC architecture. Where; Behavior/business logic (B) would …

Continue Reading
December 10th in Code Organization Guidelines by . 2 comments .

How to Refactor a Mess into an Organized Web Application (Part 1: the BPC Architecture)

This page has been translated into Spanish language by Maria Ramos. »» Cómo Refactorizar un enredo en una Aplicación Web Organizada (Parte 1: la Arquitectura BPC). In the former post I said that we would be refactoring chaos into order. This article is the next in the series; and here …

Continue Reading
December 4th in Code Organization Guidelines by . no comment .

How to Refactor a Mess into an Organized Web Application (Part 0: Teaser)

Ever found yourself as the front-end coder of a fat-client project, where the project has the following characteristics: The project has been going on for over for serveral years, The JavaScript is spread all over the place (I mean “all” over the place; inline, inside php snippets, within templates… here, …

Continue Reading
o2.js _
Fork Ribbon