Smarty Forum Index Smarty
The discussions here are for Smarty, a template engine for the PHP programming language.
Which one to get first, Design or Coding?

 
Post new topic   Reply to topic    Smarty Forum Index -> Article Discussions
View previous topic :: View next topic  
Author Message
bimal
Smarty Elite


Joined: 19 Apr 2007
Posts: 420
Location: Kathmandu, Nepal

PostPosted: Sun Sep 06, 2009 2:10 pm    Post subject: Which one to get first, Design or Coding? Reply with quote

This may be a simple confusion for most of us. Coders fight for having a project’s designs and html slices earlier than they can start coding. While, designers may not be available immediately, and investor may still keep on thinking about the website’s layouts.

So, should the coding stop and wait for the designs? Not necessary! If you have your manager analyze the system well, and thinking Smarty in mind, you can go coding without having a project’s designs. But you just have to limit to the basic functionalities of your web application. You can continue working on the coding parts that you have to do, even after receiving the project's design and html slices.

HTML Slices basically consist of images, html codes, CSS and JavaScripts, and sometimes, few embedded objects (video players, document readers, and java applets).

Instruct your designer to externalize the CSS and JavaScripts, as much as possible. (These files should not be used within a webpage, but in different files). Due to the special default delimiters used in Smarty ( { and } ), you should avoid writing these characters in an html file. CSS and JavaScripts contain these characters too frequently.

If coding starts earlier than the slices, it is the coder’s responsibilities to use the HTML IDs, and Classes correctly and explaining them to the designer later on. So, the designer can replace them accurately in the html slices.

If the manager is controlling the coding and designing, s/he can instruct both of them on how to use the name conventions code blocks, and help shape a project without hiccups. When there is a time to mix up the Smarty Templates and Designer’s work, it becomes easy. Plus, you can think of reusable parent templates and components of a template to minimize the time efforts.

Hence, properly organized templating and coding habit does not have to invite a battle between a designer and coder, who should work first.
Back to top
View user's profile Send private message Visit poster's website AIM Address Yahoo Messenger MSN Messenger
bimal
Smarty Elite


Joined: 19 Apr 2007
Posts: 420
Location: Kathmandu, Nepal

PostPosted: Sun Sep 06, 2009 3:37 pm    Post subject: Smoothen the development process Reply with quote

Plus, please read out this article as well:
http://www.phpriot.com/articles/application-logic-vs-template-logic

The author, Quentin Zervaas, has briefly noted some possible ways to see differences in Application Logic and Template Logic. If a designer is clear about the Template Logic, it is a very good thing.

The development process smoothens.
Back to top
View user's profile Send private message Visit poster's website AIM Address Yahoo Messenger MSN Messenger
Display posts from previous:   
Post new topic   Reply to topic    Smarty Forum Index -> Article Discussions All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group
Protected by Anti-Spam ACP