I was talking to a customer today who had an overhaul project for his Web site.
He had made his choice to redevelop his site, and he had understood some of the advantages of WEBDEV.

However , I realized he thought he was dealing with a classic tool, with a whole set of restrictions, and hundreds of lines of codes to write.
He wanted to proceed in two stages, first build a mock-up of his site, then develop it. He was wondering what tool he could use to build the mock up.

Well, with WEBDEV, there's no need for a complementary tool because the whole life cycle is covered.
The developer can directly build his mock-up with WebDev: place his text edit controls, his images, his buttons,..., and in sum define his whole interface.

And, above all, without having to write a single line of code, he can have a working site, with the corresponding automatic input masks, action buttons, etc.

Next, thanks to WLanguage's power and ease of use, he can add his procedures with some lines of code: no HTML code, Javascript or anything else to write.

In the case of an Intranet site, the developer can even integrate user groupware rights in just one click, with no code.

For all of those who are constantly on the move, it might be interesting to have all your applications and data on a USB Flash Drive.
This lets you avoid moving around with a laptop, and run the application from any computer.
With WinDev, it's extremely easy to deploy an application and its data on a USB flash drive, in other words, to create an application that you can run directly from the USB flash drive.

If you have an Oracle database, you're probably asking yourself how you will be able to access it from WINDEV, what is the development method, the architecture you have to use, the performance level, etc.?

Follow the guide

WINDEV lets you build all sorts of applications that access Oracle databases. Applications created with WINDEV (and WEBDDEV) can be connected to Oracle (version 7 and above) via ODBC, OLE DB, and also via “Native Access”.

Native Access means that you don't have to configure or install drivers or providers between the client and the server. But above all, it means faster access and applications that fully exploit Oracle's possibilities.

Oracle's “Native Access” simply relies on Oracle's client layer.
The setup is automatic and you have access to all the functions of the WINDEV and WEBDEV environments.

In terms of programming you can have access to Oracle databases with SQL functions as well as the HRead* functions (compatibility mode with Hyper File).

Have a look at the “Native Access” possibilities in this address:
http://www.windev.com/nativesaccess/ANOracle.htm
We obviously recommend “Native Access” if performance and integration are your priorities.

On a performance level, the client feedback shows complete satisfaction.
You can read Quiksilvers' testimonial. They relied on WINDEV for their CRM and they use Oracle data. Over 550 million records and counting!

PS: WINDEV is also known and recognized for its access performance to Hyper File databases (databases included in WINDEV, and WEBDEV).
In addition to its power, Hyper File is also known and appreciated for its free deployment with applications in local, network, Client/Server (Windows and Linux) and Mobile.

Often I get asked the question about how to use an IPBX through WINDEV...
Here's some information on the subject.

First of all, what's an IPBX?
In the telecommunications industry an IP BPX (also called an IPBX) is a system used in companies to ensure call routing using the Internet Protocol (IP), internally on the company's local network (LAN) or on its external network (WAN).

Concretely a PBX links a company's phone extensions to the public phone network.
PBXs have evolved and now they let you manage voice over IP (VOIP). They're now named “IPBX”.
An IPBX can manage hundreds or even thousands of calls in a company.

How does it work?
All the company's phones are linked to the network, simply by classic RJ-45 network cables.
Each phone is identified by an IP address.
All the phone calls pass through the IPBX, whether they're incoming or outgoing calls.
An IPBX simply establishes the correspondence between an phone number and an IP address.
A computer can communicate with the IPBX thanks to a TAPI driver and therefore manage phones.

How does it work in WINDEV?
Thanks to WINDEV's telephony functions, you can make your applications interact with an IPBX.
This way you can process different events such as:

• Detecting an incoming call and knowing it's phone # (tapiListen function)
• Dialing a phone # from an application (tapiDial function)
• Retrieving the call info (the phone # with the TapiCallerId function )
• Detect when the call was hung up (tapiCallIsOver function)

Conclusion
WINDEV's telephony functions let you execute several procedures:

• Telephone exchange supervision
• Recording a conversation
• Creation a vocal server
• Call monitoring (call schedule statistics, call duration)
• Knowing at any given moment the state of line occupation
• Etc.

WINDEV's telephony functions
These are the telephony functions that WINDEV offers.
You will notice that these functions are simple, clear and concise!

tapiCallStart
Returns the date and time a call started (incoming or outgoing).

tapiCallIsWaiting
Indicates if there's a call waiting.

tapiCallIsBusy
Tells you whether the number called is busy. This function can only be used with the current outgoing call.

tapiCallEnd
Returns the date and time of the end of call

tapiNoAnswer
Tells you whether the call was answered.

tapiStop
Forces a pre-recorded message to stop playing (tapiPlay function

tapiCapability
Returns the characteristics of a telephony peripheral.

tapiLineDial
Dials a phone number for a voice line and chooses the device.

TapiCallDuring
Returns the call's duration.

TapiRecord
Records the current communication as a .WAV file.

tapiError
Specifies if the last tapixxx function (telephony management functions) has returned an error in the TAPI module.

tapiCompleteTransfer
Transfers a call (with ability to retrieve the call).

TapiStopCallDetection
Stops the incoming call listening service, which started when the tapiListen function was called.

tapiPlay
Plays a sound file (.WAV) for the specified line.

TapiDeviceList
List of the TAPI 2.0 compatible devices installed on the current station.

tapiHold
Puts a call on hold. This call will remain on hold until the tapiUnhold functions is called.

TapiCallerId
Identifies the calling number (the one making the call).

TapiCalledID
Identifies the telephone number called.

TapiSendKeyç
Simulates the use of the phone keys.

tapiOrigin
Lets you find out where a call originated from (incoming call, outgoing call, etc.)

tapiDevice
Selects the TAPI device that will be used by default.

TapiHangUp
Hangs up a phone line opened with the tapiDial function or the tapiAnswerCall function.

TapiAnswerCall
The modem picks up and the call can be processed by the modem (using an answering machine for example).

tapiunhold
Retrieves a call put on hold.

TapiKeyPressed
Gives you the history of the keys pressed on the telephone pad.

tapiBlindTransfer
Performs a "blind transfer". The call cannot be retrieved.

The benefits of unit tests are systematic and obvious.
Recently an IT manager was telling me about his experience. His team consists of 12 developers and 2 project managers. Before, 3 engineers dedicated themselves to testing applications.
With an average project of 400 windows, the time dedicated to testing before the release of a new version was of 3 weeks.
Since they started using WINDEV unit tests, a version's test validation time has gone down to one or maybe 2 days tops!
The team is more responsive if a regression is detected.
The gain is obvious, it changes the team's life and it's more satisfying for them. They can now concentrate on more creative tasks.

Here's how to do it!
When you're developing and integrating new features, you have to make changes in procedures and windows whose good performance has been certified over several versions. These procedures and windows are used pretty much on a daily basis by your users and clients. Therefore it's necessary to pay special attention to their smooth functioning, track any regression that a new version might have brought in and reduce any defect related costs.
WINDEV brings us a precious help in this procedure aiming at making our new versions more reliable, thanks to its “Unit Test Editor”.

The Unit Test Editor lets you save, from the creation of your windows and procedures, test scenarios in an intuitive manner.
Let's take the example of a window:
To start saving a test, all you have to do is click on the “Save” icon on the WINDEV toolbar.




Your window is now executed interactively, and all you have to do is perform actions (keyboard, mouse) that you wish to incorporate into the test.
To stop saving the test all you have to do is close the window.
WINDEV now generates the WLanguage code that corresponds to your actions, the test scenario.
You will find the command EmulateMouse for mouse actions, EmulateInput for keyboard manipulations,...
At any time, you can replay the test scenario and WINDEV will tell you in the test report if the test has been validated or not.

Of course, WINDEV also makes regular suggestions to run your complete test scenario (reintegration in the SCM, creation of the .exe, ...) to verify the overall quality of your application.
Thanks to WINDEV, this is how you can deploy the new versions of your applications with peace of mind.
You will be able to meet deadlines providing more reliable applications.

Regardless of the technical aspects and the technologies that can be found in the product, the reliability of applications developed in WINDEV is the consequence of its architecture.

I'd like to remind you that WINDEV was based on the principle of “Let's not re-invent the wheel” each time we develop.

Most of the procedures and behaviors of applications won't be defined in WINDEV through “code”, but through “checking options”.

• Therefore there's no risk of bugs. The features are deployed by millions of copies throughout the world, therefore they benefit from this to offer great reliability.
• In addition, you can be sure that the features will satisfy needs. These features were developed by experienced teams, and they benefit from the feedback of millions of users all over the world. No mater what the skills of a developer in you company are, there's little chance that he'll reach the feature and reliability level of an integrated module.

Here are some examples of procedures that can be defined “by clicks” just by answering some questions in a window or assistant. You can find hundreds of these in WINDEV, and these are just some of them. Not one of these features needs a single line of code (“Zero code” technology).

• Creating a “live-update” setup for an application, in other words, one that suggests an update for each new version of the applications through the company's network or Internet
• Translation an application into several languages
• Managing the “user feedback”: pointing out bugs, suggestions...
• Changing the database of an application (for instance going from SQL Server to Oracle)
• Creating a window (form) with an amazing interface
• Recompiling in 64 bits
• Creating reports: to be viewed, to be printed, paper or PDF
• Creating bar codes

Here I'll mention some of the features that can automatically be found in an application:

• Exporting to Excel or OpenOfficeCalc
• Exporting to Word or OpenOfficeWrite
• Exporting to XML
• Searching the window
• Adding a total or average to a table
• Resizing a combo box
• Adding an automatic validation timer to a button (in can validate itself after a certain amount of time)
• Spell-check
• Display a field's entry log
• ...

Simply imagine: Any developer that uses WINDEV immediately benefits from a whole set of high level features, features that are for the most part exclusive.
The industrialization of the development process is automatic, not only without restrictions, but also in terms of development time, budget and reliability.

Benefits:

• The development time is reduced to almost zero because of the numerous features
• Bug risk is eliminated (therefore there is higher client satisfaction, less maintenance, therefore a more comfortable budget and more resources available for new projects)
• Applications can have a richness of features like no other