Archives For Development

A hasty zip through downtown

September 20, 2015

where the bank used to beWeekends are always about running errands. This weekend, for the most part, was no different. Except this time, after running an errand close to down-town Orlando, my wife and I decided to head over to the downtown area around Lake Eola.

One big problem with downtown is parking. It’s only gotten worse of late as new construction has hit the area, such as the Dr. Phillips Center. Other new construction consists almost entirely of expensive townhouses. The whole downtown is rapidly gentrifying.

But Dr. Phillips Performing Arts Center is a resource for the whole area, not just the downtown gentry. It’s been good to see what was a pretty rundown area cleaned up and transformed into something that both benefits and beautifies the downtown core.

architecture palm theme
sunday contemplation
dr. phillips main entry
in the raftersTONE/Orlando – Art in Odd Places

I also discovered at the Dr. Phillips Center that I missed four days of visual and performance art. It started the 17th and ended today, the 20th. There were nearly 50 different installations all up and down Magnolia starting at the Dr. Phillips Center and ending at the Orange County Regional History Center. It’s my loss, obviously. I found a tiny bit of it right at the Center; a see-saw that drove a drum that made music, and a field full of mushrooms made from paper bags.

Maybe next year…

ride my see-saw
paper bag shroomsOther Changes

orlando urban bike rentals

I’ve started to see bike racks like this (from other businesses) popping up all over Orlando. I have no idea how good they are, let alone how much it costs to use one. This particular one was next to City Hall, across the street from the Dr. Phillips Center.

On the way home I took the ramp onto the 408. Hiding away under the overpasses were the homeless. Less than a block from all the new pretty buildings. I would have documented it, but I’m more and more afraid these days of providing information that can be used against those who aren’t nearly as fortunate as I am, let alone the newer, younger residents of downtown.

Technical

It has been a very long time since I talked camera equipment used to help create my photographs. For these last three posts I used a Sony NEX 5N with a Sigma 2.8/19mm and 2.8/30mm lenses. The body was purchased nearly two years ago when it was heavily discounted on Amazon. The lenses a year later when they were discounted to $99 each.

Although I use Olympus almost exclusively, I switch to the Sony because the quality of its sensor is fundamentally different from the Olympus, even though Sony made both sensors. What’s interesting is that all my camera sensors are now 16mp, which would seem to be behind the times to the camera gear hardcore.

I don’t care. Both types of cameras are remarkable and produce excellent results. They’re just different, a difference I can see. And different is good.

In creating a new Android 5/Lollipop app that uses the latest Material Design, I created a new project and selected Android 5 (API 21) (NOT API 20+: Android L (Preview)!). In the process of bringing up the application, Android Studio threw exceptions that it couldn’t find Java class android.support.v4.view.View, among others. To solve this problem I had to add a support library (also known as a library dependency) to the project. This is accomplished via File > Project Structure (Ctrl + Alt + Shift + S) to bring up the Project Structure window.

To add a library dependency, select the Dependencies tab at the top right, click on the plus symbol on the far upper right (see big red arrow above) and then click “1 Library dependency.”

This brings up the “Choose Library Dependency” dialog. I’ve stretched it out to show all that are available to me. You selection will be dependent on the all the APIs you’ve chosen to support. I’ve highlighted the v4 support library. Once you’ve selected the dependency library you need click “OK” all the way back. Once that’s done the project will resync itself, and if you’ve found all the dependencies that project says it needs, Gradle will complete successfully.

Editorial Comment

I realize this is beta code. But this was a new project and all dependencies should have been automatically settled during the creation process. The way Android Studio is behaving right now it’s as if it were still late stage alpha code.

This is also one of the worst UI examples I’ve ever come across, bordering on disastrous. None of this is intuitive, all the way from digging out the main dialog. I know that Google didn’t write the IDE, but they selected it, and they now share responsibility for how bad it is. And this is very bad indeed.