2010-01-12 Tuesday Meeting
Discussion on web client
proj. mgmt
- Contact Donald before weekend
- What do we do wrong?
- What would a new tool give us that we don't currently have?
4.2
- responding to Jason's email
- J-M/Will away.
-
discuss today updating the graffle
- if we can get web flushed out today
- prefixing graffle with which trac
misc
- another laptop for andrew
presentation : WEB
- understanding short term TODOS vs. long term strategy
- leading toward clarifying what the web client is
- scientists want to share; what are the workflows within client?
- recently moved to left panel navigation, right panel metadata
- check boxes on each thumbnails for applying action
- Scott: value of import and rois as part of workflow ?
- Chris: could also do statistics/admin'ing in insight
- Josh: would be good to all be moving
-
Jean-Marie: first decide if we're happy with direction web is going
- i.e. 2 panel solution (available to play with?)
- perhaps need feedback before we add new things
- Chris: everything available? Yes, except for annotations
- Scott: navigation...
-
Will: if web & client are to have same functionality,
- then they should have the same layout.
- shouldn't have to learn a new UI
- examples of web apps that work like fat clients
-
Chris: looking at the screenshot, what do we need to change?
- 3 panels? Ola: but no space
- resizing the columns is not so easy, but browser dependent
- moving of borders? important?
- more than 2 thumbnails side-by-side
- resizing will never work like standalone
- Jean-Marie: don't want to disturb too many people
-
Jean-Marie: make decision about functionality like history
- use space for something else
-
Chris: are we happy with how this looks?
- Brian: leap isn't too large from insight
-
Jean-Marie: what are we interested in?
- If I'm doing imaging, I want to see images.
- prob. only for 1 out of 50 will want to see text
- insight is 70/30 ratio of images
-
propsition with Jason: collapsing of columns
- Brian: hide button
- application doesn't have state, will have to re-save
- Josh: what are the other things like state and navigation?
-
Chris: we should be careful to not do this multiple times
- disturbs people
-
Donald: scrolling
- wide screens?
- what if you don't know it's there?
- relationship to google maps? collapsing panels
- Carlos: many features "borrowed" from maps
- Jean-Marie: if that's how users interact on the web...
- Brian: fullscreen ability? (based on browser)
- Jean-Marie: viewer in center panel?
-
Jean-Marie: other web specific features that we need to have
- bring users to a level that they are used to
-
Chris: if we can reasonably get to a 3 panel state
- then we can look at workflow things
- default views, can you do the same things, etc.
-
Jean-Marie: with insight, we had to get it in front of users
- Josh: thought we have some data on that
- Chris: do have enough data?
- Josh: the feedback period needs to be a conscious decision
-
Ola: one feedback - links to data
- problem is the state of the tree, etc.
- Carlos: calculating on open of box. work like that?
- still possible with ajax
- Chris: no choice - has to use the little link icon
- Josh: doesn't have to be decided now...
-
Scott:
- Chris: we have very little data
-
Jean-Marie: example of emma
- originally said "that's fine"
- then when had to annotate MBL data said "sucks"
- Chris: link for example is useless without permissions
-
Can we make April 15? / What else other than UI?
- multi-action button
-
data public / shares
- search
-
group visible is mostly done
- how do people organize their data
-
Donald: publishing > rois?
- if someone is only using web, then they won't have any rois or scripts
- Chris: do we have an exhaustive list?
- measurement tool, scripting, roi, editor,
- Jean-Marie: but are we confident in what's there
- Brian: solidify the base functionality
-
Ola: re-organize the whole UI in a week
- all supported by Ajax
- not perfect then
- could spend a whole month and could still be wrong
- e.g. drag-n-drop is very sensitive (remove it?)
-
planning
-
ui / navigation (1 month)
- A. Applying what we've already learned about usability
- B. Making sure web2.0 usability is also present
- C: LOTS and LOTS of feedback, talking to groups
- first step: 1 wk. layout then Monday testing? * Josh: but who is trying to do there work? * Chris: approach a HCS group (no experience) * Ola: one of the demo servers on trunk? * Jean-Marie: perhaps we could first discuss about previous version * Jean-Marie: multiple people for testing on diff. browsers
- if we are getting no response, then we'll readjust
-
sharing permissions within a group
- must work!
-
publishing
- couple of weeks
- depends on how much functionality / how many options
- one image should be easy, multiple images ....
- depending iShare must come first
-
roi: do some markup
- Jean-Marie: should use the power of web
-
MISC
- look at it every week?
-
ui / navigation (1 month)
graffle
- take turns, Chris & Melissa starts
- color-code is good. (more feedback for Donald)
- Chris: end of week? Josh: for thursday would be better.
- all of jean-marie's for january is there
- add somethings into februrary if possible.