FEATURE REQUESTS

http://lists.osafoundation.org/pipermail/design/2007-September/ 007669.html Keith Windsor made a request for a a way to dynamically re-adjust the recurrence rule for recurring tasks. 'This is ideal for those things that have to be done at regular intervals, but that can slip for a day or two: Give cat worm tablet, check car tyre pressures, do monthly review, etc, where, having slipped, you don't want to go back to the original schedule.' Andre chimed in with additional use cases: Hair cut, oil change.

http://lists.osafoundation.org/pipermail/design/2007-September/ 007676.html Greg Noel wrote in, in support of a more flexible multi-week view (as opposed to a fixed month view). That is indeed the direction we're headed in, but won't be in the first iteration of month view we implement.

http://lists.osafoundation.org/pipermail/design/2007-October/007718.html
I forwarded a thread from the internal PR list about a feature request for duplicating events.

ANNOUNCEMENTS

http://lists.osafoundation.org/pipermail/design/2007-September/ 007677.html I posted links to very bare 1.0 Planning Wiki pages for both Desktop and Server.

http://lists.osafoundation.org/pipermail/design/2007-October/007720.html
Jeffrey sent an update on improvements he's made to the quick entry field including short-cuts for the various commands we currently support.

http://lists.osafoundation.org/pipermail/design/2007-October/007735.html
I sent out a call for Open Design Issues that should be addressed before I leave for vacation this Saturday.

DESIGN ISSUES

- Sharing between Desktop and Hub Issues

http://lists.osafoundation.org/pipermail/design/2007-September/ 007672.html I pulled together a summary for the 'Rationalizing various sharing URLs between Hub and Desktop' issue. This discussion is currently on the back-burner as there are more critical sharing issues to work on in the near-term. I plan to bring this up again after 0.7.2.

http://lists.osafoundation.org/pipermail/design/2007-October/007684.html
Morgen started a thread to explore options for keeping subscriptions in sync between the Desktop and Hub. Some issues that have come up are being tracked in bugzilla: https://bugzilla.osafoundation.org/ show_bug.cgi?id=10983 + What do we do with subscriptions that Hub supports but Desktop doesn't and vice versa? + What if the Desktop user subscribes without an account and then at a later date signs up for an account?

http://lists.osafoundation.org/pipermail/design/2007-October/007687.html
I started a thread for 'Keeping published collections in sync between Desktop and Hub'. I wasn't sure if the Desktop would suck down the default Hub collection that's created when users sign up for a Hub account.

Next action: Morgen There's still an open issue about who creates the tickets for this collection: Hub or Desktop?

- Calendaring

http://lists.osafoundation.org/pipermail/design/2007-September/ 007681.html
Reid posted notes from our meeting on Month View

I followed up with preliminary proposals for Month View on the Desktop and Month View and Overlays for Hub. + Desktop: http://lists.osafoundation.org/pipermail/design/2007- September/007682.html + Server: http://lists.osafoundation.org/pipermail/design/2007- September/007683.html

http://lists.osafoundation.org/pipermail/design/2007-October/007694.html
I sent a proposal for incorporating a Date Picker in the Hub Detail View. mde followed up with some questions.
Next Action: Bobby to reply to mde's questions...

http://lists.osafoundation.org/pipermail/design/2007-October/007703.html
I sent out some mock-ups for overlays in Hub.
+ mde responded with some questions/issues which led us to filing a bug for keeping the collection name in sync between Desktop and Hub: https://bugzilla.osafoundation.org/show_bug.cgi?id=11010 + Jeffrey forwarded a related thread on this issue from the Cosmo-Dev list: http://lists.osafoundation.org/pipermail/design/2007-October/ 007725.html

http://lists.osafoundation.org/pipermail/design/2007-October/007736.html
mde responded to my call for Open Design Issues with a question about how to phrase the recurrence edit dialogs on Hub.

- Dashboard

http://lists.osafoundation.org/pipermail/design/2007-October/007685.html
I wrote-up a summary of design issues related to the Who column and the Addressing stamp.

This spawned a number of related threads:
+ The summary above included a proposal to only display 'edited/ update by' temporarily in the Who column for unread items if the item in question was a message and had fr/to attributes. This led to the proposal that we should do the same for 'date last modified' and display that temporarily in the Date column for unread event items or items with upcoming tickler dates. In writing up the bug however, I came across a few issues with this proposal: http:// lists.osafoundation.org/pipermail/design/2007-October/007692.html

+ Jeffrey started a thread to further explore options for making the 'Addressing stamp' more useful for assigning tasks, etc: http:// lists.osafoundation.org/pipermail/design/2007-October/007706.html

http://lists.osafoundation.org/pipermail/design/2007-October/007738.html
I forwarded a thread from the Users list about sorting in the Triage Status column. In particular, how to reconcile explicit ordering with auto-ordering based on the Date column.

BUGS

http://lists.osafoundation.org/pipermail/design/2007-September/ 007674.html I reported seeing some false-positive sharing conflicts due to email updates and sharing getting out of sync with each other. We have a partial solution to this problem, which won't get rid of the false- positives entirely. But assuming users are syncing regularly, false- positives should at least go away once users sync both email and shares.

http://lists.osafoundation.org/pipermail/design/2007-September/ 007675.html As a short-term resolution to the still open issue of 'Which inbound changes should be considered/ignored for marking an item unread or moving to the NOW section', I asked Morgen if we could fix the errant 'from' attribute that's causing message items to pop into NOW for seemingly no reason.

I started a thread to try and pin down the handful of 'serious screwing up my data' bugs that still remain.
http://lists.osafoundation.org/pipermail/design/2007-October/007695.html


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

Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design

Reply via email to