>
>
> The administrator can add, edit, and delete events.  Events can have
> start/end times/dates, titles, and descriptions.  These attributes are
> displayed in the Event list.  In the add/edit views there is a field
> for Location, although I'm not sure how this is used -- it is not
> displayed anywhere that I noticed.
>

Location is just a text field where people can enter something like
"Minneapolis" or "My House". It's not used in the views, but you can easily
add it if you need it.


>
> 1. Is it only possible for administrators to add/edit/delete events?
> Can moderators and/or members?

Currently just admins.


>
> 2. How is the location attribute used?

See above.


>
> 3. The Event model has a user_id field -- how is this used?

It's not used. But in some apps I subclass Event and I need the subclass to
have an owner (Bulletins, in TennisMetro, are a subclass of Event).



>
> 4. The Event model has a metro_area_id field -- how is this used?
>
Same as above; it's nice to be able to attache a metro area to a subclass of
Event.


> 5. Is there any other functionality that exists out-of-the-box?
>
Nope.


>
> Some of this stuff may only be known to Bruno.  Thoughts?
>
> On Jun 29, 6:22 pm, Justin G <[email protected]> wrote:
> > Thanks Errol, I figured someone submitted this patch considering the
> > "applying diff" commit message.  Once I get some code in decent shape
> > I'll post my branch to github.
> >
> > I like your duplicate event idea because I expect to have events that
> > don't follow a predictable schedule, but may occur at the same place
> > or time of day.
> >
> > Justin
> >
> > On Jun 24, 5:15 pm, eksatx <[email protected]> wrote:
> >
> > > Thanks for the shout-out (I submitted that as a patch to Bruno as I
> > > had not yet gotten the hang of github, pull requests, etc.).
> >
> > > I'm definitely interested in fleshing out the events functionality.
> > > The things you suggested have all crossed my mind.
> >
> > > Here's another one: a link for 'duplicate event' that would be helpful
> > > for events that repeat.  A link like that would be much easier than
> > > "repeating event" functionality (which in my opinion often ends up
> > > either to simplistic to be useful or too complicated for users to
> > > understand).
> >
> > > I will pitch in and help with this as soon as I am done with my
> > > current project.  I am currently fleshing out the private message
> > > stuff.  It is so close to being done that it made sense to me to knock
> > > that out.  I'll post a separate topic about that in a minute.
> >
> > > Anyhow, I'll keep this thread bookmarked and come back to it when I'm
> > > free.
> >
> > > Errol
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"CommunityEngine" 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/communityengine?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to