Hints for using the first two Android training guides with Android Studio 2.0 and suggestions for extending your first app to programmatically check locale, use log statements, use screen orientation to test different layouts, and create a quick run-time build-version test using the Snackbar message.
As the title suggests, this article is for developers who are new to the Android development platform. You need some knowledge of markup languages, but don’t have to be an expert in XML. It’s great if you know Java, but as long as you’re familiar with other programming languages, you can build an Android application. Of course, you also need Android Studio 2.0 and the latest SDK.
The Internet has no shortage of resources for beginning Android developers, but I like the training guides on the Android developer website because they are thorough and let you jump right in and start coding. There are eight Getting Started guides, beginning with Building Your First App and including guides for supporting different devices, building a dynamic UI, and using system permissions. (More experienced developers may like the 19 advanced educational categories, including writing for wearables and best practices for performance and security.)
Continue reading “Building Your First App with Android Studio 2.0” →
Sorry for the repetitive title, but Apache Taverna is preparing a release that will include the Taverna Commandline Tool, or is it Command Line Tool, or Command-Line Tool? Or just Command Line? Now you see the problem. The name for the tool is different throughout the documentation. Not good.
The project lead, not a native English speaker as it turns out, requested that those of us who are native English speakers weigh in on the correct name for the tool. Challenge accepted. How hard can this be? I know compound adjectives are frequently hyphenated when they modify a noun (think, Red-headed woodpecker), but maybe there is a different software-development convention for this particular term?
First, look online
It turns out there is some inconsistency in the online use of command line tool versus command-line tool. First, I found some examples without hyphens: What is the Command Line Tools Package? and Top 10 Command Line Tools. Then I found a different use, from Wikipedia, that was hyphenated: Command-line interface. But the article has an “issues” flag and, oh yes, it’s Wikipedia; not a good academic reference. I next found Command-Line Reference from Microsoft – with a hyphen. And then I found another from Microsoft, this time without a hyphen: Using command line tools for networking information. And finally, two more from Microsoft – with hyphens: Windows 7 command-line tools and programs and How to create a command-line toolkit for Windows. It seems like the hyphens have an edge, but I wanted a more definitive answer. Continue reading “Commandline Tool? Command-line Tool? Command Line Tool?” →
I was mesmerized by the abundance of resources for new Apache Software Foundation (ASF) committers. As a result of this bounty, it took more time than I expected to make my initial commit. The process now seems straightforward, but way back, say, 24 hours ago, things were much fuzzier.
Two resources are key. If you’ve watched Rob Weir’s video tutorial and read the Get Started Editing a Page link in the CMS Reference, good for you! You are ahead of where I was. These references are probably good enough for most people, although one important point is missing: The copy I was editing did not match the live web page. I needed to update my local version before editing, which sounds obvious now, but that’s because I finally understand how the process works. Continue reading “ASF CMS Editing Hints for New Committers” →
Using Simple Git Commands to Tame Website Updates
In my last post, I talked in general about how I use Git to provide version control for my website. In this post, I’ll describe the simple Git commands I use to manage changes to my website.
Simple Example: Edit a File
I have a master version of my website that I push via FTP to a web server. I also have a development version of my website that I use to test changes before deciding to take them live. Git manages those versions seamlessly so I can concentrate on the changes. Here is a typical exchange: Continue reading “Making Changes Without Fear” →
TL;DR. Git provides better control of website changes than manually tracking file versions and it’s free.
I decided to build my portfolio website from scratch, just to practice my HTML and CSS skills. It’s always better to practice on something real, and I’m relatively happy with it. It does what I need it to do right now, but I periodically need to add content or make improvements.
I’ve also been learning Git and GitHub as I contribute to an open-source Apache Software Foundation incubator project.
It only recently occurred to me to join the two endeavors (duh!) and use Git to provide local version control as I continue developing my website. Continue reading “Using Git for Website Version Control” →