So I've recently rewritten the model for Datasources to allow them to
be loaded by reflection from the Datasources object -- it reads a
properties file with classnames, factory method names, and string
parameters (that's the only restriction) and then calls the method to
return the datasource. The only one that is required to succeed is
the user DS, other than that it's open.
NutritionData.com is partially in place. It loads food groups, and is
beginning to acquire the bits needed to search for foods. I'm close
on that one, I think. I have the general outline of what I want to
do, now it just remains to be seen if I can do it.
The design issue I have is with the "Create New Food" use case. Right
now, we allow it to be created as coming from any given source -- be
it nd.com, USDA... The thing is, it won't keep that info - It will be
set to "My Foods" no matter what, since that's the only food
datasource that is allowed to change at all. I know the dialog is
generic, so maybe that combo box could be disabled when it's used for
a new food? I'm thinking maybe that box should be a label, instead --
that field will never be changeable in there. Then, when a food is
edited from a non-mutable source, it can be changed to reflect the new
source.
I'm still working through some UI ideas in my head right now. I can
feel that there's things I'd like to do, but the ideas aren't gelling.
I only know that I don't want to do too close an imitation of the
food tool you're already using. Which is, I realize, not necessarily
your call on it. Naturally where it comes to design, I have to bow to
your preferences :) Still, I think it might pay to sit down and have
a UI design session of some kind sometime soon.
--=20
Chris R.
=3D=3D=3D=3D=3D=3D
Not to be taken literally, internally, or seriously.
|
