4D V13

warning: file_get_contents( [function.file-get-contents]: failed to open stream: HTTP request failed! in /var/www/ : eval()'d code on line 4.

Web Get Body Part

Called in the context of a Web process, the WEB GET BODY PART command parses the "body" of a multi-part request.

This demonstrates how to use this command to get a file via the browser.


Download for Windows or Mac

Webkit Integration

As of 4D v13, the Web Area function of 4D integrates the Webkit rendering engine, using the same engine in under both Windows and Mac.

As a result, Web pages will have the same appearance and behavior on both platforms, ignoring Internet Explorer on Windows.


This demo shows how web interfaces look under the Webkit rendering engine.


Download for Windows or Mac

Windows Enhancement

4D v13 provides a new parameter for SET WINDOW RECT.

This allows you to move a specified window to the passed coordinates and set it as a foreground window. The command now accepts a * parameter to keep the window in the background.



Download for Windows or Mac

XPS Print Preview

4D supports XPS Print Preview under Windows.

This "How Do I" gives you an example of a direct print preview.


On Windows, if a print job is launched with the Print Preview checkbox selected, 4D redirects printing to the Microsoft XPS viewer.


Please note: Under Windows XP, Microsoft's .Net framework is required. 


Download for Windows or Mac

Enhanced list boxes

The list box is a key component to any business application. When data is the most vital part of a solution, viewing and organizing it in a meaningful and efficient way is critical to its ease-of-use.

List boxes allow you to present data however

Webkit integration

From its very early days, 4D has been committed to cross-platform equality. And with the growing use of the Web as a platform in and of itself, 4D’s Web Area has been a popular method of incorporating Web-based technologies such as HTML5, CSS and JavaScript directly into your applications.

Earlier implementations of Web Area were sometimes limited by each platform’s native browser engine, namely Safari on Mac OS X and Internet Explorer on Windows. The integration of the open source Webkit engine into the Web Area guarantees HTML compatibility across platforms.


Next generation HTTP server

The multithreaded server is much more than a means of serving up Web pages.

It has long served as one of many ways of making your application data available to others, and as of 4D v13 it has been further modernized to bring more capabilities to developers and users alike:

  • Full Web standards support
  • Improved cache management
  • Native GZIP support, with automatic and programmatic compression
  • A new fully-threaded architecture designed for higher scalability


Session handling

Expandable HTTP client

An expandable HTTP client gives you access to more data.

Leverage HTTP to access external data
Your app can take advantage of the HTTP client to retrieve data from any HTTP server – beyond Web and Web services. Use the HTTP client as a go-between from one application or function and the world of third-party data and services available over HTTP.


A lighter, slicker HTTP client
Use less code. Use it as a proxy! With the new HTTP client, you can even build your own synchronization mechanism based on HTTP, no matter what the server is.



Look deep inside your code with introspection features, gaining insight on your development.

Code introspection
The day hasn’t quite come where code can fully generate and maintain itself, but you can be confident in the integrity of your development efforts thanks to powerful new code introspection features.


Externalized application settings

Application settings and preferences can now be stored external to your 4D application’s primary structure (e.g. the size of the database cache, HTTP port number, etc.).

This allows for smoother upgrades whenever you update your solutions, especially on large-scale deployments that have numerous users.