Text Services Framework
- other webpage : http://windowssdk.msdn.microsoft.com/en-gb/library/ms629032.aspx
Text Services Framework
Overview of text services framework for theTablet PC.
When the Text Services Framework (TSF) is enabled on a control with a PenInputPanel object attached, it allows the PenInputPanel object to insert text directly. If the control does not support Text Services Framework (TSF), the PenInputPanel object must resort to using the SendInput function to insert text.
The ability to insert text directly becomes very important on East Asian systems, where using the SendInput function can produce incorrect characters.
TSF provides an interface for correcting recognition errors enabling the end user to correct, rewrite, or even dictate the proper text.
TSF is enabled by calling the EnableTsf method with the enable parameter set to TRUE.
[C#]
Copy CodePenInputPanel thePenInputPanel = new PenInputPanel(theControl);
//...
thePenInputPanel.EnableTsf(true);
A PenInputPanel object attached to a InkEdit Read the rest of this entry »
Telephony Application Programming Interface
The Telephony Application Programming Interface (TAPI) is an API, which enables PCs running Microsoft Windows to use telephone services. Different versions of TAPI are available on different versions of Windows. TAPI was introduced in 1993 as the result of joint development by Microsoft and Intel. The first publicly available version of TAPI was version 1.3, which was released as a patch on top of Microsoft Windows 3.1. Version 1.3 is no longer supported, although some MSDN development library CDs still contain the files and patch.
With Microsoft Windows 95, TAPI was integrated into the operating system. The first version on Windows 95 was TAPI 1.4. That version was not very different from 1.3. The biggest enhancement of TAPI 1.4 was support for 32-bit applications.
The TAPI standard supports both connections from individual computers and LAN connections serving any number of computers.
TAPI 2.0 was introduced with Windows NT 4.0. Version 2.0 was the first version on the Windows NT platform. It made a nice step forward by supporting some ACD and PBX specific functionality.
In 1997, Microsoft released TAPI version 2.1. This version of TAPI was available as a downloadable update and was the first version to be supported on both the Microsoft Windows 95 and NT/2000 platforms.
TAPI 3.0 was released in 1999 together with Windows 2000. This version enables IP telephony by providing simple and generic methods for making connections between two (using H.323) or more (using IP Multicast) computers and now also offers the ability to access any media streams involved in the connection.
The release of Windows XP included TAPI 3.1. TAPI 3.1 supports the Microsoft Component Object Model and provides a set of COM objects to application programmers. This version uses File Terminals which allow applications to record streaming data to a file and play this recorded data back to a stream. A USB Phone TSP (TAPI Service Provider) was also included which allows an application to control a USB phone and use it as a streaming endpoint.
The Telephony Server Application Programming Interface (TSAPI) is a similar standard developed by Novell for NetWare servers.
[edit]
TAPI 2.x vs TAPI 3.x
It is a common error to think that TAPI 3.0 (or TAPI 3.1) is the “improved” version of TAPI 2.x. The fact is that TAPI 2.x is written in C/C++ so that it could be accessible from C/C++ or unmanaged code. On the other hand, TAPI 3.x is designed with the COM (Component Object Model) interface, with the intention of making it accessible from managed code (.NET environment). TAPI 3.x has a slightly different set of functions and does not neccessarily support all functionalities that TAPI 2.x does. One of the most noticeable differences between those two are the supports to Phone class (speakerphone volume control in particular), for that TAPI 2.x appears to be the better choice for programmer.
[edit]
TAPI compliant hardware
Telephony hardware that supports TAPI includes most voice modems and some telephony cards such as Dialogic boards.
TAPI
|
TAPI[태피]는 전화나 비디오폰을 통해 사용자나 컴퓨터가 전세계 어디에 있는 사람들(또는 전화에 연결된 자원들)과도 통화를 할 수 있도록 해주는 프로그램의 표준 인터페이스를 말한다. 자신의 컴퓨터에 TAPI가 장착되어 있고, 관련 응용 프로그램과 하드웨어 설정이 올바르게 되어있다고 가정하면, 다음과 같이 해 볼 수 있을 것이다.
인텔과 마이크로소프트가 협력하여 개발한 TAPI는 윈도우95/98 및 NT 운영체계에 포함되어 있다. TAPI를 사용하면, 프로그래머들은 보통의 PSTN, 디지털 ISDN 그리고 사설교환기 등을 포함한 다른 전화 시스템들에 대해 자세한 내용을 알지 못하더라도 된다는 장점이 있다. 각 전화시스템 하드웨어 제공자 (예를 들어 모뎀 제작자나 ISDN 카드 제작자)가 자신의 하드웨어와 직접 접속할 수 있도록 특유한 소프트웨어 드라이버를 제공한다. |
|
TAPI는 다이얼링과 통화 단절에 관한 고급 인터페이스를 제공한다. 다이얼링을 위해 ATDT 스트링을, 전화를 끊기 위해 ATH 스트링을 인코드하는 대신, 프로그래머는 보다 간단한 “function call”을 사용하면 된다.
TAPI는 응용프로그램 인터페이스에 추가하여, 드라이버 소프트웨어를 작성하는 하드웨어 공급자들을 위해 SPI (Service Provider Interface)를 포함하고 있다. TAPI DLL이 API를 SPI에 사상시키고 입출력 량을 조화시킨다.
