(ccing design)
Mimi,
See below...
...Bryan
Mimi Yin wrote:
http://wiki.osafoundation.org/bin/view/Journal/AlphaFourDetailView
Okay, I've done a pass at pulling together all of the features that
the detail view is going to expected to support in the Alpha 4
timeframe. (I also snuck in some nice to haves, just in-case ;o)
What am I missing?
I see that the Label field isn't in alpha4 anymore, but you don't
mention Appears In: you still want it as-is for now, right?
What doesn't make sense?
- " Pop-up fields (to be able to view and edit fields when the text
exceeds 1 line)" (if that's what I'm seeing depicted in
Alpha4_DetailView_Edit.png) conflict with the way autocompletion works
-- I'm not sure how popping up an autocompletion list over the popped-up
editing field would look: is that your intent? (or is autocompletion
supposed to work some other way?)
- The special requests section (storing gobbledygook in addressing and
date/time fields, especially addressing!) both look hard to implement in
a way that's complete and satisfying -- where "hard" means we'll need to
reconsider and possibly reimplement a lot of how we store, sort, index,
import/export, and share/merge these fields, and I'm still not sure it
won't be more confusing to the user than if we'd just done decent
validation (with support from autocompletion) at data-entry time. Is
this really an alpha4 requirement?
What should I storyboard out in more detail?
Do we need a spec for this?
Have a good weekend!
Mimi :o)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
