![]() Gravitybox WebSchedule.NET
1998-2005 Gravitybox Software LLC
Page 8 of 65
The need for WebSchedule.NET
In todays world, there is a need for a general-purpose scheduling utility. More
applications are requiring at least some scheduling as part of their functionality. Many
developers dreading this task save it for last only to realize that it is a much larger task
than at first they thought. A high-quality schedule inside of your application is an
application in and of itself. You could spend your entire allotted time developing just this
part of your application.
This is where the Gravitybox WebSchedule.NET component comes in. Many
companies want to provide their clients with the ability to schedule various events.
Alternatively companies wish to provide some sort of pay service that includes the
ability to schedule appointments. For example a golf course or doctors office may wish
to offer their clients the ability to setup their own times online for appointments.
Traditionally building an application with scheduling on the web has been very difficult.
There have been no third-party components of any significance and manually creating a
schedule grid has produced less than professional results. The WebSchedule.Net
component addresses these issues and allows you to add scheduling to any web
application with minimal effort.
Goals of WebSchedule.NET
The goals of WebSchedule.NET are several. These are the guidelines on which the
software was developed.
To create a high-quality component
To have a small learning curve
To have the maximum functionality with a minimal of code
To add user requests in a timely fashion
Real-World Uses
When evaluating a software product, its usefulness is its most important attribute. No
matter the time and care expended to create a software program, if it does not solve
any real-world problem, it is useless. WebSchedule.NET has been designed to resolve
many scheduling situations. The original goal of the component was to produce a
module that could be dropped into an ASP.NET application to provide scheduling for a
for a doctors office. This did prove an ambitious goal in and of itself. The necessary
functionality has been added to accomplish this task.
As stated, this component may be used to create web applications that have significant,
differing scheduling purposes. The first use is an office application. Some of the
program features follow. It should graphically display clients that are scheduled to come
into the office on any given day. It should be able to list services provided and cost. It
should be able to assign a category and a provider to an appointment. The developer
should be able to define categories and providers. There are other more advanced
|