Re: [PHP Template] template system requirements

Hi, Michael. On Mon, 10 Apr 2000, Michael Pohl wrote: > A full-blown requirements document would be ideal. Lacking that, I mean > any attempt to enumerate specific requirements beyond the general > philosophy of separating form from content. I mean the requirements that > would hopefully inform the specs, rather than vice versa. > > A few examples: > > How are terms like "template logic" and "presentation" being defined > exactly? > > Is a requirement to have template tags appear for designers in plain text > in WYSYWIG editors? To be hidden altogether? To be always parsed on the > fly? > > What are the goals for the syntax? To be as HTML-like as possible? To be > as plain-English as possible? To save as many keystrokes as possible? Truthfully, we did not have a requirements document. I mainly took what FastTemplate had and expanded on it. The main goals, I guess, were to be designer friendly but still flexible enough to have template logic. If someone wants to work with me to come up with requirements document, it'd be a good project. The spec certainly is not good for documentation either, it's just a reference. One of the reasons I've created this mailing list is to ask people's opinions on the design of the engine. -Andrei When we eliminate the impossible, whatever remains, however improbable, must be true. -- Sherlock Holmes