BenchmarkXPRT Blog banner

Category: TouchXPRT

TouchXPRT update

We have been spending a lot of our energy (and blog space) on HDXPRT 2012 over the last few weeks. We have not, however, forgotten about TouchXPRT.

As we discussed in the past, TouchXPRT will be a new benchmark designed for touch-based devices like tablets and touch-capable Ultrabooks. It will incorporate apps and scenarios tailored to touch-based environments and devices. The initial version will run on the Windows 8 environment formerly known as Metro.

Our current plan is to release an informal design overview later this month. We then hope to have a preview version of TouchXPRT available to community members in October. Depending upon feedback, we will work on improvements and fixes through January with a release in February. We will have more details in the forums and in blog entries over the next few weeks.

As always, we need feedback and input from the community. If you are not currently a member, now is the time to join so you can participate in specifying and developing TouchXPRT. We are excited about both the benchmark and this emerging product space. We hope you are, too!

I do have one thing to mention about HDXPRT 2012. Please remember that we are going to do a Webinar next week (Tuesday, 9/18 at 2:00pm ET). We plan to discuss HDXPRT 2012 and have plenty of time for questions from attendees. We’d love for you to join, learn more about the benchmark, and give us your thoughts and feedback. We will send out more details to community members in an email later this week.

Bill

Comment on this post in the forums

Lights! Camera! Action!

While we continue working on the testing, white papers, and Webinars that are part of the HDXPRT 2012 roll-out, we also are working on some other things as well. The importance of HDXPRT shows how the world is moving toward a much more visual/graphical future. To keep up with that trend and with our benchmark, we are adding video content to the site.

At Principled Technologies, we have been embracing video in a big way. We built a dedicated video-production studio (picture lots of green walls) and bought the necessary video, audio, and lighting gear, so our talented video-production staffers have all the tools they need. Our goal is to be able to quickly create for our clients all sorts of videos of things like our performance reports. We are now able to utilize those same video assets for the XPRTs (HDXPRT and TouchXPRT).

To get things rolling here, we created a video blog based on an entry from a few weeks ago. We will be experimenting with doing more with video, including videos explaining and promoting HDXPRT and regular video blogs. Let us know what you would like to see!

Bill

Comment on this post in the forums

History in the making

We are quickly approaching the debut of HDXPRT 2012. It will be the second version of HDXPRT developed under the benchmark development community paradigm. This milestone provides a nice opportunity to look back at what has happened over the nearly two years since we started creating community-based benchmarks.

The most obvious accomplishment is the development of HDXPRT 2011 and HDXPRT 2012. HDXPRT 2011 has been used around the world for evaluating the performance of computers using applications doing activities that consumers do to create and consume content. We are hopeful that HDXPRT 2012 will be even more widely used.

We also announced earlier this year a new benchmark, TouchXPRT. This benchmark will provide a way to evaluate the performance of the emerging touch-based devices, including tablets. TouchXPRT will debut later this year, initially on Windows 8 Metro.

We have been working hard to get the word out about the benchmarks. We’ve been writing this weekly blog, conducting Webinars, and generally talking with folks in the computer industry. We’ve visited with members of the community around the world at trade shows like CES in Las Vegas and Computex in Taipei. We also spent time with members of the press and computer hardware and software developers. Over the coming months, we are planning to revamp the Web site, add video content, and generally find ways to better engage with and extend the development community.

Less obvious, but equally important to me, has been the development of the development community itself. Developing benchmarks has not been done this way before. We are doing what we can to make the process open to the community, including releasing the benchmark source code. We are optimistic that this method will grow and be a real asset for the industry.

As we look at the growing family of benchmarks under the benchmark XPRT umbrella, the question is always what is next? How can we improve the products and the community? What performance areas do we need to look at in the future? Battery life? Macs? Phones?

Thanks so much for joining us on this journey. The members of this community are what make it work. We look forward to continuing the journey with you!

Bill

Comment on this post in the forums

Tablets everywhere

Everyone wants in on the tablet market. This month, two software vendors have announced hardware tablets—Microsoft’s Surface and Google’s Nexus 7. Both vendors in the past relied on OEMs to create tablets using their software (Windows and Android). Both have met with limited success doing so.

Now, both are trying Apple’s strategy of controlling the hardware as well the software. Unlike Apple, however, Microsoft and Google still need to work with their OEM partners. I’m looking forward to watching that delicate dance!

I’m looking forward more, however, to being able to actually play with both of those products. I’m also looking forward to using TouchXPRT on such products. We have not given you an update in a while on TouchXPRT, but rest assured that we are hard at work on it. Once we have HDXPRT 2012 ready to go, we will give you more details on where we are with TouchXPRT and its current schedule. The touch and tablet market are heating up and we plan to be there for it. As we have indicated before, we will support Windows 8 Metro in the first version, but we see a real need for TouchXPRT to work on multiple platforms. So much to do!

Please note that today is the end of the beta test period. We appreciate the results, bugs, and suggestions you have sent so far. Feel free, however, to continue to send us any feedback or issues you find even after the official beta period is complete. After today, we can’t guarantee to be able to address them, but we will try.

Bill

Comment on this post in the forums

Touch: The finger versus the stylus

One advantage of being in the industry for a long time is seeing the development pendulum go back and forth. One such pendulum is the way of interacting with touch interfaces. Touch interfaces existed long before the current phone and tablet devices. I remember the HP-150, an early touchscreen PC, from my days working on Kermit in the 1980s. It was not a big seller, so you probably never used one. However, you may have used early touchscreen technology in devices like kiosks. While those touch interfaces were fairly simple, you used your fingertip on the screen to indicate your selections.

When PDAs became a big deal in the 1990s, the stylus rather than the fingertip became the way to touch the screen. If you lost your stylus or did not feel like pulling it out of the case, you could use your fingernail. I became very good at writing in the odd script that the Palm OS used. (I still sometimes write the letter A as an upside-down V.) Though the stylus was easier, you could do most things using your fingernail. I also used a stylus (and my fingernail) with Windows smartphones.

Smartphones, especially the iPhone, swung the pendulum back to touching the screen with your fingertip. It took me a decent bit of time to adjust to touching the screen that way. I also had to get used to staring at screens through fingerprints. The ability to multi-touch, however, made that worthwhile. (And, caused me to make sure I always carry those screen-cleaning cloths.)

Recent tablets have generally utilized multi-touch, fingertip interfaces. I still find myself wishing for a stylus at times. I’ve purchased a few different styli for using my iPad, but the mushy, fingertip-like ends leave much to be desired. I just ordered an interesting compromise, the Adonit Jot Classic Stylus. I’m hopeful, but won’t be surprised if I’m disappointed.

The stylus on some Windows 7 tablets like the Dell Latitude ST shows what is possible with a stylus. The stylus can be really useful in some work environments. Hopefully, we’ll see more innovation in touch interfaces. In my ideal world, I could use a simple stylus or my fingernail some of the time and my fingertips when multi-touch is better—all on a single device, of course! For now, I just have to keep cleaning off my iPad’s screen while I try to find the ideal stylus.

Whatever way the touch interface pendulum swings, we’ll try to make sure that TouchXPRT will be the right tool to measure it.

Bill

Comment on this post in the forums

Back to the future of source code

Today I’m spending a good chunk of the day participating in a panel discussion on the Kermit file transfer protocol as part of an oral history project with the Computer History Museum. A little over 30 years ago, I worked at Columbia University on the original versions of Kermit. In preparing for the panel discussions, I’ve been thinking about projects with available source code, like Kermit and HDXPRT.

Kermit was a protocol and set of programs for moving files before the Internet. We designed Kermit to work between a wide variety of computers—from IBM mainframes to DEC minicomputers to CP/M microcomputers. As such, we wrote the code to accommodate the lowest common denominator and assume as little as possible. That meant we could not assume that the computers all used ASCII characters (IBM mainframes used EBCDIC), that 8-bit characters would transmit over a phone line, or that packets of more than 100 characters were possible (DEC-20 computers specifically had an issue with that). The pair of Kermit programs negotiated what was possible at the beginning of a session and were able to work, often in situations where nothing else would.

We developed Kermit before the open-source movement or Gnu. We just had the simple notion that the more people who had access to Kermit, the better. Because we did not want incompatible versions of Kermit or the code to be used for the wrong purposes, we retained control (via copyright) while allowing others to use the code to create their own versions. We also encouraged them to share their code back with us so that we could then share it with others. In this way, Kermit grew to support all sorts of computers, in just about every corner of the planet as well as outer space.

In many ways, what we are doing with HDXPRT and its source code is similar. We are working to create a community of interested people who will work together to improve the product. Our hope is that by having the HDXPRT source code available to the Development Community, it will encourage openness, foster collaboration, and spark innovation.

I believe that what made Kermit successful was not so much the design as it was the community. I’m hoping that through the Development Community here, we can make just as successful HDXPRT, TouchXPRT, and who knows what else in the future. If you have not already joined, please do—the more folks we have, the better the community and its resulting benchmarks will be. Thanks!

Bill

Comment on this post in the forums

Check out the other XPRTs:

Forgot your password?