2011

  • December 7, 2011

    All C/C++ compilers predefine macros indicating the target processor, operating system, language features, compiler name and version, and more. Cross-platform code can use #if/#endif to wrap OS-specific #includes (such as <Windows.h> vs. <unistd.h>), compiler-specific code (such as inline assembly), or processor-specific optimizations (such as SSE instructions on x86). Macro names are not standardized and nor are methods to get the compiler to list them. This article surveys common desktop and server application compilers and shows how to list their predefined macros.

  • November 2, 2011

    This part 4 of 4 articles continues a component by component review of problems, workarounds, and special features for the classic Java Swing CDE/Motif look and feel. Example images are included along with UIDefaults values, color swatches, and icon images.

  • October 10, 2011

    This part 3 of 4 articles continues a component by component review of problems, workarounds, and special features for the classic Java Swing CDE/Motif look and feel. Example images are included along with UIDefaults values, color swatches, and icon images.

  • September 6, 2011

    This part 2 of 4 articles continues a component by component review of problems, workarounds, and special features for the classic Java Swing CDE/Motif look and feel. Example images are included along with UIDefaults values, color swatches, and icon images.

  • August 3, 2011

    The classic Java Swing CDE/Motif look and feel recreates the beveled buttons, gray color scheme, and light-weight design of the X11 window system's applications circa 1990. This article is part 1 of 4 and provides a component by component review of problems, workarounds, and special features of Java's CDE/Motif look and feel. Example images are included along with UIDefaults values, color swatches, and icon images.

Syndicate content
Nadeau software consulting
Nadeau software consulting