1. THE OUTPUT I have changed my thinking on the groupings. If today was THU then WED would be "Yesterday", TUE would be "Tuesday", MON would be "Monday", SUN would be "Last Week". If monday was the start day of your config for a week. This is the very same behaviour as MS Outlook 2003 when you group by date. The only mod to the outlook behaviour (Microsoft do do some things ok ;-)) if when the dates get older they could be split into "First Half of 2007" "Second Half of 2007" OR "Winter of 2007", "Spring of 2007", "Summer of 2007", "Fall of 2007", "Winter of 2006" etc etc You would need to take into consideration hemisphere somewhere in the application settings as it differs.
When you're looking back at dates human nature is to group things into bigger sets that the memory can bounce other events off. 2. THE CONTROLLER and VIEW The controller method must provide a way of sorting these records by this field. So it would neeed to be numeric or something The view method can produce the nice english phrase above (Internationalised of course) I prefer convetion over configuration so the parameters should default to todays date from the client side and also should look for the T2 stamp modified_date field. If there is none then it should use the first date field it can find. OH just thought also that there should be a "No Date" phrase as well. My thoughts are exactly along your lines of including this as a display method on a column in the model. This would be a default and could be overridden at the view level. What da ya think? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
