Skip to main content

Livin the Java Life

As a start for this blog, this is a video.

Comments

Post a Comment

Popular posts from this blog

C#: How to add the C# compiler command utility (csc.exe) to the system Path?

Doing .NET development does not necessarily assume using the holy Visual Studio IDE. Every now and then, you need to code some simple piece of software that does not require a factory (read: Visual Studio). Personally, I like to use Vim within Windows PowerShell to create/edit C# files rapidly, that also means that I need to compile and build my C# files within the command line. Having Visual C# installed on your PC, does not mean that the C# compiler is ready to be used outside of Visual Studio (within the command line for example). You have to manually add the path to the C# compiler (csc.exe) to your system or user environmental variables. Just follow along: 1- On Windows 7, click on the Start menu launcher, right-click on Computer , click on Properties . At the left of the window that appears, click on Advanced system settings . 2- At the bottom of the System Properties dialog, click on Environment Variables . 3- In the Environment Variables dialog box, click on the New ...
Post a Comment
Read more

Quick How To: Improving NetBeans GUI rendering on Linux

A lot of developers that like to use the NetBeans IDE on top of Linux complain about its ugly GUI rendering, especially fonts rendering. NetBeans requires the Java Development Kit (JDK for short) to run, and bad rendering for Swing based GUIs is due to the fact that Linux distros chip with OpenJDK as the default JDK (almost all of them), which means no anti-aliasing for GUI and fonts rendering is enabled by default. The solution is very simple, though. We can make OpenJDK render Swing based GUIs with anti-aliasing enabled by setting the right option in the  _JAVA_OPTIONS   environment variable.  In a Terminal session, type the following command:  export _JAVA_OPTIONS="-Dawt.useSystemAAFontSettings=on" Almost done. To make the command global (that is, we don't have to issue the same command on every system session) we can add it to our   ~/.bash_profile . That's it. If you can make this tip better, feel free to add a comment below.
2 comments
Read more