Chris, > Do you have the web2py book? Yes, I do, however, since I am no Python programmer, I don't always get my head around things. Learning Python is high on my priority list.
> Documentation on the newer features is available on the web site > e.g.http://www.scribd.com/doc/16085263/web2py-slides-version-163 I bookmarked the link. I'll have a look at the slides asap. > Sorry if I was a little rude. I was just quite excited to see a > question on the mailing list that I thought I could actually answer! No offense taken;-) I very much appreciate your help, and I couldn't agree with you more on: 'mucking about with times in string format'. I made all the changes you suggested and the time fields all work perfectly. I had a look at the AlterEgo post, it also says: If create widgets, we suggest you put them in a module for easy reusability, importing them and assign them to the fields in the model file. In my case, I would create a widgets.py file in the modules folder of my application, put the widget code in widgets.py, in my model import the widgets (from modules import widgets) and use it like this: widget=timeplain. Wouldn't I? Kind regards, Annet. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
