Not necessarily. You can put one partial in a single location. I have
the following structure for my applications:
application/
layouts/
views/
scripts/
modules/
agency/
views/
scripts/
I have scripts located in both the layouts/, views/scripts, and
modules/*/views/scripts/ folders, and I render some partials located
in just application/views/scripts from the module/controller view
script. You don't have to have a copy in each of your respective
controller directories.
BTW, is what you're doing not suitable for Zend_Layout ?
--
Chris Weldon
On Mon, Jan 19, 2009 at 12:36 AM, Cameron <themsel...@gmail.com> wrote:
> wouldn't view partials still require the view script to exist? I was trying
> to avoid having the actual files there too. Infact, the perfect solution
> would be to override if the file does exist.
>
> On Mon, Jan 19, 2009 at 3:32 PM, Chris Weldon <ch...@chrisweldon.net> wrote:
>>
>> Action Helpers are really dependent upon what you are trying to do.
>> Something that's static I would render out using partials. However, if
>> you're doing a bit of output processing (nothing static), I would
>> recommend using an Action Helper. :-)
>> --
>> Chris Weldon
>>
>> On Sun, Jan 18, 2009 at 11:17 PM, Cameron <themsel...@gmail.com> wrote:
>> > Hi guys,
>> >
>> > I have an application that is growing piece by piece, table by table,
>> > and as
>> > it grows, as do the number of view scripts the application needs. In
>> > order
>> > to ease maintenance on these, I've managed to make the vast majority of
>> > the
>> > views indentical across controllers, by just passing the relevant
>> > variables
>> > in to the view. Of course, this means I still have to cut and paste the
>> > views each time I make a change to one of them, which is clearly
>> > inefficient. So, what's the standard way around this? I saw Action
>> > Helpers,
>> > and they seem like they would do the trick, but I'm not sure if that's
>> > considered "best practice". Any ideas?
>> >
>>
>>
>>
>> --
>> Christopher Weldon
>> http://chrisweldon.net
>> ch...@chrisweldon.net
>
>
--
Christopher Weldon
http://chrisweldon.net
ch...@chrisweldon.net
