The device has an ok camera, ok battery life, and ok WiFi and Bluetooth. The projector screen looks reasonable but isn’t very high resolution. Along my right temple there is a touch sensitive surface. There isn’t a speaker, but it uses a bonefone for sound output (by vibrating against the back of my ear). The mic can pick put other people shouting commands at me, but it is only in voice command mode very VERY briefly so having unwanted input is not a huge concern.

Glass runs Android Ice Cream Sandwich 4.0.4. All of the local applications appear to be standard apks. You can take download them to a PC using adb, uncompress them, and examine their structure. The various Dalvik bytecode inspectors still work correctly and there doesn’t seem to be anything special going on under the hood as far as software goes.

Using Glass is somewhat of a mixed bag. The voice commands are rather limited; however, the voice recognition and synthesis are VERY good. Taking a picture, recording a video, starting a call, and performing a search are nearly instant. Getting directions, making a call, sending a message, and starting a hangout tend to be good if you are on WiFi but you are at your carrier’s mercy when you are tethered to your phone. Overall the voice controls are impressive where they exist.

If you wish to do other things (ex, read a notification, configure your device, share a photo), you will probably have to use the touch controls on your temple. They are limited (you have single finger swipe left, swipe right, swipe down, and tap gestures), but once you get used to them you can navigate the device quite well.

A lot has been made about the social implications of Glass (mostly in the press which has had a nice babble head quality about the device). In general the reactions I have had have been good. Lots of people have come up to me to ask about it and get a quick demo. No body has asked me to take it off and for people who havn’t heard of Glass saying “It’s a computer” generally satisfies them. I still feel self conscious about it when I go out with it, and I’m not used to having strangers ask me questions about my tech. At the very least it has been good practice for public speaking.

From a developer’s point of view I adore this device. It is VERY different from what I am used to in terms of affordances and capabilities. Being able to have a very quick, unobtrusive, but intimate moment with my user is completely new. However, the capabilities in terms of amount of content I can deliver and receive is limited. This is a Jane. You ask it to tell a server elswhere to do something on your behalf and wait for the response. It has sensors to collect all of the necessary information it may need. Then it is my job to take that information and use my server resources to create a good response and deliver it to the user (quickly).

Currently, there are several companies making Glassware applications for the device. The New York Times has a nice service you can subscribe to. Twitter released an application, and there are some third party Facebook apps as well. Google has been on a regular update cycle for the device so it should have extra functionality rolled out over the next few months. Finally there are several I/O sessions about the device which should encourage more development.

In addition to the device itself, there is a companion Android application which helps with configuring, tethering, and demoing the device. The app includes a screen catcher so people can see what you see. There is also a web app which is used for installing services, managing your shared contacts, and viewing information about your device. Finally there is a web forum for connecting with other Glass Explorers.

I’m researching the device, its software, and its services. I am planning on making some hello world style applications and advocating the technology. I don’t know if this will change computing or consumption, but I hope it at successfully and popularly augments it. We have been promised wearable and ubiquitous computing for a while and Glass is the next step in this general evolution.

August 20, 2013

About the Speaker

May 21, 2013

{ "keys": ["ctrl+b"], "command": "toggle_side_bar" }

jboss-eap-6.0/bin/add-user.sh --silent=true <username> <password> [ManagementRealm]

This is software still in development and we really don’t recommend that you run it on a production site — set up a test site just to play with the new version. To test WordPress 3.6, try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”). Or you can download the beta here (zip).

The longer-than-usual delay between beta 1 and beta 2 was due to poor user testing results with the Post Formats UI. Beta 2 contains a modified approach for format choosing and switching, which has done well in user testing. We’ve also made the Post Formats UI hide-able via Screen Options, and set a reasonable default based on what your theme supports.

There were a lot of bug fixes and polishing tweaks done for beta 2 as well, so definitely check it out if you had an issues with beta 1.

Plugin developers, theme developers, and WordPress hosts should be testing beta 2 extensively. The more you test the beta, the more stable our release candidates and our final release will be.

As always, if you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. Or, if you’re comfortable writing a reproducible bug report, file one on the WordPress Trac. There, you can also find a list of known bugs and everything we’ve fixed so far.

We’re looking forward to your feedback. If you find a bug, please report it, and if you’re a developer, try to help us fix it. We’ve already had more than 150 contributors to version 3.6 — it’s not too late to join in!

Google Summer of Code

GSoC is a summer internship program funded by Google specifically for college/university student developers to work on open source coding projects. We have participated in the Google Summer of Code program in the past, and have enjoyed the opportunity to work with students in this way. Some of our best core developers were GSoC students once upon a time!

Our mentors, almost 30 talented developers with experience developing WordPress, will provide students with guidance and feedback over the course of the summer, culminating in the release of finished projects at the end of the program if all goes well.

Students who successfully complete the program earn $5,000 for their summer efforts. Interested, or know a college student (newly accepted to college counts, too) who should be? All the information you need about our participation in the program, projects, mentors, and the application process is available on the GSoC 2013 page in the Codex.

Gnome Outreach Program for Women

It’s not news that women form a low percentage of contributors in most open source projects, and WordPress is no different. We have great women in the contributor community, including some in fairly visible roles, but we still have a lot of work to do to get a representative gender balance on par with our user base.

The Gnome Outreach Program for Women aims to provide opportunities for women to participate in open source projects, and offers a similar stipend, but there are three key differences between GSoC and Gnome aside from the gender requirement for Gnome.

1. The Gnome program allows intern projects in many areas of contribution, not just code. In other words, interns can propose projects like documentation, community management, design, translation, or pretty much any area in which we have people contributing (including code).
2. The Gnome Outreach Program for Women doesn’t require interns to be college students, though students are definitely welcome to participate. This means that women in all stages of life and career can take the opportunity to try working with open source communities for the summer.
3. We have to help raise the money to pay the interns. Google funds GSoC on its own, and we only have to provide our mentors’ time. Gnome doesn’t have the same funding, so we need to pitch in to raise the money to cover our interns. If your company is interested in helping with this, please check out the program’s sponsorship information and follow the contact instructions to get involved. You can earmark donations to support WordPress interns, or to support the program in general. (Pick us, pick us! )

The summer installment of the Gnome Outreach Program for Women follows the same schedule and general application format as GSoC, though there are more potential projects since it covers more areas of contribution. Women college students interested in doing a coding project are encouraged to apply for both programs to increase the odds of acceptance. All the information you need about our participation in the program, projects, mentors, and the application process is available on the Gnome Outreach Program for Women page in the Codex.

The application period just started, and it lasts another week (May 1 for Gnome, May 3 for GSoC), so if you think you qualify and are interested in getting involved, check out the information pages, get in touch, and apply… Good luck!

Google Summer of Code 2013 Information
Gnome Summer Outreach Program for Women 2013 Information

Some people who are planning parties or who organize meetups are already talking about doing group orders to save on shipping costs, which is a great idea — just make sure you allow enough shipping time. If you’re not sure if the tees could make it to you in time on your side of the world, use the contact options at the bottom of the store page to ask about shipping times. If they can’t reach you in time and you want to have a local printer do some for your group, we’ll post the vector file on the wp10 site within the next week (and this post will get updated accordingly).

The shirts are available in black or silvery gray. Why silvery gray? Because of trivia: the traditional gift for 10th anniversaries is tin or aluminum.

Rather, Google is starting a wonderful thing. In the time I have used it, many of the most obvious problems haven't improved in the slightest.

Here's a quick run down of the good and the bad as I see it. Overall, I see it as comparable to my two-year stint using a Mac for software development. The promise is there, but when you actually try it, you realize why it's not yet the norm.

The Good

I love receiving calls and having all my devices ring. In 2013, it's the way things ought to work. If I'm in the car, my car stereo should ring. If I'm at my desk, I should get a notification on my desktop. If I'm watching TV, my physical phone should ring. Google Voice gets this just right.

I love the option to take calls at my desk. I already do a lot of voice chat sessions with coworkers around the world, and it just seems right that I should do the same thing with gmail addresses and numeric phone numbers.

I love the text transcription of voice mails, for those times I can't take a call immediately. The quality is iffy but is usually high enough that I can understand the gist of what the person was telling me.

Phone number porting works just fine, so you can keep your pre-existing number and not even tell people you are using Google Voice. Well, you have to tell them for a different reason: there is so much bad with Google Voice that you need to warn your potential calling partners about how gimped your phone service is.

The Bad

It doesn't work over data connections. I really don't understand why it is missing. Because of this problem, I have to buy minutes on the POTS to use it on my cell phone, and minutes are far more expensive than the associated data cost. More pragmatically, if I am travelling and don't yet have a local SIM card, it means I cannot use my phone to call over a wifi network.

You can't make or take calls directly from the Voice web page. You have to log into both Google Talk and Google Voice, configure Voice to talk to Talk, and then make your call from Voice. Yes, you can also make a call from Talk directly, but that's a separate feature of the Google suite, thus confusing matters even further. Google is normally excellent at building web user interfaces, but that seems to go down the tubes when an issue crosses multiple teams.

When you make a call at your desk, using Talk, the volume is extremely low. I originally thought that was just my configuration, but some web searching indicates that this has been a widespread problem for several years. I have to turn up my system volume to the max just to barely hear the other person, at which point every random system notification is an ear splitter.

It doesn't support phone usage from the UK. This is a very surprising restriction, because Talk can make calls to the UK just fine. Part of the benefit of Voice for me is the promise that I can travel around and call POTS numbers from wherever I am. However, even if I get a UK SIM card, it's just not supported by Voice.

There is no MMS, and there is no warning on either side when an attempted MMS does not go through. I have to tell people to use email, or to use my physical cell phone number rather than my Google Voice number. If Mom emails me a photo of one of my nieces, it quietly disappears. I am oblivious, and she is wondering what planet I am on that I didn't write back.

The Ugly

The ugly part is that Google is not doing anything to fix all of this. I'm willing to be a beta tester in this case. It's not beta testing, though, if they never fix the problems.

At this point, the POTS tax is substantially higher than the Microsoft tax of yore. It costs tens of dollars a month to participate, and you can't live without it. ]]> http://blog.lexspoon.org/feeds/7485191422762210335/comments/default 0