Re: [SMARTY] my second plugin! :)
| From: | Mitch Vincent | Date: | Wed, 05 Jun 2002 03:50:37 +0000 |
| Subject: | Re: [SMARTY] my second plugin! :) | ||
| References: | 1 | Groups: | php.smarty.general |
| Request: | Send a blank email to php-smarty-general+get-4599@lists.php.net to get a copy of this message | ||
> but I'm the only designer/developer on the page, so ... besides which,
> in any of the places I've worked, we've never had designers that did
> HTML - they did the graphics, and we (the programmers) did the HTML
> and the programming ... unless you were working on the next microsoft.com,
> I don't know why you'd want to have different guys doing the HTML and the
> programming? at least I've never worked on any site that big, and frankly
> I hope I never will ;)
MVC can be used with anything -- even a one page deal. Imagine if you didn't
have to kludge through PHP code to make a layout change.. Non-PHP
programmers can make changes to dynamic web pages without a risk of fscking
everything up!
I'm not a designer. I'm not a graphics guy, don't enjoy doing layout and
would rather walk on red-hot coals than fuss with HTML to get things looking
right. *grin*
IMHO any well designed web shop is not going to have their PHP programmers
designing web pages or the layouts and graphics for web apps :-)
I mean no offense, perhaps you're a design whiz and a PHP whiz but I've
never met someone that went both ways and was very good at either.. I'm
certainly not good at design.
> to me, it's usefulness lies in the integration of the roles - I can now
> do the "programming" (queries, sending mail) without really programming
> at all, and I have exactly the separation I want: if I wanted to switch
> to a different email system or another database, I could do so simply by
> altering my plugins.
What I'm doing right now is an excellent example of why MVC is awesome. I'm
writing a web based inventory/order entry/POS application 3000 miles away
from the guys designing the site. They can design the whole thing, I can
write all the backend code and we never need to speak anymore than to allow
me to tell them what the variable names are. I get to concentrate on what I
do best (PHP programming) -- they get to concentrate on what they do best
(designing!)
Another cool thing about using MVC methodology is that they can totally
redesign the look of the site and the designers NEVER have to call me!!!
I use MVC with everything from the smallest one-day eCommerce site (one day
because I can work independent of the designers!) to large web applications
like my current project. In the end is easier to maintain and change --
there is total separation of presentation and backend logic so that a layout
change doesn't interfere with the inner workings of the application.
> severing the function calls from the template would not simplify things,
> not for me - quite the contrary. I use Smarty for componentizing not
> just HTML, but also functionality - you may not like that, and I'm very
> aware that it's far from "by the book", but if it works, it works :)
I don't think anyone is trying to tell you how to do things -- just
suggesting the path that the authors of Smarty had in mind when they came up
with it.. If you don't want to use MVC, by all means -- don't :-)
-Mitch