|
|
Posted by petermichaux on 10/12/05 23:34
Carl,
> Having recently started the planning stage of a project very similar to
> yours, I am also quite interested in this subject. More in the
> consolidation aspect of it than in the 'guideline' aspect.
How similar? If it is eCommerce then perhaps we could work together?
What do you mean by consolidation vs. guideline?
>
> IMO, the database abstraction _code_ should be handled in a fashion
> similar to i18n, meaning that just as you would present text to a client
> depending on the currently defined language context, the text(code)
> presented to the DB should depend on the selected database context.
Say what? What is i18n?
> What exactly do you mean by a 'PHP class pattern'? Are you using one
> 'class' to handle all of your forms, or applying a pattern to each of
> your forms.
I am applying a pattern to each form. I think it is neat, tidy and
flexible. It is easy to develop seperately the parts of a new form from
a blank form template. The form handling is about the only part of my
application that I am really happy with. Perhaps if we decide to have a
sample application I can explain more after strip the bells and
whistles from my code.
-Peter
Navigation:
[Reply to this message]
|