On Mon, 2013-06-10 at 15:58 +0200, Cédric Krier wrote: > On 10/06/13 07:06 -0600, Mark Hayden (local) wrote: > > > > > > > > > > Al 10/06/13 11:19, En/na Cédric Krier ha escrit: > > > > On 10/06/13 11:16 +0200, Sergi Almacellas Abellana wrote: > > > >>> Al 09/06/13 01:25, En/na Cédric Krier ha escrit: > > > >>>>> On 08/06/13 23:01 +0200, Albert Cervera i Areny wrote: > > > >>>>>>>>> A Dissabte 08 Juny 2013 20:59:19, Cédric Krier va > > > >>>>>>>>> escriure: > > > >>>>>>>>>>>>> Hi, > > > >>>>>>>>>>>>> > > > >>>>>>>>>>>>> With the calendar view going to be included > > > >>>>>>>>>>>>> [1], I'm looking for places where we could > > > >>>>>>>>>>>>> use it. > > > >>>>>>>>>>>>> > > > >>>>>>>>>>>>> I already made a patch for production > > > >>>>>>>>>>>>> module [2] because I think it makes sense > > > >>>>>>>>>>>>> to plan the productions. > > > >>>>>>>>>>>>> > > > >>>>>>>>>>>>> Please tell me if you have any other > > > >>>>>>>>>>>>> applications? > > > >>>>>>>>> > > > >>>>>>>>> events in calendar module :) > > > >>>>> No calendar view is not a generic calendar. > > > > I still think it would make sense to have events in a calendar view--it > > seems like the most obvious one ;-) > > > > > >>> > > > >>> I don't understand. If events have date_start and date_end why > > > >>> don't create a calendar view for it? > > > > Because they don't always have. > > > > > > dtstart is required[1] on the Event object, so it's allways defined? > > > > > > [1] > > > http://hg.tryton.org/modules/calendar/file/96d8ad41a859/calendar_.py#l408 > > > > > > > I am willing to be patient--not work on it right away but have a > > calendar view of events be in future plans. It can be more complicated > > than simple reminders because events can span over time (across weeks > > and months, etc) and they can be recurring. The dtstart might not mean > > the actual time an event starts--I think with recurring events it may be > > the initial recurrence sometimes, etc. so it may be the most complex > > case to deal with. I am not sure of all the possible complexities and > > how the database represents them so I cannot say for sure (I have only > > used events in the most simple case so far--meetings that span only > > hours within a single day--and it is enough for me right now how to deal > > with presenting the times to users in different time zones properly!). > > > > Saying that, even if it is more work than one would think it's not like > > proper calendaring including a calendar view of events has not been done > > before--so it should be something to consider on a "wish list" for the > > future to support such cases. > > I don't think it should be in the scope of Tryton client. > If you want a calendar application use one (like Thunderbird+Sunbird) > that support CalDAV. > It is just the same approach as the one to not create (or remove) an > email (request) client inside Tryton client but use any existing Email > client. >
That is a fair comment I suppose--Tryton is an ERP applications platform first and foremost, not a groupware system, and with CalDAV interface we can use a client of our choosing (we have also fed event data to web applications via Nereid here). I can still see how it would be useful not having to switch between clients if such events are part of business operations though. Since that is perhaps a more special case it may not be suitable for core functionality, and a contrib module extending the view would be more appropriate, and it is a "nice to have" anyways. Another thing Tryton would be good for (including a calendar view) would be in an asset management application (not stock lot management, but for assets like manufacturing equipment, computers, vehicles, etc) to handle things like scheduled maintenance activities, work orders and so forth. Not aware of asset management modules that are distributed so such a module would have to be created first. However the calendar view would be a useful part of that. Mark.
