unclebill, on May 17 2006, 01:02 PM, said:
An appearance table needs to added to the database, to allow what is called soft code.
Just a word of advice, using terms like "what is called soft code" comes across as exceptionally patronising.
I'm a proffessional PHP developper, adopting an MVC approach within PHP to seperate code and content.
The only time I've ever heard the terms hard coding and soft coding regard paramaters like the base_url of a site beign coded in in every instance it's needed as opposed to a $cfg['base_url'] variable, or some such.
unclebill, on May 17 2006, 01:02 PM, said:
For example the color of the column headings on a page would be stored in the database and could be changed in the admin panel. You might even prompt a color pallet in the admin panel to help the admin select the color.
That would end up with an exceptionally bloated database, because in order to give control over the html, you'd need database entries for every box in the system, meaning that every time you want to add a new piece of html you have to add a new cell to the database, lowering efficiency by creating more need for database connections.
unclebill, on May 17 2006, 01:02 PM, said:
Templates are OK, but just more hard code.
Templates are not hard coding. Templates aren't coding at all, they're layout.
unclebill, on May 17 2006, 01:02 PM, said:
If you want a truly flexible product, you should soft code as much as possible.
I really can't see where you're coming from here.
unclebill, on May 17 2006, 01:02 PM, said:
This eliminates users from having to learn to alter files and code.
And increases overhead by needing a database query per-box per-paragraph per-page.
unclebill, on May 17 2006, 01:02 PM, said:
It makes upgrades less painful.
But running the system more painful and slower.
unclebill, on May 17 2006, 01:02 PM, said:
All in all it makes the product more like an upscale business software
No. It really doesn't.