Skip to content
This repository has been archived by the owner on Nov 23, 2018. It is now read-only.

Update the time inputs for the user schedule #84

Open
MitMaro opened this issue Sep 15, 2013 · 4 comments
Open

Update the time inputs for the user schedule #84

MitMaro opened this issue Sep 15, 2013 · 4 comments
Labels
enhancement
Milestone
Version 1.0

Comments

@MitMaro
Copy link
Member

MitMaro commented Sep 15, 2013

Add drop-down for hours, minutes and a.m./p.m. and limit the second set of drop-downs to only times after the first.
@whymarrh
Copy link
Contributor

Would be nice to have a natural language form (see http://goo.gl/otQPo).

@whymarrh whymarrh mentioned this issue Sep 21, 2013
Closed
@whymarrh
Copy link
Contributor

screen shot 2013-09-21 at 5 17 10 pm

How does this look?

whymarrh added a commit to whymarrh/aba-lookup that referenced this issue Nov 4, 2013
@whymarrh
Refactored AbaLookup module.
dbea85c 
Still to-do:

- Refactor test classes.
- Remove TODO notes from comments and flesh out accordingly
- Update views

In progress:

- Merging profile and profile edit views (MUNComputerScienceSociety#99)
- Add ScheduleForm in place of 'hard-coded' form

Blockers:

- Issues MUNComputerScienceSociety#84, MUNComputerScienceSociety#82, MUNComputerScienceSociety#79, MUNComputerScienceSociety#65

In this commit:

- Moved authentication actions into their own controller
- Moved registration into AuthController
- Merging profile and profile edit views
@whymarrh
Copy link
Contributor

whymarrh commented Nov 5, 2013

Do we want to add this to Milestone Version 1? This can affect how we structure the form for editing the schedule and in turn the Schedule API. For example, if we have a list of the available times and a radio element for choosing add/remove, vs. if we have (as shown above) the various select elements may result in different APIs.

@whymarrh whymarrh mentioned this issue Nov 5, 2013
Open
@MitMaro
Copy link
Member Author

MitMaro commented Aug 17, 2014

I like what is above and I think we should simply keep the previous input so that a user only need to change a single field to duplicate a timeslot across different days.

@whymarrh whymarrh added this to the Version 1.0 milestone Aug 18, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
Version 1.0
Development

No branches or pull requests
2 participants
@MitMaro @whymarrh