On Mon, Sep 09, 2013 at 09:25:54PM +0700, Henrik Sarvell wrote: > Aha ok so the file grew by accident to become something that is not really > best practice?
Well, it can also be "best practice", if you like. Just don't worry too much about it. For an application with so many classes and indexes as in that example, it may make sense to create more files. It is difficult to give a clear rule. > Anyway your template example pointed the way for me, I simply "pad" my dbs > E/R like so: > > (dbs > (3 +Page #1 > ... > (5) #13 > (6)) #14 > > And then in the project building on the framework: > > (dbs+ 15 > (3 +Blog) > (3 (+Blog id url hline content pdate)) ) Yes, perfect. So you have room for later extensions. ♪♫ Alex -- UNSUBSCRIBE: mailto:email@example.com?subject=Unsubscribe