The downside is that it makes the code more brittle. As soon as you
change the ID of a subsite, add a new one above it or change the
element ID, you'll get a bunch of errors about missing templates.
Do you think it's a good idea to add this feature to the public API?
Sounds good, yes. I think I'm not mistaken if I say that most
applications won't
have that many subsites, and even fewer will radically change their
structure
over time. These methods will make things easier for 80% of the
applications out
there, and a fair warning should save the other 20% from hell.
There's one thing that breaks we this also though, you can't just jar
up your templates and elements anymore and include them at any
location into another site. Any getHtmlTemplate() call in there will
then fail. Currently, you can pretty much take any site-structure and
reuse it that way.
--
Geert Bevin Uwyn bvba
"Use what you need" Avenue de Scailmont 34
http://www.uwyn.com 7170 Manage, Belgium
gbevin[remove] at uwyn dot com Tel +32 64 84 80 03
PGP Fingerprint : 4E21 6399 CD9E A384 6619 719A C8F4 D40D 309F D6A9
Public PGP key : available at servers pgp.mit.edu, wwwkeys.pgp.net
_______________________________________________
Rife-users mailing list
[email protected]
http://www.uwyn.com/mailman/listinfo/rife-users
