Smarty

[arne_anka]

hi,
i only just begun to dig into smarty and the question occured to me how to design a bigger smarty-based application.
having one big single php-script serving all requests and delivering different templates seems no really good idea. on the other hand even creating another smarty-object in every php-script/-class called seems not really best practice. the examples i found are very small and thus not really helpfull.

assume an application in the style of the old netscape-configuration-menu:
to the left a long menu with items and to the right depending on the item choosen one or more forms separated into tabs which are used to insert/change/maintain data of different kind and for different purposes which require several different php-classes.

how would one designt that application best to prevent unnecessary wasting of resources?

[shannera]

I use one base script with smarty configuration, database initializing, etc. and one base template, and depending on a specific url variable (I use $_GET["content"]) I include scripts with the business logic and include templates for the content area of the page.
With this, you have all settings by hand, but have the business code splitted in script files.

[TGKnIght]

I have written a simple example of this, check the second link in my sig
_________________
Smarty site with one index.php controller file
Working with MySQL and Smarty
SmartyColumnSort
Custom Smarty Javascript Debug Template