Hi, I just wondered, which is the exact reason for naming / organizing the three components for data abstraction like it is done in the quickstart.
While it seems perfectly clear that the model is named Guestbook, I find
it a little bit irritating that the Mapper / Gateway is named
accordingly and the DbTable has its own subdirectory.
I think we should either aim for a flat hierarchy like
Guestbook.php
GuestbookMapper.php
GuestbookDbTable.php
or should spend the mappers a directory too - just so that on every
level only files of the same type are accessible ... something like
Guestbook.php
Mapper
--- Guestbook.php
DbTable
--- Guestbook.php
I am aware of the fact that you can implement this according to your
personal likes, but I guess - taken into consideration that there's not
always a DbTable to extend - a more general naming convention could keep
irritation low ...
Just my two cents.
--
Cheers, \\|//
Vince (o o)
----------------------------ooO-(_)-Ooo-------------------------
''' (o)_(o) [ ][0][ ]
ô¿ô (=°o°=) World Domination by Copy and Paste [ ][ ][0]
- (")_(") [0][0][0]
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
Ooo.
---------------------------.ooO----( )-------------------------
( ) (_/
\_)
signature.asc
Description: OpenPGP digital signature
