Re: Requesting a report in the QuickEntry

I think 2 is better as well. 1 could be misconstrued as a way to  
define how granular you want the reports to be. Report my progress on  
a day-to-day basis versus monthly summaries.

===

<Food for thought. No need to act on the stuff below, but Vera's  
question got me thinking about use cases and ways to refine the  
report UI.>

Backing up a second, what are some use cases for these different time  
parameters? I think this is an interesting way to think about how (in  
the future) reports for different time parameters might be different.

One is simply, the user defines the report around the amount of time  
it's been since they did their last review.

A second might be that so much happened in the last 48 hours, you  
feel like you need to do an overview to make sure you didn't drop  
anything.

Mimi

On Jul 10, 2007, at 11:57 AM, Jeffrey Harris wrote:

> Hi Vera,
>
>> 1) Rigid, but possibly simple to use:
>> "/report daily" - for the last day
>> "/report weekly" - for the last week
>> "/report monthly" - for the last month
>> "/report" - will result in a default weekly report
>>
>> 2) Flexible, similar to the timedelta in Python
>> "/report days=1" - for one day
>> "/report hours=2" - for the last two hours
>> "/report weeks=2" - for the last two weeks
>> and so forth
>>
>> What are your opinions?
>
> Option 2) sounds good to me.
>
> Sincerely,
> Jeffrey
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "Design" mailing list
> http://lists.osafoundation.org/mailman/listinfo/design

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

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