Dear all,

I have a project which is to be completed before 9th April in PERL.

If anyone who have worked on PERL and is intrested can contact me on this number
09822315626.

Project Details below:

For this assignment, you will create a web site for a fictional camera retailer,
San Diego Discount Camera. This retailer sells Nikon, Canon, Olympus and Sony
digital cameras. Additionally, the retailer hosts special events to promote the
business.
One of the major problems faced by small retailers and organizations is the
difficulty and expense of keeping their web site current. Your application will
provide a turn-key solution to this problem by allowing the retailer to add,
modify, or delete information easily, and with no special training.
Your main page must consist of the following:
Links: Home, Inventory, Events, About Us, Contact. These links should always be
visible in the current page. (Inventory items and events cause a new window to
open. These links should not be visible in transient windows.
Calendar: A calendar for the current month. Your calendar should be labeled with
the current month and year. It should be correctly formatted, with a column
header day of the week label. If there is an event for any day that month, the
date is a link, which will open an information page about that event in a new
window when clicked. You need not show more than the current month. A nice
enhancement which is desirable, but not required, is the ability to advance the
calendar to future months.
Inventory Link: When the Inventory link is clicked, a sub-selection with brands
will be displayed. When a brand is selected, the inventory items for that brand
are displayed. This page contains all items for a particular brand in an
abbreviated fashion, which shows a small image and a model descriptor, both of
which are clickable. When the user clicks on either the image or model
descriptor, a new window will open with a larger image, and a full description
of the product. This window should feature a "print" button that sends the
current window contents to the printer.
Events Link: When clicked, this displays all current and future events in
summary fashion. The date and title for each event is shown. The event title
should be a link which opens a new window showing complete details about the
event (similar to the window that opens for inventory items.)
The About Us and Contact links are static pages with appropriate fictional
details.
Additional Details
Your application will have two distinct entry points: one for customers
(public_html/proj3/proj3.html, as detailed above.) and one for the retailer to
update his site. The entry point for retailer administration is
public_html/proj3/proj3_admin.html.
The proj3_admin.html should be a login screen with username and password fields,
plus reset and submit buttons. (NOTE: be sure to put your username and password
on the single page you will submit for this assignment!)
On successful login, the user will be presented with the following choices:
Add new inventory item.
Delete inventory item(s).
Add new event.
Delete event(s).
You must verify the authentication before any changes are made to the system.
You may use cookies, sessions, or hidden fields to accomplish this.
You may add choices to edit inventory items or events, but this is not required.
Should the user need to edit an inventory item or event, he will need to delete
it, and then add the corrected entry. (If you add edit options, then the user
should be presented with a screen populated with current information which can
then be edited.)
For Delete Events/Delete Inventory Item selections, the user should be presented
with a line line description of the item and a check box. All items selected via
the check box should then be deleted from the system on submit.
It is desirable (but not required) that your system delete any image associated
with a deleted item.
The fields for inventory items are:
Model name or number.
Image of the item.
Description of the item. A short paragraph of text extolling the virtues of this
model.
Specifications. i.e. number of megapixels, sensor size, recording media, aspect
ratio of image, weight etc.
Price (formatted as $xxx.xx)
The fields for events are:
Title.
Date and time of the event.
Location.
Image (optional). [ Note: optional for the user--your application will allow the
user to upload an image or skip it as he/she desires. ]
Description of the event.
Any additional details. (This provides for a second text section if it is
desired)
When an inventory item or event is opened in a new window, it must be formatted
in an appealing way. For events, the page must look good whether an image for
the event was supplied or not.
Events in the system on dates that have passed should be deleted from the
system. [ A good way to do this is when any script is run from proj3.html, check
for and delete any old events. ].
Details about this assignment may be added or clarifications added as the
assignment progresses. Any changes will be clearly marked as such in this
assignment page, and will become part of the assignment specifications.
Do not use the -wT flags or use strict in your perl code. While it's a good idea
to enable these, it fills up the log files on the server. This is a gradeable
issue.
Be sure to populate your project with at least five inventory items per brand,
and also five events that occur in April 2009 after the 9th.


Thanks & Regards,
Mandar