Just wondering about something...
Does anyone actually use multiple view paths?
I do but my path layout is something like
main_template_path (custom, tables, etc)
library_path1
library_path2
I was looking at the way that Maypole::View::Base constructs the
paths handed
on to the derived View class (TT). From the above we would get:
main_template_path/current_table
main_template_path/custom
main_template_path/
main_template_path/factory
library_path1/current_table
library_path1/custom
library_path1/
library_path1/factory
library_path2/current_table
library_path2/custom
library_path2/
library_path2/factory
Is it just me or is that inefficient and not terribly useful?
I generally find that I would want just one path to the factory
templates
because I only put them in one place. I'd also want just one
occurrence of my
library paths without 'custom' or the name of the table appended.
In other words, were I to have two sets of main templates (current
project does this),
I'd like (and expect) to see.
main_template_path1/current_table
main_template_path1/custom
main_template_path2/current_table
main_template_path2/custom
library_path1
library_path2
factory_path
Does anyone else think this (if so, I'll write patch or two) or not
(in which case I'll do my own View package)?
nic
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Maypole-users mailing list
Maypole-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/maypole-users
