The system disclosed in O'Sullivan, however, does not perform the actions of a virtual assistant, nor does it permit the user to control how the system adapts. Another caller adaptive VRS is disclosed in U. Martin et al. The response time of a user to voice prompts is measured and an average response time is determined.
It is assumed that the lower the average response time, the greater the competence of the user. The average response time is used as an index to a table of ranges of response times. Each range has respective voice segments associated therewith. The voice segments comprise oral instructions or queries for the user and vary according to the anticipated competence of the user.
If the average response time changes such that the voice segments indexed are different to the current voice segments then a data base containing information relating to user competence is updated to reflect such a change.
Accordingly, when the user next interacts with the voice response system a new set of voice segments more appropriate to the user's competence will be played. The system in Martin et al. The call identification code of a telephone call can be used as an index to data stored in a user database comprising information relating to the competence of a user.
Alternatively, the user can be asked to enter a password before further access is allowed to the system. The password can then serve as an index to the stored data associated with the user.
The stored data identifies which set of voice data is appropriate for use during an interaction with said user. Alternatively, determining the number of times per day that a user accesses the system or the length of time which a user has subscribed to such a system may also be indicative of their competence.
Again, VRS disclosed in Martin does not perform the functions of a virtual assistant, nor does it permit the use to have any significant degree of control over the behavior of the system. Further, while the prior art systems adapt automatically to the caller, the degree of adaptation is relatively limited. For example, the prior art systems do not disclose a virtual assistant that automatically uses words associated with polite discourse when the user's input contains words associated with polite discourse.
Prior art systems also do not disclose a virtual assistant that adapts to the user based on the user's emotional state. The present invention relates to a personal virtual assistant with many discrete features, each of which comprises a separate but related invention.
Thus, one aspect of the present invention is a computer-based virtual assistant the behavior of which can be changed by the user, comprising a voice user interface for inputting information into and receiving information from the virtual assistant by speech, a communications network, a virtual assistant application running on a remote computer, the remote computer being electronically coupled to the user interface via the communications network, wherein the behavior of the virtual assistant changes responsive to user input.
Another aspect of the present invention is a computer-based virtual assistant that automatically adapts its behavior comprising a voice user interface for inputting information into and receiving information from the virtual assistant by speech, a communications network, a virtual assistant application running on a remote computer, the remote computer being electronically coupled to the user interface via the communications network, wherein the remote computer is programmed to automatically change the behavior of the virtual assistant responsive to input received by the virtual assistant.
As detailed below, the virtual assistant adapts to the user in many different ways based on the input the virtual assistant receives. Such input could be user information, such as information about the user's experience, the time between user sessions, the amount of time a user pauses when recording a message, the user's emotional state, whether the user uses words associated with polite discourse, and the amount of time since a user provided input to the virtual assistant during a session.
Other features and advantages will become apparent based on the following detailed description of the preferred embodiments and the claims. The subheadings used herein are meant only so as to aid the reader and are not meant to be limiting or controlling upon the invention. Generally, the contents of each subheading are readily utilized in the other subheadings. As shown in FIG. The human interface 12 is comprised of a graphical user interface 22 , which may be a web browser, a subscriber or user voice user interface 24 , generally accessed by a telephone, and a public voice user interface The virtual assistant allows a user to use a voice interactive device, such as a telephone, either wired or wireless, to access and update such information.
The VA Server also manages all incoming communications by sorting, prioritizing, and filtering such communications, while providing notice to the user of important messages and events.
As seen in FIG. The VA Engine receives spoken commands, interprets and executes them. The VA Engine also supports a telephony interface 46 to voice messaging 52 and private branch exchange systems 54 , enabling third-party systems to be integrated with the VA Server.
Those skilled in the art, however, recognize that the VA Server can be ported to other computing platforms. Multiple systems may be clustered together to support higher system workloads and fail-safe operation. The VA's architecture, however, advantageously permits integration with other commercially available and customized messaging applications. The VA Application can be easily modified to satisfy specific requirements of a user. The basic functions of the VA Application include:.
Contact Management—scheduling, planning, group calendar, contact and referral organization. Intranet Applications—users can remotely access information contained on a corporate network inside the company firewall using the VA, for example, customer data, shipping and inventory information, sales reports, and financial data, or any information on a database server 66 , including SQL databases such as Oracle or Informix.
The VA Studio allows a user to create, modify and debug applications that run on the VA Server 40 without requiring the user to be skilled in the complexities of the underlying components of the VA Server, such as the speech recognition engine, text to speech engine, switch control and unified messaging. It allows developers to create projects, each of which defines a VA application. VA applications are developed using Active Scripting languages such as VBScript and JScript, thus enabling integration with a variety of third party components.
The VA applications created with the VA studio will include voice query to SQL databases, message stores, business logic and mainframe applications. VA applications are composed of discourses and resources.
Discourses are the context of conversations between a user and the VA. Resources are items like voice prompts and dictionaries.
Application templates consist of packages of predefined discourses and resources. Once a VA application template is generated, the application is further customized using any supported Active Scripting languages. After writing the VA application, it is then submitted to the build process. During the build process, VA Studio checks for dialog errors, builds a master intermediate grammar and builds a master lexicon.
Once compiled and error-free the application is ready to be published. The VA Server allows a scripted application to access services such as voice mail, databases, and telephony equipment. The completed application is then automatically installed and configured to run on the VA Server, which enables the VA application to take incoming calls and provide access to both public and private information.
An Introduction to Virtual Assistant Applications. A VA application allows a user to manage electronic communications and access his or her business's computer resources through a telephone. Using speech recognition and text-to-speech technology, the VA communicates with callers in spoken English. By calling into the VA on a standard telephone, a user can perform functions such as the following:.
Checking, replying to, and forwarding email messages. Looking up phone numbers and addresses in an electronic address book. In addition, the VA can perform many of the functions of a personal secretary, such as the following:. Informing the user via pager when new voice and email messages arrive.
Filtering incoming voice mail, email, and pages as instructed by the user. In the preferred embodiment, the VA performs the above functions by interfacing with a company's Microsoft Exchange server.
This application, in effect, allows users to use their desktop Outlook software over the telephone. The SDE provides the core components necessary for the functionality of a VA: a telephony interface, speech recognition facilities, a text-to-speech engine, interfaces with databases and mail servers, and an administrative framework in which the assistant applications will run.
As discussed above, the VA Platform consists of three main components:. The function of each of these components can be understood using a World Wide Web analogy. The SDE functions like a web server, providing connections with the network and telephone system, controlling the execution of VA applications, and providing resources such as text-to-speech and voice recognition engines that will be accessed by the applications that run on it.
The VA applications are analogous to web pages, determining the content that will be presented and controlling the interactions with the user. The main component of the SCE is the VA Studio application, which is based on the Microsoft Visual Studio paradigm and provides a graphical environment with a variety of tools that can be used to create, debug, and publish applications that are run on the SDE.
The SCE also includes a set of COM objects that can be used in applications to perform functions such as checking email, reading from a database, and manipulating sound files. The Service Deployment Environment consists of eight processes that run simultaneously and perform the functions necessary to support a VA application. Although they may all run on the same hardware platform, for large VA implementations the components can be distributed across several servers and communicate over the network.
Such distribution can allow, for example, one server to be dedicated to performing voice recognition functions while another supports the VA Engine that actually runs the applications. When multiple VA components are distributed across multiple machines, these machines are collectively termed a VA server set.
As illustrated in FIG. Based on the application's instructions, the VA Engine uses its telephony interface to communicate with the user and its speech interface to recognize speech into text and translate text into speech. In the preferred embodiment, the user is electronically coupled to the virtual assistant application via a public switched telephone network. As can be appreciated by one skilled in the art, the communications network that electronically couples the user interface to the computer on which a virtual assistant application is running could be a packet switched telephone network.
Also, the communications network could be a wireless communications network. A VA Engine process can support user interaction over only one telephone line, but multiple VA Engines can be run simultaneously on a single platform. If the VA platform is connected to more than one telephone line, then a separate VA Engine will be running for each incoming line. The Text-to-Speech Server receives text from other components, translates it into speech that is, into a sound file , and returns it to the requesting component.
This speech translation service is isolated in a separate component to improve performance and to allow for TTS vendor-independence. Only the TTS Server component would have to be modified for such a customization, not the entire platform. Multiple VA Engines can use the same TTS Server process, and more than one TTS Server can be running at the same site, allowing translation services to be distributed across multiple machines for load-balancing.
The Recognition Server receives sound files from other components, attempts to recognize them as speech, and returns the recognized text. Like the TTS server, the Recognition Server is a component that isolates speech-recognition functions from the rest of the VA platform.
The server provides an interface to a third-party voice recognition engine in the preferred embodiment, Nuance that can be changed to a different vendor's brand without requiring the entire VA platform to be modified. The Recognition Server process requires three additional processes to be running:. The Resource Manager: The Resource Manager is a management process that automatically load-balances requests when more than one instance of the Recognition Server is running.
Rather than making recognition requests to a particular Recognition Server, the VA Engine makes the request to the Resource Manager, which forwards it to the first available Recognition Server. The License Manager: The License Manager server runs continually in the background and dispenses licenses to all requesting components.
Only one license manager need run in a single server set, but no Recognition Server components can launch unless the license manager is already running. In the preferred embodiment, all of the sub-processes of the Recognition Server are recommended only for Nuance brand Recognition Servers. If a user uses different speech recognition software, a different set of processes may be needed. These functions include the following:. Monitoring external sources such as email boxes, databases, and web sites for events e.
Applying rules and filters to external source events to determine whether the VA system should take any actions. This application creates and monitors all VA components that are active on the system, and it provides management interfaces that are used for the following purposes:. Configuration both at start-up and during run-time. Signaling of events such as errors and informational messages. Logging of each call received by the VA applications running on the system.
Performance monitoring through an interface to Window NT's Perfmon utility. The VA Server Manager provides a single point of control for all of the processes and servers being used in a VA server set. It communicates with the VA Manager running on each VA server in the set and, through this interface, allows an administrator to use a single system to manage the entire site.
There are two ways an administrator can connect with the VA Server Manager application:. Using an Administrative Web Page: The VA software also includes an administrative web page that uses Active Server Pages to interface with the VA Server Manager service, allowing an administrator to manage the site through a standard web browser.
Returning to FIG. In addition to the service processes, the following components are used on the VA platform. The MSDE database engine is installed automatically as part of the VA platform install, and the recommended tables and initial data are created during the installation routine.
This object is created automatically at start-up by the VA Server Manager and provides a set of application programming interfaces API's that other VA components can use to retrieve configuration information and log data.
In addition, the DBManager object automatically handles version checking, database restoration, and other database management functions. In the preferred embodiment, as illustrated in FIG. These utilities include the following a VA Logging Tool, which is used by the administrator to view and manage system logs. The VA software uses a set of shared directories for storing files necessary for platform operations. In a multi-server implementation, these shares are stored on a central server the same server that hosts the VA Server Manager process and can be accessed by all the systems in the server set.
The shared directories used by the VA platform are described in the table below. By default, this path is c:. Program Files. Conita Virtual Assistant. The service processes that make up the VA platform either can be run on a single server a VA platform server or can be distributed across multiple servers a VA platform server set. A single-server implementation is adequate for small companies that need to support only a few incoming VA calls at a time. For larger companies, however, a server set implementation will be necessary for load balancing.
As the platform's primary server, the Server Set Controller Node will host the following components:. Shared directories that will be used by all the servers in the server set to store logs, utterance files, application files, and user information. In single-server implementations, the lone server is configured as the controller node, hosting the database, web-server, and VA Server Manager process along with all other VA services.
The way a business configures its VA platform will depend on the number of users who will be interacting with the VA application. Such a site could support several incoming telephone lines , allowing up to multiple instances of the VA application to be running simultaneously. For larger sites that need to support many simultaneous VA application sessions, the VA components can be distributed across multiple systems. A large organization may require even more scalability.
The duties of the VA Virtual Assistant platform administrator include the following tasks:. Preparing the server s for installation of the VA platform software. Ensuring that the application software can communicate with the telephone system and other hosts such as a Microsoft Exchange server. Configuring Microsoft Exchange to support VA users. Using the VA management interfaces to manage the systems in the server set, start and stop the VA services, and run VA applications.
Monitoring the platform interfaces and error logs. In order to perform the above duties, a VA administrator needs to have experience with the following software packages:. In the preferred embodiment, a VA platform server system uses two 2 personal computers, each of meets the minimum hardware requirements listed in the table below:. In the preferred embodiment, the following operating system and third-party software are be installed on a server in order to support the VA platform software.
In the preferred embodiment, the prerequisites for installing the SCE on a workstation are listed in the table below:. In the preferred embodiment, the prerequisites for installing the VA Management Console software on a remote workstation are listed in the table below:. Although in general there is no one order required for installing the pre-requisite software packages for the VA platform, the following sequence is generally used when preparing a VA platform server:.
Windows NT Option Pack 4. Dialogic DNA 3. A server's domain should not be changed after the VA platform is installed. For this reason, when installing the VA software on a machine, it is recommended that the server already be properly configured on the domain in which it will be used.
When installing and configuring the Windows NT operating system on VA platform servers, the following steps should be performed:. When partitioning the hard drive s , use NTFS on all disk volumes. During the Select Components phase of the installation, select the Windows Messaging option. If the Windows Messaging option is not selected, or if a server on which Windows NT has already been installed is being prepared, the option can be added later. After the basic Windows NT operating system is installed on the server, the following set of add-on packages should be installed in the specified order:.
When installing the Option Pack, Upgrade Only option should be used. Pack on secondary servers in case Controller Node later needs to be moved to a different server. Internet Explorer Version 5. If a RAID solution is used, it should be properly configured after installation of the operating system on the Controller Node. The VA platform requires up to three different types of telephony boards, depending upon the types of services that will be available.
Telephony hardware is recommended only in the platform's telephony server s. Small installations will likely have only a single machine performing telephony services, though larger configurations may require multiple systems.
This board provides both the interface to the telephone network and the voice processing resources that are recommended for speech recognition. In order to support simultaneous sessions on all 23 available ports, a voice resource board described below is recommended:. A voice resource board provides the extra processing power recommended to support the full simultaneous use of all ISDN PRI channels on the telephony adapter board s.
Generally, an additional 22 voice resources are recommended to support VA sessions on all 23 channels. A Dialogic audio conferencing adapter is recommended for all VA platforms that will support the VA application's call conferencing feature. Three different models of conferencing adapters can be used, depending upon the call traffic that needs to be supported:. If the telephony server is installed without a conferencing adapter, the VA platform software will still function, but the call conferencing feature will not be available.
Before the VA platform is installed, the recommended telephony hardware and software should be first installed and configured. In the machine or machines that have been designated telephony servers for the VA platform, the recommended telephony cards should be installed according to the manufacturer's instructions. After installing the Dialogic hardware in the telephony server s , it is recommended that version 3. When installing DNA 3.
When starting the DNA 3. Consult the local provider for the specific protocols needed. During the installation of the VA platform software, Dialogic-specific data files will be modified by the installation routine. For this reason, there is no need to configure the Dialogic boards before installing the VA platform. The Dialog configuration steps necessary after installing the VA platform are discussed.
In the preferred embodiment, Nuance 6. The Nuance 6. More detailed instructions on installing the Nuance packages can be found in the Nuance documentation that accompanies the installation media. In the preferred embodiment, Version 3.
Install the software according to the documentation included with the product. In the preferred embodiment, all VA platform servers running a VA application should have Outlook installed on them.
The Outlook software is used not by a regular user but by the platform itself to communicate with the Exchange server. When installing Outlook , perform the following steps to ensure selection of the proper version:.
Choose a Custom Install from the main selection menu. On the Features screen, right-click the box next to each Node other than Microsoft Outlook for Windows. From the drop down menu, select Not Available. The account should be a member of the Administrators group. The ConitaVA user name is not hardwired into the VA platform software, so the administrator can, if desired, create a different account name under which the services will run.
The Install Shield application for the platform software will use ConitaVA as a default, so the administrator should be sure to enter the proper user name if a different account is to be used. In the preferred embodiment, organizations installing the VA platform will already be using Microsoft Exchange for their regular email and communication services. In such environments, the existing Exchange server and its user accounts will likely continued to be used, with the VA services added on to them.
In some situations, however, a new Microsoft Exchange platform may be installed along with the VA platform. If so, the Exchange server should be fully installed and configured according to Microsoft's documentation before installing the VA platform software. The default VA application maintains only a small amount of information about each of its users, and the majority of user management functions are performed through the standard Microsoft Exchange interfaces. For this reason, it is recommended that Microsoft Exchange accounts be set up for each person who will also be using the VA application.
New users can be added and old users can be removed after the VA platform is installed and in operation. In the preferred embodiment, in order for the VA platform services to have access to the necessary Microsoft Exchange interfaces, the ConitaVA user account should be given permissions as an Exchange Service Account Administrator.
This configuration is performed through the Microsoft Exchange Administrator application. If the VA platform will support fax services, then the fax provider software should be prepared before installing the VA platform. In the preferred embodiment, the VA platform supports the following two separate fax services, Facsys and Jfax. When installing the software for a VA implementation, an administrator should perform three different types of installations:.
VA Server Install, which installs the application components on a system that will be part of the VA server set. This package includes the add-in interface that will be used to manage VA users from within the Exchange Administrator framework.
This installation should be performed on the desktop systems for each person who will have a VA account. There are two additional types of installations that can be performed if needed within a particular environment:.
VA Application Developer Workstation, which is used to install the VA Studio and other application development components on a programmer's workstation. This package is needed only if a developer will be writing custom VA applications at the site. The Administration Station install is useful, however, for an administrator who wishes to manage the server set from a remote system.
Three different pieces of media can be used for installing the VA platform software. In the preferred embodiment, the general process for installing and configuring a full VA platform implementation is as follows:. Install the VA platform software on each secondary node, if using a multi-system implementation. Configure the platform to run one or more VA applications.
Create VA user accounts with through the Exchange Administrator interface. In many situations—particularly when installing a VA server set for the first time—it may be desirable to install the platform servers in stages. In such a procedure, a single node with all the VA software is installed, configured to run a single VA application, and tested to see whether the application functions correctly—first over the system speakers and then over a phone line.
Then, additional servers can be added to the server set until the full installation is complete. For an installation in stages, the following procedure is recommended:.
Install the Server Set Controller Node software package on a single server. Configure the single VA platform server to run a VA application using a sound card interface. Create one or two VA user accounts for testing purposes.
Test the application to be sure it functions correctly. Test the application to be sure it functions over the phone lines. Once the first server is functioning properly, add in each additional node in succession.
Bring the full VA platform online for general use. The amount of free disk space recommended to install the VA platform components on a server depends on the type of installation chosen for the system.
Approximate space requirements are listed in the table below:. The disk space requirements are for the VA platform software only. They do not include the amount needed for prerequisite packages such as Nuance and AcuVoice. On the Server Set Controller Node, it is recommended that an additional 1 GB of free space be available for the storage of logs and temporary files during VA platform operation. While only MB is recommended for the initial installation of the VA platform software, in the preferred embodiment, because the VA platform software stores temporary speech and log files on the Server Set Controller Node during execution, the amount of disk space used can grow very quickly.
It is recommended that there be one 1 GB of free disk space on the Server Set Controller Node in order to store a full set of speech and log data. For systems with smaller capacity, the amount of temporary data stored can be reduced, but such restrictions will limit the ability of an administrator to monitor the platform and track errors.
This installation should be performed first on the server that will be the Server Set Controller Node and then on each secondary server. Before beginning the VA platform installation, if a multi-node server set will be installed, identify which server will be the Server Set Controller Node. On the server that will be the controller node, perform the following steps to install the VA platform software:.
The Install Shield application executes automatically. Read the introduction and license screens, clicking Next when finished. The Setup Type selection screen will appear. Select VA Server from the setup type list box and click Next. The Select Components screen will be displayed. The next screen will provide a prompt to select the directory into which the VA platform files will be installed.
By default, this directory will be c:. To keep the default destination directory, click Next. To change this directory, click Browse and select a new destination, then click Next. The next screen will ask to install the MSDE database. Select either yes or no, based on the following criteria:. Click Next to move to the user account screen.
If Yes is selected to install MSDE, there will be a prompt for the directory in which the database should be installed. By default, this directory is c:. To change the directory, click Browse, select a new directory, and click Next.
After the database information is selected, the Enter Account Information screen will be displayed. On the Account Information screen, the username and password for the NT account under which the VA software will run should be entered. Click Next to continue. The next screen will provide a prompt for entry of the password for the Conita VA service account. Enter the proper password and click Next.
The next screen will provide a prompt for the name of the Windows NT domain to which the service account belongs. Enter this domain name and click and click Next. Note: All VA servers in a server set and the Microsoft Exchange server with which they will communicate should be located in the same domain. The final interactive screen of the installation process will prompt the selection of the Program Folder in which the icons for the VA platform software are to be installed.
Change the folder's name if desired, then click Next to begin the installation. In most cases, no reboot is recommended after the VA Server installation. If, however, one or more system files were locked by other applications while the installation routine was running, a reboot of the system will be recommended to complete the VA installation, and a prompt will be provided to perform the reboot.
The process for installing the VA software on secondary servers is very similar to that for Server Set Controller Nodes, but there will be no prompt to install the MSDE database because a database is recommended only on the controller node. The full procedure for the VA Server install an a secondary node is as follows:. The Install Shield application should execute automatically.
On the Account Information screen, enter the username and password for the NT account under which the VA software will run. The next screen will provide a prompt to enter the password for the Conita VA service account. The final interactive screen of the installation process will provide a prompt to select the Program Folder in which the icons for the VA platform software are to be installed.
If, however, one or more system files were locked by other applications while the installation routine was running, the system will have to be rebooted to complete the VA installation.
In such a case, there will be a prompt to perform the reboot. The VA platform Install Shield routine generates a log file that is useful for diagnosing a failed installation. The full path to this file is c:. In case of warning or error messages during an install, the log file should be checked first to see whether it contains a more detailed message. During the installation of the VA platform software on the Server Set Controller Node, the Install Shield routine will create two new subdirectories under c:.
These directories contain a web-based tool used for managing the VA platform logs. Although the Install Shield creates these directories, perform the following steps to configure the virtual directories and security permissions for the files. Create two virtual directories under the default web sites and point them to the actual directories created by the install. Give the two virtual directories read and script access. Make default. Remove anonymous access to the two virtual directories.
Set access permissions on the two actual directories to allow access only to the user account s who will be functioning as an administrator for the VA platform. For all sites that will be running the default VA application, the administrator should install the VA Exchange Administrator Extension package on the Exchange server that will be used with the VA platform.
This package inserts a custom add-in into the Microsoft Exchange Administrator application. The add-in is used to manage the Exchange accounts that can be accessed through the Virtual Assistant application. In most cases, the VA platform software will be installed in an environment that has an existing Microsoft Exchange server in use. In some circumstances, however, an administrator may be installing Exchange fresh along with the VA software.
In such a case, the Exchange server should be fully installed and configured before attempting to install the VA extensions. In the preferred embodiment, the Microsoft Exchange server software runs on a separate machine from the VA platform software. At smaller sites, it is possible for Exchange and the VA platform to occupy the same server. Before beginning the installation of the VA Exchange Server Extension package, the following tasks should have been completed:.
The Microsoft Exchange server on which the VA extensions will be installed has been fully installed and configured. An Exchange administrative user's account has been set up for the person who will act as the VA administrator. Regular Exchange user accounts have been set up for each person who will be a Virtual Assistant user.
Before beginning the installation, the Exchange organization, site, and container to which the extensions will be added should be determined, as well as the name of the Add-In shared directory for the Exchange server. The process for installing the VA extension on a Microsoft Exchange server is as follows:. Skills are accessible and easy-to-follow with new Learning Outcomes that outline the skills covered in each lesson and larger full-color screen images that reflect exactly what readers should see on their own computers.
Each unit begins with a brief overview of the principles of the lesson and introduces a case study for further application. The Enhanced Edition includes a new Student Success Guide that not only helps students prepare for success in their class, but also guides them through the use of OneNote to facilitate that.
The Enhanced Edition also features new and updated appendixes that offer a variety of opportunities to explore cloud computing and other developing applications in more depth. Skills are accessible and easy-to-follow thanks to the Illustrated Series' hallmark 2-page layout, which allows students to see an entire task in one view.
New Learning Outcomes outline the skills covered in each lesson, and larger full-color screens represent exactly what students should see on their own computers. Our expert industry analysis and practical solutions help you make better buying decisions and get more from technology.
Sku: Condition: New. Qty Available: 1. Buy It Now. Add to cart. Sold by jhsbooks About this product Product Information FontPage basics: installing FrontPage , how to create your first website, inserting images and customizing your pages, adding forms and interactivity, inserting DHTML and other built in FrontPage components, database connectivity features using FrontPage and Microsoft Access.
Get results with FrontPage —today! Learn from real-world examples and downloadable code Create, organize, build, and manage a FrontPage Web site! FrontPage delivers awesome Web development power to mere mortals! Now, learn FrontPage hands on from the world's 1 independent expert-through real-world examples and projects you can view on the corresponding Web site. You'll master every phase of the FrontPage Web development process!
Tiffany K.
0コメント