Hi Folks,

This may not make a whole lot of sense, it's just a brain dump of various things I'm thinking about rearchitecture, but I thought it'd be better to send it to the list so people can see the vague thoughts I've been thinking ;)



Do we need to build our own Python anymore?

To make it easier for casual developers to try things out, could we
make wx and PyICU eggs and put them on PyPI, so the whole application
is just an easy_install away?  It looks like Robin has worked on
making a wx egg...

selected difficulties from old plugin model:
  Menus: placement after x, before y
  Graceful removal of plugins
  Placement of new detail view fields

will we do sharing?
   Can we reuse most of our eim work?
   fix triage status lifecycle
   re-model to avoid recurrence hacks
   can we avoid needing server work?
   simplify conflict lifecycle

Follow pje's lead and try to do doctest first development of features, so there's more/better documentation?

searching for sets of orthogonal, but reasonably well-defined deliverables:
---------------------------------------

recurrence model
  +continue to use dateutil for expansion of rules?
  +do we try to recreate the model where any and all changes
     can apply this/thisandfuture/all?

persistence
  +persistence -> in memory
  +dump/reload eim to disk
  +save to sqlite

sharing
  +sharing to existing morse code server
  +sharing to existing CalDAV server
  +fix triage status model issues

calendar UI
  +single collection
  +multiple collections
  +multi-week
  +adjustable geometry multi-week

detail view
  +all fields visible
  +stamp -> fields appear/disappear
  +"edit session" notion

list view
  +editable title/triage status/button for re-sort
  +row reordering
  +triage button drop down (LATER +2weeks, etc.)
  +collection membership swatch column

sidebar
  spheres/hierarchy model
  spheres UI
  spheres interaction model (add collection "mine" sphere, remove it, etc.)

about:config style ui for hacking the trellis

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev

Reply via email to