r1 - 12 Jan 2004 - 16:11:00 - DuckySherwoodYou are here: OSAF >  Journal Web  >  MeetingNotes > SmallMeetingNotes > CaterpillarQuestions20031216

Meeting to discuss implementation of 0.3 caterpillar ui

Attending: JohnAnderson, JedBurgess, KatieCappsParlante
Looking at Caterpillar UI and Nav Bar Added resolutions after a meeting with the design team. (20031218)

Features we suggest not implementing in 0.3

resolution: ok

  • Undo/redo (will come later with appropriate repository support)
  • OS X style "drawer" (will start working on making this possible)
  • autocomplete in nav bar
  • stop (we should architect it, and do it if easy, but might be more complicated)

Features we might like to add

resolution: ok

  • Debug menu (in debugging version only, perhaps)
  • facility for adding columns to list views
    • resolution: in menu, Katie to provide appropriate list of choices
  • menu accelerators

Questions/Open Issues

  • "create a bookmark" button
    • included in nav bar proposal, but not caterpillar screen shots
    • "save" might be a misleading term
    • resolution: no button in nav bar, bookmark button in menus
  • parameterized urls
    • resolution: design team to follow up
  • cmd click 2 sidebar "views"
    • what is the url?
    • is this a new view?
    • resolution: design team to follow up
  • wxMac tabs are terrible
    • resolution: ok
  • url hierarchy for views and content items, and its relationship to the repository
    • resolution: we're using the list from the nav bar doc for now, which is independent from the repository.
  • reload vs notification of changes
    • resolution: we're in agreement that generally views are notified when the repository changes, without explicit action required from the user, but the user will need an affordance for update/refresh in some cases, in particular remote repositories.
  • drag and drop
    • resolution: one of the "extra credit" items, the most interesting in the very short term being the drag and drop of a content item onto another tab, used to create mixed collections. Design team might end up revisiting this.

Engineering issues

  • asyncronous fetching from the repository, notifications and threads: need to get this designed for "stop" to work correctly
  • collections and queries and cpia (known issue that folks are working on)
  • drag and drop
  • how far can we get in avoiding specialized blocks, how much can be done assembling known pieces?

-- KatieCappsParlante - 18 Dec 2003

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r1 | More topic actions
 
Open Source Applications Foundation
Except where otherwise noted, this site and its content are licensed by OSAF under an Creative Commons License, Attribution Only 3.0.
See list of page contributors for attributions.