Ok it got it working After a bit of debugging, thanks Python for clartity. The two plug ins I mentioned work but you have to easy_install dateutils, at least I had to on my freebsd 9 machine, not sure what the state of the dateutils module is regarding the python library.
Second the GantPlugin accepts a date format parameter and does the translation. It is ugly in a way because it means the format inside the DB is the format I want for display/entering (DD/MM/YYYY) and that each plugin has to have knowledge of that and accept a translation parameter, but it works. Thanks a lot for your answsers. I'll keep thinking about a "better" solution where knowledge of date format is not disseminated but Trac seem to move into that direction by itself with I18n. On Jun 4, 12:29 am, iamonotyourdatas <[email protected]> wrote: > I had a look at that :http://trac-hacks.org/wiki/DateFieldPluginand > thishttp://trac-hacks.org/wiki/CustomFieldAdminPlugin, but it seems > not to translate the date entered in the UI toward the MM-DD-YYYY > format that seems to be used internally by Trac... > > Unless I misused something, it thus does not solve the problem. > > I may be mistaken about the importance of this for the current Trac > community, just wanted to voice that this is a showstopper for > probably a lot of people that evaluate the tool, I may be wrong of > course, but it is hard to pitch a project management tool that does > not get dates. > > I understand it is hard work to properly handle field types and > widgets in a general way but I have this nagging feeling that > admitting that the pivot date is the "us" format and translating from > and back to it should be doable. It would at least help people working > on non "us" projects as long as they don't work in multi cultural team > i.e : the date format would have to be fixed by project and not adapt > to the locales values of the user. But it would still be much better > and cover a lot of use cases. > > I am really too new to Trac to hope achieve that, but I'll get a timid > look at it tomorrow still. > > Are there other people having the same problem that I do to be able to > pick up Trac as their tool of choice ? > > Thanks for the help. > > On Jun 3, 11:55 pm, iamonotyourdatas <[email protected]> > wrote: > > > > > > > > > Some of those patches are more than 2 years old .. > > And it seems focused on adding a datetimepicker on the interface but > > still having the "us" format ... > > > On Jun 3, 8:42 pm, iamonotyourdatas <[email protected]> wrote: > > > > No I was not aware of it I'll look at that (a ticket number I > > > suppose) ;) > > > > On Jun 3, 8:04 pm, Peter Suter <[email protected]> wrote: > > > > > Hello > > > > > On 03.06.2012 19:08, iamonotyourdatas wrote: > > > > > > Tracs seems not to have a "Date" type for fields and custom fields and > > > > > no plan to have one. > > > > > Are you aware of #1942? [1] > > > > > If I understand you correctly, it addresses exactly your problems. > > > > > You could apply the patches [2] to see exactly what the current state of > > > > development is. Any feedback you might have is appreciated. > > > > > -- > > > > Peter > > > > > [1]http://trac.edgewall.org/ticket/1942 > > > > [2]https://bitbucket.org/psuter/trac-1942 -- You received this message because you are subscribed to the Google Groups "Trac Users" 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/trac-users?hl=en.
