I learned about jq yesterday. As their web page says, “jq is like sed for JSON data – you can use it to slice and filter and map and transform structured data with the same ease that sed, awk, grep and friends let you play with text.” (I learned about it via this tweet by Grzegorz Kossakowski, who I met at the Scala Summit in 2013.
Android FAQ: How do I start the Android command line tool (so I can interact with my Android emulator or device)?
You start the Android command line with the adb shell command:
$ adb shell
This makes at least two assumptions:
- You have the Android SDK installed.
- You have an Android emulator (or physical device) running.
When you start the
adb shell, you'll see a very simple prompt that looks like this:
Function Point Analysis software tools: As a brief announcement, I've just created a free Function Point Analysis software application at Sleetmute.com.
If you're not familiar with Function Point Analysis (FPA), it is an industry standard technology that lets you determine the "size" of a software application. What "square feet" is to a house, "function points" are to a software application.
Continuous integration is a key to a quality build process for any multi-developer software development project. I can't say it much better than the way Martin Fowler describes it, so I'll just include a portion of his summary here:
Continuous Integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily - leading to multiple integrations per day.
Here's a page that lists a bunch of cost estimating tools for software development.
Here's a link to a tool named JSmooth that lets you create Windows executable files from standard Java JAR files. It looks like this can make the installation process on the Windows platform much more friendly.
I've finally finished creating my first two JBuilder OpenTool projects. They are very simple, but time is scarce, so the development process was drawn out. Here are quick links to the two tools:
Keith Wood has written a book about the JBuilder OpenTools, appropriately named "Inside the JBuilder OpenTools API". Here is a link to his site, and here is an even more direct link to the JBuilder OpenTools code samples he has on his site.
I recently started creating a few OpenTools for JBuilder. One of the instructions you see when you first start creating an OpenTool is that you need to modify your JBuilder classpath during OpenTool development so the classpath includes the location of your OpenTool files. But, the instructions I found were for old versions of JBuilder (that were no longer valid), which leads to the question "How can I modify the JBuilder
CLASSPATH to recognize the location of my custom class files?"