Add two main features to an existing open source Calendar program for DNN 2.0 called AVCalendar 3.0 at [url removed, login to view]
-Add categories (cities) and subcategories (event types) for filtering events displayed for each Calendar instance
-Add an option for an event list view in addition to the existing calendar view
1.) A new "calendar admin" option will be added to the "pencil" control icon
2.) Clicking this option brings a newly designed interface with
a.) a combo box for selecting the calendar city
b.) a combo box for selecting the event type (choose ALL and the calendar will display all event types)
c.) a check box for selecting the view type (calendar or list)
d.) a text box for entering #events to display for list view
e.) final button to select "update settings"
3.) An update to the "Add event" interface will be added. At the bottom of this interface there will be a required option to select the event type.
4.) The calendar display will no longer be portal /moduleID dependent. The events that get displayed on the calendar will depend solely on the cityID and eventTypeID filters
5.) The new Event List view will only display events that occur on the current day or later. And of course, only ones that match the cityID and eventTypeID. And only X amount of events will be shown as designated in admin interface. The format will look like below and be tab aligned. The event name will be a hyperlink that takes you to the event view just like in the calendar view.
08-19-04 - THR - Volleyball Team Practice
08-20-04 - FRI - Dinner Fancy Restaurant
08-23-04 - MON - Networking Breakfast
The list of cities and event types will consist of the basic set below and can be stored in a database with a primary key like below. So there is not need for an interface to add data here but it must be compatible for me to add/remove cities or event types manually to the database.
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) 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 Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.
b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request.
3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer 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 buyer on the site per the coder's Seller Legal Agreement).
4) The coder shall supply a private assembly that can be installed in DNN 2.1.2 successfully with features requested. This includes a modified SQL install script for generating any new DB tables.
5.) The coder shall supply all source code and files needed to build the private assembly.
Windows Server 2003
SQL Server 2000
.NET 1.1 Framework
Compatible with all 95% of browsers