Chris and crew,
Been following the discussions on the list while reviewing display
code for xhtml compliance. Some good discussion. Waiting to hear
some of these good recommendations turned into direction.
As for the xhtml: Most changes will be inconsequential (removing
inappropriate outer con
On 4/28/07, Ed W <[EMAIL PROTECTED]> wrote:
> Hi
>
> > 3) Workflow/User Experience concept: Here we have screens and
> > workflows. Some business rules may exist here.
> >
>
> Should we collect some simple "use case" scenarios?
Sure :-)
These include two categories:
1) Tutorials (example cas
Hi Ed;
> I can't help wondering if the current Quotes/Order/Invoice model isn't
> slightly too few states for some business.
>
> My model is:
>
> - Customer calls and gets quote
> - Customer calls back and places order
> - Customer either hands over CC details on the phone or enters them into
> t
Hi
> 3) Workflow/User Experience concept: Here we have screens and
> workflows. Some business rules may exist here.
>
Should we collect some simple "use case" scenarios?
I would be happy to knock out a few based on my own scenarios here? I
need to get them a little more straight anyway i
> Sales orders and invoices are both potentially legal documents.
>
> Invoices are financial transactions while orders are not.
>
> Again, information-wise they can still be part of the same physical
> layout, but the order will not have the financial component.
>
I can't help wondering if th
