Chrome and firefox blacklist webgl on certain setups, but you can force-enable it. On chrome, put about:flags in your urlbar. As well as being able to enable webgl, there are many other goodies there. On firefox, put about:config in your urlbar, search for webgl, and enable the force-enabled option. Your system will either crash, freeze or display an endless webgl forest…
If you want to convert png images to jpeg, you should use the following:
Code:
mkdir jpegs; sips -s format jpeg *.* --out jpgs
If the png images were generated using screen capture, you can set the default osx screen capture format to jpeg, rather than png using this command:
Code:
defaults write com.apple.screencapture type jpg
Then restart your computer for the change to take effect. To revert back to the default png format, use “defaults write com.apple.screencapture type png”.
Having been led to believe that future versions of the Mac OS X native GUI’d Java programming language might just be remote possibilities, it now turns out that Apple is more than willing to release its current Java JDK code to Oracle/Sun, including, most importantly, its Aqua-based GUI code.
This means that future versions of the Java programming language will STILL be available for the Mac and that these versions will maintain a Mac-native GUI look-and-feel, and NOT fall back on a non-Mac X11 display.
Another potentially positive side-effect might be that Java releases on the Mac may not lag behind other releases quite as much as they have done, previously.
Part of Apple’s reasoning on working with Oracle’s OpenJDK might be to throw more weight behind Oracle’s patent infringement case aimed at Google’s modifications to the Java language within their Android-based Dalvik Java bytecode conversion layer.
import org.junit.runner.RunWith;
import org.junit.runners.Suite; @RunWith(Suite.class)
@Suite.SuiteClasses({ investmentTests.class, catalogTests.class, markerTests.class })
public class AllTests { // why on earth I need this class, I have no idea! }
Joe Ocampo provides an overview of setting up an Java-annotation-based Test Suit under JUnit 4.
The most striking point appears to be the [Java compiler imposed] requirement to tie the annotations to a Java class, which itself maybe empty (it itself needs nor contains Java code). Other than this small overhead, this construct appears to perfectly well substitute previous JUnit test suite definitions.
Having installed git-core (‘sudo port install git-core’) on Mac OS X, I couldn’t for the life of me understand why ‘git svn clone’ wasn’t working (I’d used this command earlier in the day on an Ubuntu 9.10 machine at work.
I man’d ‘git-svn’ and the docs were there. ‘which’-ing git-svn gave me nothing. Turns out, via ports, that you have to add a ‘+svn’ argument to the ‘sudo port install git-core’ command.
MacPorts is doing work right now as I writethis, should have git-svn running on OS X soon, just in time to syphon of some Sourceforge and Google code projects and histories (no-404’s required here, I’m afraid).