Hi, just to add my opinion to this: - I agree with Joe, in that documentation needs to be the first base. Proof of it, is that even though, it is probably writen all over in different places, I have had to come to the T2, T3 conclusion that Massimo so clearly writes here, by deduction, and not by reading some red bright neon sign that would have saved me from putting any time into trying to get to know those products. - However, I have been seeing improvements, in the documentation little by little, and if the book is coming out, then I'd rather not fret about it, until I have it in my hands and use it daily. (I am a forgettable person, and need these books not only for learning but as constant refference).
- That said, I think that there is more to making this effort than creating an app. And I think that in there Yarko is right to the point, and only for that it should already be worth the while for all of us. If only it helps us to build a basic structure that we can further refine as a means for collaborating in developements, and possibly in documentation... Well, to me, thats the goal. Take any project as an excuse. - Regarding what project to take... well, I highly doubt that we will have any kind of success in building anything big by any standars in this initial go. But as I said, thats beyond the point that I see as main goal to this initial effort. However, I'd still say go for something small, as the need for organisation on something bigger is so much greater, that I doubt we would reach the developement phase in one piece, and a fruitless project is discouraging to all. - I also have to say, that I do like Johns idea of going through the book, although, I think it achieves a different goal than setting a collaborating/developement/documenting environment. - As for a callendar, well, thats something I have been missing in several of my projects, and its easy to see a fit to it to almost anything, from event management to time resource availability. Even a calendar app may get big though, so again, I'd start with something small. - Regarding CMS and eStore. Well.. a CMS is a monster of its own, but I think that one needs to consider, what effort will be put into maintaining, and documenting it later on... onto adapting it and updating it as web2py advances?. That's actually the main reason why I wouldnt try to create a full fledged CMS, its kind of diverting resources from web2py if you want it to be alive, and what point is it in creating it as a whole if we do not plan on maintaining it as we go along?. I really think that both CMS and eStore, really only make sense as proof of concept, and not as full fledged applications, just as a basis to go on from there. Anyway, all that said, I am in... however I have to say just like John... I am a slow programmer. My main area of expertise is actually ERPs. Benigno. On Jul 12, 4:28 pm, 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 -~----------~----~----~----~------~----~------~--~---
