BLOGS

4D BLOGS

warning: file_get_contents(http://www.telize.com/geoip/54.227.127.109) [function.file-get-contents]: failed to open stream: HTTP request failed! HTTP/1.1 404 Not Found in /var/www/www.4d.com/docs/includes/common.inc(1762) : eval()'d code on line 4.
14/10/2010

Yesterday was a day full of exciting demos that the Summit team was eager to present.

Read more

13/10/2010

Preparation for the 4D Summit involves assembling many important pieces.  From picking out critical features to show off, to pleasantly surprising the attendees as the day moves along, getting it all together is no easy task.

Read more

13/10/2010

Thanks to a new HTTP API providing database-level communication between 4D v12 and third-party applications, iPad, iPhone and iPod Touch users can automatically synchronize data both ways between their devices and 4D over wi-fi and 3G.

Read more

12/10/2010

And we're off! The gates are open and our eager attendees have begun to arrive! The earliest-of-earliest were here with a purpose: Today's scheduled Pre-Class, 4D v12 In-Depth.

Read more

12/10/2010

As of the weekend, the 4D crew has been in San Diego, putting polish on sessions, events, and – of course – the eagerly anticipated keynotes. We're also working hard shooting and editing video to bring you the latest proceedings from the Hard Rock Hotel as they happen.

Read more

07/10/2010

4D is pleased to announce the availability of 4D v11 SQL Release 8 (11.8). As a service release, this incremental upgrade builds upon previous releases to bolster stability and reliability of the 4D v11 SQL product line.

 

Read more

14/09/2010

After the other day's country stroll in the Method Editor, let’s spend a few minutes on the ListBoxes. Because among other new major (1) features of 4D v12, ListBox improvements are definitely major-major (1 too).


Let’s start with a short reminder, kind of A ListBox History.

Read more

14/09/2010

4D is pleased to announce the availability of 4D v11 SQL Release 7 Hotfix 1.

Read more

14/09/2010

 

This blog post is the final in a four-part series written in French in September 2009.


To finish this series, here are a few items allowing us to further appreciate the usefulness of timestamps.

 

Read more

10/09/2010

This blog post is the third in a four-part series written in French in September 2009.

 

In previous posts we’ve seen the use of a timestamp based on a long integer, which brings us much in terms of efficiency, saving space and performance. Let’s now look at how to code the conversion of a date and time into a timestamp and vice-versa.

In the end, the timestamp is calculated by the number of seconds compared to a reference date. To keep it simple, we’ll use January 1st, 2000 as our reference date. This allows us to go up until 2068. Why 2068 and not 2136, assuming that 136 years corresponds to 4 billion seconds? Because long integers in 4D are signed, we must remember that the value 0 is in the middle of the range of possible values. As a result, our timestamps allow us to navigate between the years of 1932 and 2068. Of course, there’s nothing preventing you from shifting your reference date to cover your needs better.

Read more