[FX.php List] Curious: include-page naming conventions

[Kevin Futter]

I use an 'includes' folder too, but I tend to only use includes for page
sections that repeat across a site ('header_inc.php', 'footer_inc.php',
'main_nav_inc.php', etc), or for classes and other 'helper' files.

Speaking of classes, and segueing slightly, do you guys use any sort of
naming convention for classes? I've only recently started tackling writing
OO PHP, and have been struggling with how best to organise such code. At
the moment I'm using a 'classes' folder and calling the class files
whatever seems a fair thing. Would PHP still make sense of a '.class' file
(rather than '.php') and parse it once included?

Kev

--
Kevin Futter
Webmaster, St. Bernard's College
http://www.sbc.vic.edu.au/




On 6/10/11 9:45 AM, "Tim 'Webko' Booth" <tim at nicheit.com.au> wrote:

>
>
>Mine are always in an includes folder, with the parent page as the
>start of the name:
>
>search.php
>includes/search_form.php
>includes/search_list.php
>includes/search_detail.php
>
>Cheers
>
>Webko
>
>_______________________________________________
>FX.php_List mailing list
>FX.php_List at mail.iviking.org
>http://www.iviking.org/mailman/listinfo/fx.php_list

This e-mail and any attachments may be confidential. You must not disclose or use the information in this e-mail if you are not the intended recipient. If you have received this e-mail in error, please notify us immediately and delete the e-mail and all copies. The College does not guarantee that this e-mail is virus or error free. The attached files are provided and may only be used on the basis that the user assumes all responsibility for any loss, damage or consequence resulting directly or indirectly from the use of the attached files, whether caused by the negligence of the sender or not. The content and opinions in this e-mail are not necessarily those of the College.