One thing is important... Build each controller in a controller with its own name (do not call it default, call it calendar for example).
Assume a db connection created by db.py but put the models for your component in db_calender.py. This will simplify merging of components. Massimo On Jul 12, 9:28 am, JohnMc <maruadventu...@gmail.com> wrote: > Yarko, > > I am game. Just be warned, I code slow. I don't have all of Web2Py in > my head like some of you sharper knives in the drawer! :) > > I think it would still be useful to sprint through the book as a proof > of process. But I am flexible. > > If we tackle calendar Then I might offer a few suggestions for > requirements - > > * Views available for day, week, month, year. Plus a stub for custom > views. > * Configurable attributes - > + time slice of any span down to 15min. > + user definable classification of event types. > + user definable coloration of the classification. > + user definable default view. > + user definable mail address. > * Events that - > + usual details, time, place, date, interval, recurring. > + can have predecessor/successor tags. (w) > + triggerable. Mark the event to launch an action thru cron (w) > + Notification either by mail or notification if user is also using > Web2Py calendar. > * Variable visibility of events (public, private, confidential, etc) > * Export/import calendar via RSS, XML, iCal. > * Usual tools, copy, paste, delete, bulk move > * Group functions - > + view participants public calendar events. > + assign/remove a new event to all in a group. With confirmation > acceptance. > + find first available date based on time interval for all in group. > > (w) - Would be part of a workflow controller. But hooks are available > in calendar. > > Probably missed some pieces. I just pulled the major attributes off > the PlOne CMS calendar function. A repeat of this is available > --http://docs.google.com/View?id=ddfwjgjr_68cb6fk4gr > > I'll open it up to invitees to those interested that want to add/edit > the requirements. > > JohnMc > > On Jul 12, 2:19 am, Yarko Tymciurak <yark...@gmail.com> wrote: > > > My mind immediately JUMPED at JohnMc's suggestion of a calendar - > > > Useful everywhere; useful in CMS, in community sites, even in eStore where > > you sign up for events (as opposed to shippable products - e.g. seminars, > > haircut appts, etc.) > > > Massimo's like just gives the front end - all that's left to do is a base > > backend (I would guess).... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
