Thank you very much for your comments.
On Feb 12, 2011, at 3:34 AM, Quincey Morris wrote:
> So you still at the stage where you need to think about design not
> implementation -- don't make the mistake of designing for a pre-chosen
> implementation strategy. First, start by designing your user w
On Feb 11, 2011, at 18:08, Andy Akins wrote:
> Imagine a "purchasing" application. First, you have to open a "catalog" - a
> file that lists the items that are available. There might be multiple files,
> representing multiple stores or sets of items, but you have to pick just one.
>
> Then, you
I'm working on an application that has multiple files as part of its data
model, and I'm not sure on the approach I should take.
An example of what I mean:
Imagine a "purchasing" application. First, you have to open a "catalog" - a
file that lists the items that are available. There might be mu
