16:00-18:00
Final class meeting, with group presentations.
This was a very useful class - I'd recommend it highly to anyone with a good programming background needing a quick course in web development and design.
Over and out...
Wednesday, August 15, 2007
Finished developer notes
12:00-2:00
Finished developer notes, contents are:
Account summary (username, passwords, various account descriptions)
Site administration (login information, and index page for editable content)
Content management (howto for image upload, RTE and calendar database)
Technical details (how to write a new web page, site layout, etc.)
Finished developer notes, contents are:
Account summary (username, passwords, various account descriptions)
Site administration (login information, and index page for editable content)
Content management (howto for image upload, RTE and calendar database)
Technical details (how to write a new web page, site layout, etc.)
Monday, August 13, 2007
class meeting
15:45-19:30
Met for class, did site review as group. (Fixed typos, gramatical errors, nits, etc.) Wrote whatever temporary content we could.
Site is now fully "live", no more lorum ipsem, though still plenty of "coming soon"... It's a shame, but our client apparently had still another death in the family, and has basically been out of action for the entire term. As far as content goes, we put up what we could.
Met for class, did site review as group. (Fixed typos, gramatical errors, nits, etc.) Wrote whatever temporary content we could.
Site is now fully "live", no more lorum ipsem, though still plenty of "coming soon"... It's a shame, but our client apparently had still another death in the family, and has basically been out of action for the entire term. As far as content goes, we put up what we could.
Sunday, August 12, 2007
Thursday, August 9, 2007
worked on docs
18:00-22:00
Fixed a few minor issues, and wrote the docs for technical description of website.
- Technical details documentation is about 3/4 done. (Rough draft)
- Administrator's guide is about 3/4 done. (Rough draft)
- Content management users guide about 1/4 done.
- Replaced "disclaimer" link in footer with link, in red, to the administration page for the duration of an administrative login session. (<~10 minutes)
- Made some minor suggestions for Aubrey's forms. (Code was fine, just needed some refactoring to tidy up.)
Wednesday, August 8, 2007
team meeting
16:00-19:00
- Finalized the header and footer formats, replaced all the old files.
- Accepted the new file upload manager. Marked images as uploadable. (Got help from instructors for DOM code problems.)
- Cleaned up nits in style sheet (with Manit & Amy)
21:30 - 23:00
- Finished with the uploadable images. (Renamed images to correspond to their container pages; duplicated images that were linked from multiple pages.)
Except for the content, the site is basically complete. It's been a bit disappointing to get so little feedback from Nancy. :/
Tuesday, August 7, 2007
Added file upload support
16:00-23:30 (approx)
- Wrote php form for file uploading (uploadmgr.php) and for accepting the uploaded file (upload.php)
- Wrote javascript routines so that file upload manager is spawned when the image to upload is clicked. (Took a long time, since I needed to learn the javascript.)
Behavior of the upload manager
- img "alt" property is replaced (java onload function) by "click to upload" to give a cheesy tooltip in IE. (This required adding a "name" property to uploadable images. I don't like this.)
- img "onclick" added to launch the upload manager.
- May add red border to editable pictures in admin mode.
Sunday, August 5, 2007
unify style sheets and navigation
16:00-23:00 (approx)
- Group meeting from 16:00-17:00,
- After discussion in class:
Removed style directives from content pages, as much as possible. (With much help from Amy) - Wrote new include file header that shows the appropriate secondary navigation (based on a variable)
- Stripped out all the secondary navigation stuff from the content pages.
Thursday, August 2, 2007
Calendar function is working
17:00 - 21:00
Still need some work on style and I/O formatting, but INSERT, UPDATE and DELETE all work, along with presentation of a calendar (ranged query) for each event type (MUSIC, VISUAL, etc) or for all events together.
Action items:
Still need some work on style and I/O formatting, but INSERT, UPDATE and DELETE all work, along with presentation of a calendar (ranged query) for each event type (MUSIC, VISUAL, etc) or for all events together.
Action items:
- Use javascript for presenting data, rather than generating html with php. (It must be more efficient for the server.)
- Add relabelling for generic field-name input
- Add support (and security) for fully typed generic sql I/O
Wednesday, August 1, 2007
site plan, calendar
15:00-19:00
PRIMARY KEY (event_id),
KEY(start_date)
);
Limitations of RTE mean that uploaded images must go in a directory named .../image, and must be named by hand. This means that a user (dynamic) image directory is required, which I will call
href="/uploads/image"
- Wrote the site plan, rough draft.
- Came up with a usable design for the calendar.
- Helped Zeke with rte configuration.
calendar plan
Will serve ranged queries on date, using first, last date and optional event type. Schema is:
CREATE TABLE calendar (
event_id INT NOT NULL AUTO_INCREMENT UNIQUE,
start_date DATE NOT NULL,
start_time TIME NOT NULL,
end_date DATE,
end_time TIME,
event_type ENUM ('MUSIC', 'VISUAL', 'PERFORMANCE', etc),
event_name VARCHAR(100),
event_location VARCHAR(100),
html_text TEXT(2000)
PRIMARY KEY (event_id),
KEY(start_date)
);
Limitations of RTE mean that uploaded images must go in a directory named .../image, and must be named by hand. This means that a user (dynamic) image directory is required, which I will call
href="/uploads/image"
Subscribe to:
Comments (Atom)