Chekin' in

[Daniel Abrams]

Me too. This is MUCH BETTER than the old Events!

I'm going to update Calendar once we are closer to having Events done. So, it looks broken at the moment.

[Hollis Brown]

Let's go down the list of icons on /admin-manage-events/.

• Fee - Eventually we will want to allow Admin to setup individual Fees for individual Days of Child Events.
• Attendees - Obviously dependent on #1 above, we will want individual Sign-in/out for individual Days and/or Child Events.
• Emailer - Also dependent on #1, would be kool if we could target to individual Day and/or Child Event Attendees.
• Cloner - Do we want to be able to clone Day and/or Child Events?

This may be a discussion for another day, or...

[Hollis Brown]

Would be kool if Admin could Activate/Inactivate by clicking [Active] or [Inactive] here: /admin-manage-events/

[Daniel Abrams]

Fee - Eventually we will want to allow Admin to setup individual Fees for individual Days of Child Events.

I agree, but definitely in this update. Huge, huge job!

Attendees - Obviously dependent on #1 above, we will want individual Sign-in/out for individual Days and/or Child Events.

Same. I agree, but definitely in this update. Huge, huge job!

Emailer - Also dependent on #1, would be kool if we could target to individual Day and/or Child Event Attendees.

Same. I agree, but definitely in this update. Huge, huge job!

Cloner - Do we want to be able to clone Day and/or Child Events?

Let's also hold off on this well for now.

Would be kool if Admin could Activate/Inactivate by clicking [Active] or [Inactive] here: /admin-manage-events/

Don't we already do this some place like Admin :: Manage Users. Would make life easier than coding from scratch.

[Hollis Brown]

I think we're getting close.

[Daniel Abrams]

Working on it ...

[Hollis Brown]

When I attempt to delete a Child Event, I get this popup:

Are you sure you want to delete this Master Event and all of its Days, Child Events, and Breaks? This action CANNOT be undone.

This is not a Master Event. Nor is it a Main Event.

[Hollis Brown]

Would be kool if Admin could Activate/Inactivate by clicking [Active] or [Inactive] here: /admin-manage-events/

Don't we already do this some place like Admin :: Manage Users. Would make life easier than coding from scratch.

Seems like it, but I don't know where.

[Hollis Brown]

Regarding the Main :: Sub v. Parent :: Child discussion. I'm thinking that "Main" could easily be construed as the Single (top of the tree) Main Event. In that case, the event below (Day) is a sub-Event. Does that make the partial day Event a sub-sub-Event? People better understand that the Parent :: Child :: relationship is generational. Since we have more than one generation (and possibly more to come), I'm thinking Parent :: Child is optimal.

How would we have more - you ask. In next update we might have a morning Child event that has two, or more, different Speakers with two separate sign-in/outs.

So, unless you see a reason not to, let's go with Parent :: Child.

[Daniel Abrams]

Working on something ...

[Daniel Abrams]

Would be kool if Admin could Activate/Inactivate by clicking [Active] or [Inactive] here: /admin-manage-events/

Don't we already do this some place like Admin :: Manage Users. Would make life easier than coding from scratch.

Seems like it, but I don't know where.

Would be kool if Admin could Activate/Inactivate by clicking [Active] or [Inactive] here: /admin-manage-events/

Done.

Regarding this, fixed. Look at other post shortly . . .

[Daniel Abrams]

Regarding the Main :: Sub v. Parent :: Child discussion. I'm thinking that "Main" could easily be construed as the Single (top of the tree) Main Event. In that case, the event below (Day) is a sub-Event. Does that make the partial day Event a sub-sub-Event? People better understand that the Parent :: Child :: relationship is generational. Since we have more than one generation (and possibly more to come), I'm thinking Parent :: Child is optimal.

How would we have more - you ask. In next update we might have a morning Child event that has two, or more, different Speakers with two separate sign-in/outs.

So, unless you see a reason not to, let's go with Parent :: Child.

Confusing. What changes are you suggesting?

[Hollis Brown]

I thought we were in the middle of a discussion about language:

Main Event :: Sub-event

or

Parent Event :: Child Event

I decided that I like Parent :: Child.

I'll keep an eye out for places that I think it might be confusing.

[Hollis Brown]

Would be kool if Admin could Activate/Inactivate by clicking [Active] or [Inactive] here: /admin-manage-events/

Don't we already do this some place like Admin :: Manage Users. Would make life easier than coding from scratch.

Seems like it, but I don't know where.

Would be kool if Admin could Activate/Inactivate by clicking [Active] or [Inactive] here: /admin-manage-events/

Done.

Regarding this, fixed. Look at other post shortly . . .

Oh that... yeah, we did that in /manage/members/, but that's not what I had in mind. I was thinking [Click to Toggle].

[Daniel Abrams]

Would be kool if Admin could Activate/Inactivate by clicking [Active] or [Inactive] here: /admin-manage-events/

Don't we already do this some place like Admin :: Manage Users. Would make life easier than coding from scratch.

Seems like it, but I don't know where.

Would be kool if Admin could Activate/Inactivate by clicking [Active] or [Inactive] here: /admin-manage-events/

Done.

Regarding this, fixed. Look at other post shortly . . .

I think we did this somewhere. Can you have a look around?

Oh that... yeah, we did that in /manage/members/, but that's not what I had in mind. I was thinking [Click to Toggle].