By using new introspection commands like METHOD GET PATHS, METHOD GET CODE, FORM GET PROPERTIES, and FORM SCREENSHOT we've been able to create an organized HTML folder that contains all of our application's source code as well as all the form pages. And it took less than three minutes! (In our case, it's 1800 methods, 600 form pages, and 3000 object scripts.) Filters allow us to target the necessary modules and thus make folders for the necessary services. We've even converted some of our 4D 2004 and 4D v11 SQL just to have this folder to be ready for the move to 4D v13.

With our solutions being essentially Web-based and exchanging data via HTTP, the new HTTP server and HTTP_Request commands in 4D v13 provide tangible improvements that in our testing have made our products faster and more efficient. These first impressions lead us to believe we'll be putting 4D v13 into production as soon as possible!

We started a new, completely Web-based project with 4D v13. The rewritten Web server brings some marked improvements: On one hand there's the performance thanks to its multi-process capability, but also new features as well, like new tags and commands. Furthermore, the integration of an HTTP client, in addition to providing us with new possibilities, freed us from the use of external tools like cURL. The development interface is measurably more comfortable with its new features like predictive type, comment tooltips, etc. We are thus truly enthusiastic about this new version that we're discovering bit by bit and that gives us even more confidence in our choice of 4D as our platform.