You have chosen to sponsor your bid up to a maximum amount of .
The calendar I use is great for paying jobs, but right now I can not add appointments that are not with clients. I have included the actual page that the calendar runs on (calendar_action.php) and the included file that contains most of the code (calendar03.phtml). calendar_action.php connects to the database already, so you need not worrry about that.
I have created a mysql table PT_Other_Appts with the following fields:
This table will hold the data for my non-client appointments.
I would like it to display appointments like this: the name in blue and the start and end time (different than my client appointments) The name should also be a link to a popup window that has all of the info for the appointment (except id).
Below the last form to add a paying appt., I would like a form that allows the user to create an appt in PT_Other_App. the form should post to the same page calendar_action.php that the form is in.
For the tutor_id field, it should be a pull down menu. You can get the values for the menu from another table PT_Tutors. The menu should display first_name last_name and the value should be id.
For the date, I would like a pop up calendar that the user can use to select the date. The month of the pop up calendar should match the month of the calendar, not the present date.
For the times, I would like the use to enter the hour and minutes as separate text fields, and there should be a pull down menu for am/pm.
Both dates and times will have to be converted to mysql format when they are entered into the data base.
When this information is entered, the same page should be called, and the data should be entered into the data table PT_Other_Appts
1) All deliverables will be considered "work made for hire" under U.S. Copyright law. Employer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the employer on the site per the worker's Worker Legal Agreement).
2) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
3) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):
a) For web sites or other server-side deliverables intended to only ever exist in one place in the Employer's environment--Deliverables must be installed by the Worker in ready-to-run condition in the Employer's environment.
b) For all others including desktop software or software the employer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this project.