BLOGS

4D BLOGS - AUGUST, 2011

11/21/2012

4D has announced the immediate availability of 4D v13.2, the latest version of its flagship product line.

 

Read more

09/26/2012

The fourth Hotfix release for 4D v12.4 is now available to 4D Partners.

Read more

09/20/2012

The first Hotfix release for 4D v13.1 is now available to 4D Partners, with particular interest for users of Mac OS X "Mountain Lion."

 

Read more

09/17/2012

The third Hotfix release for 4D v12.4 is now available to 4D Partners, with special interest for users of Mac OS X Mountain Lion.
 

Read more

09/06/2012

The second Hotfix release for 4D v12.4 is now available to 4D Partners.

Read more

08/31/2012

Following up on my last blog post, and also on some of the information I presented in the 4D Summit 2011 Pre-Class, I've updated one of my systems to an Intel 7-series motherboard and benchmarked a RAID 0 SSD array. Read on for the results!

Read more

08/20/2012

Exciting news this week as Intel has announced (via journalists apparently, I can't find an official posting) that the TRIM command is now passed though to RAID 0 SSD arrays.

Read more

08/02/2012

After a number of partial communications regarding compatibility between 4D and Mountain Lion since the release of the operating system last week, we are now able to conclude our various tests.

 

Read more

07/25/2012

Mountain Lion has just joined the club of the most popular felines in the world, and those of you who won't wait a single minute to install Mac OS X 10.8 will discover rather quickly one of the new features of the operating system called Gatekeeper.

 

Gatekeeper is designed to protect users from malicious downloads and by default blocks opening executables that haven't come from the Mac App Store or that aren't signed with a certificat formally identifying the developer via Apple.

 

Read more

07/13/2012

Today I posted an update to the CodeExport GitHub project to remove its one and only plug-in dependency (for compile-time at least). Thanks to Kirk Brooks for pointing out the problem! Read on to find out what I did.

Read more