Ted Wise

Printing in color to the Savin C3535 printer from OS/X

2010-03-12T15:17:43Z

This one has been bugging me for quite a while. My office has a large number of multi-function printers and none of them have good support under OS/X. It's easy to print to them in black and white by treating them as generic HP PCL/PXL printers, but they refuse to work as color printers.

Snow Leopard supposedly has full support for the Savin printers, but it appears that support requires the Savin printers to have Postscript cards installed. That's not the case at my office. If you try to use the Savin Postscript (PS) printer drivers you'll end up printing page after page of Postscript gobbledygook.

On-line recommendations for other printers insist that the PCL XL generic printer driver will print in color. That doesn't work for the Savin printers. The print dialog refuses to allow color as an option.

To solve this problem we need to venture into the Unix heritage of OS/X. OS/X uses the Unix CUPS printing system under the covers and hides it with pretty dialog boxes and System Preference pages. If you look around you'll find PXL color drivers (PPD files) for the Savin printer drivers. Those drivers are for Linux (which also uses CUPS) and won't directly work on OS/X. If you install one, you'll get a warning message from OS/X telling you that required software is missing. OS/X will suggest using Software Update to get the required software. That won't work either. A little more spelunking around finally gave me the answer.

First, download and install Ghostscript from the Open Printing group. Ghostscript is an open source Postscript interpreter. It takes the Postscript page description code that Mac software generates when printing, and converts it for use by the printer-specific drivers. It's an OS/X package, so you'll have to double-click on the mpkg file to install it.

Second, download and install foomatic-rip. This interfaces with Ghostscript to support the foomatic printer drivers. This is also a mpkg file that needs to be installed. You can't print yet using these two applications, they provide the "missing software" that OS/X complains about when you try to install the PPD printer drivers.

After these two items are installed you can make use of the foomatic printer drivers. The Savin color PXL drivers are available from openprinting.org. Unfortunately, they're in Linux-specific RPM and DEB formats. I converted them to a zip file that you can download here. Unzip that file and it contains the PPD printer driver files.

If you want to get them directly from the source, instead of using the zip file, download the DEB file from here. From the command-line you'll need to extract the files out of the DEB file:

# ar xv openprinting-ppds-pxlcolor-savin_20090512-3lsb3.2_all.deb
# tar -zxvf data.tar.gz
# cd opt/OpenPrinting-Ricoh/ppds/Savin
# gunzip *.gz

That will get you the PPD printer driver files for the Savin printers.

From here, it's normal OS/X printer installation. Go to the OS/X System Preferences and click on Print & Fax. Click the '+' icon to add a new printer. Choose the IP option and for the Protocol, choose HP Jetdirect - Socket. We make that choice because we're treating the Savin printer like an HP PXL printer.

Enter the IP address of your Savin printer, and provide whatever Name and Location you like. Once you enter the address, OS/X will most likely automatically choose the Savin C3535 PS printer. If you're reading this, you already know that driver won't work for you. Click on the Print Using drop-down and choose 'Other..'. Use the file selector to find the PPD file for your particular printer, and open it. OS/X will setup the printer and you can finally print in color!

1. The primary reference for this information can be found here.

2. The Savin PXL color driver page can be found here.

Creating a circular gradient in iReport

2010-02-07T22:47:05Z

JasperReports is an extremely flexible tool for creating reports in Java. Reports are defined as JRXML templates, compiled to JASPER binaries and run through the JasperReports run-time. iReport is the GUI report writing tool that creates the JRXML templates.

A JRXML template is an XML file with a jrxml extension. Here's an example of a very small template with a single parameter:

 
<?xml version="1.0" encoding="UTF-8"?>
<jasperReport xmlns="http://jasperreports.sourceforge.net/jasperreports"
              xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
              xsi:schemaLocation="http://jasperreports.sourceforge.net/jasperreports http://jasperreports.sourceforge.net/xsd/jasperreport.xsd"
              name="comments" pageWidth="554" pageHeight="802" columnWidth="554" leftMargin="0" rightMargin="0"
              topMargin="0" bottomMargin="0">
<parameter name="displayValue" class="java.lang.String" isForPrompting="false"/>
<pageHeader>
        <band height="120">
            <image>
                <reportElement x="339" y="44" width="65" height="12">
                </reportElement>
                <imageExpression class="net.sf.jasperreports.engine.JRRenderable">
                    <![CDATA[new com.report.jasper.CircularGradientImageRenderer("#00FF00")]]></imageExpression>
            </image>
            <textField isBlankWhenNull="true">
                <reportElement x="339" y="44" width="65" height="12"/>
                <textElement textAlignment="Center" verticalAlignment="Middle">
                    <font fontName="DejaVu Sans" size="7"/>
                </textElement>
                <textFieldExpression class="java.lang.String"><![CDATA[$P{displayValue}]]></textFieldExpression>
            </textField>
        </band>
    </pageHeader>
</jasperReport>

A common requirement when displaying values is to highlight them by displaying them with a background color. But many background colors can cause values to be difficult to read or can make values illegible when reports are faxed or copied in black-and-white.

To get around this, a circular gradient background can be used. The resulting background looks like this:

iReport lets you place images on a report that can come from a physical file or can be dynamically generated. In our case, we'll write a simple Java class that will generate the gradient background. Note that the example provided here will only work when generating PDF reports.

 
package com.report.jasper;
 
import java.awt.*;
import java.awt.geom.AffineTransform;
import java.awt.geom.Rectangle2D;
 
import net.sf.jasperreports.engine.JRAbstractSvgRenderer;
import net.sf.jasperreports.engine.JRException;
 
/**
 * Draws a colored, circular gradient background used in the report.
 */
public class CircularGradientImageRenderer extends JRAbstractSvgRenderer {
    /**
     * The gradient color.
     */
    private String rgb;
 
    /**
     * Create a circular gradient image in a bounded square.
     *
     * @param rgb The gradient color.
     */
    public CircularGradientImageRenderer(String rgb) {
        this.rgb = rgb;
    }
 
    /**
     * Pull out a substring without returning null.
     *
     * @param value The value.
     * @param begin The beginning index.
     * @param end   The ending index.
     * @return The substring.
     */
    private static String safeSubstring(String value, int begin, int end) {
        String sub = "";
 
        if (value != null) {
            if (value.length() > begin) {
                end = Math.min(end, value.length() - 1);
                sub = value.substring(begin, end + 1);
            }
        }
 
        return sub;
    }
 
    /**
     * Parse a hex value without throwing an exception.
     *
     * @param value The value to convert.
     * @return The integer value.
     */
    private static int safeHexParse(String value) {
        try {
            return Integer.parseInt(value, 16);
        } catch (NumberFormatException e) {
            return 0;
        }
    }
 
    /**
     * Convert a string hex color into a Java Color object.
     *
     * @param rgb The string value.
     * @return The Color object.
     */
    public static Color stringToRGB(String rgb) {
        int r = 0;
        int g = 0;
        int b = 0;
 
        if (rgb != null && rgb.startsWith("#")) {
            r = safeHexParse(safeSubstring(rgb, 1, 2));
            g = safeHexParse(safeSubstring(rgb, 3, 4));
            b = safeHexParse(safeSubstring(rgb, 5, 6));
        }
 
        return new Color(r, g, b);
    }
 
    public void render(Graphics2D g2d, Rectangle2D rect) throws JRException {
        // Save the Graphics2D affine transform
        AffineTransform savedTrans = g2d.getTransform();
 
        float radius = (float) (Math.max(rect.getHeight(), rect.getWidth()) / 2);
        float[] fractions = {0.0f, 0.3f, 1.0f};
        Color[] colors = {Color.WHITE, Color.WHITE, stringToRGB(rgb)};
 
        // Paint a nice background...
        g2d.setPaint(new RadialGradientPaint((float) rect.getCenterX(), (float) rect.getCenterY(), radius, fractions, colors));
        g2d.fillRect(0, 0, (int) rect.getWidth(), (int) rect.getHeight());
        g2d.draw(rect);
 
        // Restore the Graphics2D affine transform
        g2d.setTransform(savedTrans);
    }
}

This simple class is provided with a drawing rectangle and context by JasperReports. It uses the Java RadialGradientPaint class to draw the circular gradient. This class was added in Java 6 so don't go looking for it in earlier Java versions.

To make this work in iReport, you create two items. The first item is the background image. Drag an image widget from the tool palette to the report. iReport will prompt you for an image to display in the widget. Press cancel. We're dynamically creating the widget so we don't need an image file. Place the image widget wherever you want the value displayed, and size it appropriately.

Next, select the Image Expression property and press the ellipsis button next to the field. A pop-up window will appear. In that window, type the name of the Java class that will dynamically create the gradient background. The class we're using takes an RGB color as a String parameter, so a red gradient would be "#FF0000".

Next, set the Expression Class property. Set the property to 'net.sf.jasperreports.engine.JRRenderable'. This tells JasperReports that the custom class is writing a rendered image. You could also write a Java class that created a 'java.awt.Image'. But that is a fixed-pixel size image that won't scale appropriately in a PDF.

Finally, we drag a Text Field widget onto the report. Place it on top of the image widget created earlier and size it identically. If you find that the text field ends up behind the image, select the image, right click it and choose Send to Back.

Don't look at the raw XML trying to find a z-order attribute, you won't find one. JasperReports represents z-order by the order elements appear in the XML file. Elements that appear last overwrite elements that appear earlier in the file.

That's all there is to it. You can change the size of the inner white circle by tweaking the Java class.

 
float[] fractions = {0.0f, 0.3f, 1.0f};

Move the center value (0.3f) up and down to find the right size.

One last tip. If you try to preview the report in iReport you might receive errors that the class can't be found. Bring up the settings in iReport and add the path to the compiled class in the Classpath section.

Larry’s vision of the cloud

2010-02-02T14:13:07Z

While taking a trip to sun.com today, I noticed that it's already redirecting to oracle.com. And at the same moment I noticed that the headliner at oracle.com is an announcement about the Oracle Cloud Computing Forum. Given Larry's well know views of the cloud, I found this amusing. And a vision of Larry running a cloud conference immediately came to mind. Here's how I imagine a Cloud Computing Forum run by Larry Ellison would go:

Larry: "Welcome to the Oracle Cloud Computing Forum. Please take a seat. There's been lots of talk about cloud computing and we here at Oracle wanted to share our own corporate vision. Ready? Here goes. There IS NO cloud! It's all a bunch of CRAP! It's the same thing we've been doing for TWENTY FREAKING years! You want a cloud? Go buy our hardware and software you CHEAPSKATES! Thank you, that concludes our forum. I'd like to open the mic for questions."

Random Guy: "Isn't a cloud more then just a web site?"

Larry: "No. Next question."

Other Random Guy: "Is a cloud just outsourcing your IT?"

Larry: "How many times do I have to tell you? There IS NO cloud. And yes, it's just outsourcing your IT. And only idiots would do that. Buy our hardware and software."

Final Random Guy: "What about Amazon's and Google's vision of the cloud?"

Larry: "Google is just hotelling web apps and any idiot can do that in their own data center. Amazon is just hosting a big virtualization server and any idiot can do that too. You want to swallow that crap? Fine. I'll buy your company and fire you for being stupid, or you can just buy our hardware and software. Now everyone go home, the conference is over."

Apple’s Trojan horse

2010-02-02T14:08:25Z

Apple's trojan horse is the "computer as appliance". They've managed to create devices that are almost as wide in scope and functionality as general computing devices but are easily accessible to non-technical people. And, more importantly, don't need technical maintenance or an understanding of the computing underpinnings.

If it were just the App store, then all of the new stores that other vendors have created would have propelled their devices off the shelves.

If the iPad succeeds, it's because its an idiot-proof appliance. And Apple isn't unique in knowing this. Nobody has to setup their Kindle's file system. Or figure out where that book they downloaded went.

Do you want to know how the unreleased iPad works? It works just like the iPhone. It's the exact same operating system. It's 90% of the same UI. What are the major technical differences?

It's much faster.
The OS now allows files to be exchanged both between iPad applications and with computers.
It supports hardware bluetooth keyboards and custom on-screen touch keyboards.
It has new UI elements that take advantage of a bigger screen.
It supports external displays, aka the projector.
And, lastly, it has a big, bright, sharp screen.

Thanks to the screen size and the CPU speed, the apps are going to be larger in scope. There are apps for editing Microsoft Office files on the iPhone but no one uses them for more then display and minor touch-up. The screen is too small, the device is too slow and it's too hard getting documents in and out. The last two points will likely evaporate with the next iPhone refresh. But the first one never will.

But, at launch, Apple showed a mobile edition of iWork. With a well thought-out gesture interface. And, an application for drawing on the iPhone was reworked for large-scale drawing on the iPad. You can run a sizable portion of Photoshop on the iPad. And it makes sense to do it. And, Mac software makers who weren't considering the iPhone are now announcing iPad plans. Omni Group, who makes the Mac's equivalent of Visio, are halting existing development to create iPad versions of their applications.

Why all this trouble? Why not create a tablet running standard OS/X instead of iPhone OS? After all, you could create an App Store for OS/X apps. 90% of Mac software doesn't even require an installer. Again, it's because Apple is moving toward computing appliances. Which means locked-down devices with restricted technical underpinnings. And OS/X is wide open. It has a standard filesystem. It has drivers. It has software that can get into the guts of the OS and need to be wiped to clear it out. And for a consumer device you don't ever want to worry about, that's not good enough.

The other vendors know it too. Asus, the largest computer company in the world, announced they aren't going to make a tablet. Why? Because they said Windows 7 can't compete with the iPhone OS on a tablet device. And there's no way that mobile Windows can either. And Android isn't close enough yet.

If Apple is right, and this is a market that's been going either unserved or underserved by netbooks, then stand to make a killing.

Steve Jobs holds forth at Apple town hall

2010-01-31T23:12:54Z

Steve Jobs held an internal town hall at Apple after the unveiling of the iPad. Since secrecy is so tight, many at Apple had no idea the iPad was coming. He took questions and second-hand commenters say he had a few choice comments.

He said that Apple bought Lala because they wanted their talent for the iTunes team.

He said that Apple didn't go into the search business but Google went into the phone business. He feels that the Android team at Google (not the entire company) would love to kill off the iPhone. And he feels that the Google "do no evil" corporate mantra is a bunch of crap.

According to Jobs, Apple is going to update the iPhone/iPad faster then Google can with the Android. He also said that the next iPhone hardware update was going to be an "A+" update. He rounded out the hardware talk by stating that the next Mac refresh was going to "take it to the next level".

Finally, he lamented that the "kick-ass" Adobe of old was now a "lazy" company and that Flash was a dead technology.

---

My take - Google has a split focus between their Google OS and Android. What they're trying to accomplish - a netbook-like computing appliance, is EXACTLY what the iPad is. Google's problem is they've decided that Android won't do what they want, so they've gone down the Google OS road as well. This means they need double the resources and gain little between advances in one platform. Google's approach is, ironically, the Microsoft approach. Google is checking of technical functionality checkboxes at the expense of ease of use and paradigm shifts. They'll probably sell a crap-load of Android devices but they're relegating themselves to the Microsoft second-tier in the mind of consumers.

Will Apple really update their platform faster then Google will? I have no idea. They've let iPhone OS languish while the iPad was in development, we'll see if that picks back up now that the iPad is public. The biggest problem for them is they're trying to forge new ground - looking for new approaches that differ from long-established solutions - like, a filesystem. That's not a fast or simple process.

From the hardware perspective its now assumed that the new Apple-designed A4 CPU will be coming to the iPhone. Probably a speed-throttled version. Maybe that's what Jobs means by an "A+" update. It will probably have an increased screen resolution and a better camera. Beyond that, I have no idea.

And the Mac refresh he's talking about will be a switch to the new Intel i5 chipset. This brings a significant jump in performance without a battery life impact.

And finally, yes, he's correct. Flash is a dead-end and it needs to die so that HTML5 moves forward. Honestly, it's already happening at a much faster pace then I expected. Google just announced they're killing IE 6 support in Google Docs and other web properties. And YouTube and Vimeo now support HTML5 video in place of Flash. That's coupled with announcements that, for the first time ever, the percentage of Flash-enabled user agents is dropping.

Don’t misunderstand Oracle’s purchase of Sun

2010-01-31T16:42:27Z

I was reading a blog post about what will happen now that Oracle has purchased Sun. The poster repeated a number of fallacies that I've seen around the web.

1. MySQL is dead now.

MySQL is dead? No its not. Oracle has owned InnoDB and never once used it against MySQL users. They own BerkelyDB and support and sell it. Oracle is attempting to own every segment of the market from the "Enterprise" to the "tactical". They're placing MySQL at the tactical end. They'll sell you MySQL support and attempt to upsell you if they get the opportunity.

I'm no Oracle fan but they're not attempting to kill any open-source projects. They're continuing to fund Glassfish, Hudson, Netbeans and numerous other open-source projects. They're even continuing to donate to Eclipse. And they intend to increase the community involvement in the Java language.

2. Solaris/OpenSolaris is going to be killed off.

Oracle is looking to combat IBM. IBM's "secret sauce" in the lucrative Enterprise space is owning the entire stack, from the hardware, to the OS to the software running on top of it. That's why Oracle is keeping Solaris and the SPARC hardware. They'll tell Enterprise buyers that they'll get the pinnacle of speed and reliability with carefully developed and tuned software running on their own hardware.

3. Oracle's plans for Java aren't clear and Netbeans is history.

Oracle says they're increasing community involvement. They seem to want to move at least some of the R&D for Java out to the community. And, again, Netbeans isn't history. The official Oracle roadmap lists an increase in funding for Netbeans. They intend to use Netbeans as the "tactical" IDE offering, while using JDeveloper as the Enterprise one. Personally, I'd move everything to Netbeans (or Eclipse) and kill off that piece-of-crap JDeveloper, but I'm not Larry.

4. SPARC is dead - Oracle isn't a hardware company.

Oracle wants to be in the hardware business. That's how they intend to compete with IBM. They see IBM as their competition, not Microsoft. They're increasing the hardware push and co-branding them as Sun/Oracle.

5. OpenOffice and VirtualBox are dead.

Oracle is starting up a new division to work on OpenOffice and they're integrating VirtualBox with Oracle VM.

I'm no great fan of Oracle's business. They make overly complicated and buggy software and then charge you an arm and leg to make it work. But the Oracle DB is hands down the best database server on the market. Larry intends to own everything including the kitchen sink and will sell you any part of that vast array of software. And if the software is free, he'll sell you the support instead.

I would greatly prefer that Oracle start uniting platforms and move to an open source model but, at least at present, that doesn't appear likely.

References

http://java.dzone.com/articles/oracles-roadmap-sun

http://www.oracle.com/ocom/groups/public/documents/webcontent/038563.pdf

Maven Micro-Tip: Get sources and Javadocs

2010-01-27T19:43:46Z

When you're using Maven in an IDE you often find the need for your IDE to resolve source code and Javadocs for your library dependencies. There's an easy way to accomplish that goal.

# mvn dependency:sources
# mvn dependency:resolve -Dclassifier=javadoc

The first command will attempt to download source code for each of the dependencies in your pom file.

The second command will attempt to download the Javadocs.

Maven is at the mercy of the library packagers here. So some of them won't have source code packaged and many of them won't have Javadocs.

The HTML5 video mess. See it today!

2010-01-22T14:10:25Z

Two giant video web sites are now running HTML5 video betas. This means that you can use their sites without having Flash active. Vimeo's setup is especially impressive in that it very closely mimics the Flash experience.

If you don't know what HTML5 video is, its an HTML video tag that will play video in the browser without requiring a Flash plugin. More importantly, the browser can interact with the video using JavaScript to display video overlays, control "scrubbing" of the video, etc. Pretty much any interaction you can do with the Flash plugin can be done with HTML5 video.

The YouTube beta needs to be activated by going to http://www.youtube.com/html5.

The Vimeo beta needs to be activated by clicking on an easy-to-miss link at the bottom right of each video's description.

Both betas remain active once you select them. Why would you use the HTML5 version? Because Flash is often a vector for security problems and because Flash video decoding uses a large percentage of CPU. A small side bonus is that video scrubbing is smoother with the HTML5 version.

But most of you won't be able to use the betas. Because both betas require a browser that supports the HTML5 video tag, but, in addition, also supports the H.264 video codec.

There are three shipping browsers that support the HTML5 video tag: Firefox, Safari and Chrome. But only Safari and Chrome support the H.264 video codec. H.264 must be licensed before it can be legally used. And that license is expensive. And that license cannot be transferred with source code. So, downloadable binaries can be licensed and can include H.264 but open source programs that are compiled by others can't be. That means that Chromium, the open source version of Chrome, can't display H.264 video.

Mozilla, the maker of Firefox, could probably afford the H.264 license, but they refuse to. First, a high percentage of Firefox consumers use the source code from Mozilla, not the binaries. Virtually every Linux distribution works this way. Secondly, Mozilla, as an open source company, feels that a licensed codec like H.264 is unacceptable.

So Firefox (and Chrome) also support the open source video codec Ogg Theora. But Apple doesn't. And Google won't encode video in Ogg Theora for YouTube. The first issue is video quality and bit rate. H.264 has slightly better video quality at an equivalent bit rate to Ogg Theora. For Ogg Theora to match H.264 video quality the bit rate has to be increased. And for a web site like YouTube, that means all consumers have to have better Internet connections and Google has to pay a bigger bandwidth bill. The second issue is hardware support. There are hardware chipsets available (and in iPhones today) that decode H.264. That means that the phone CPUs (which aren't that powerful) aren't taxed with decoding video, and that power usage when displaying video is greatly reduced. The last issue is patents. Apple isn't satisfied that Ogg Theora doesn't violate patents that exist around video decoding and they're unwilling to be the target of a law suit that goes after Apple's deep pockets. Google, seemingly, doesn't care.

So, the biggest single browser, Internet Explorer, doesn't support the HTML5 video tag. The second biggest browser, Firefox, supports the tag but only displays Ogg Theora videos. The third biggest browser, Safari, supports H.264 but not Ogg Theora. And the fourth biggest browser, Chrome, supports both H.264 and Ogg Theora. And the big video sites refuse to support Ogg Theora.

It's a mess.

This impasse will only be resolved when someone buys H.264 outright and releases it to the public or when Ogg Theora is improved, cleared of patent issues and gains hardware support. Neither events seems likely anytime soon.

It’s market share time again – who’s winning? Windows, of course.

2010-01-21T20:19:23Z

ArsTechnica posted the latest operating system market share statistics. As of December, 2009, Windows is still the lions share of the market at 92.21%. OS/X is a very distant second at 5.11% and Linux trails at 1.02%.

The trend is very slightly downward for Windows. It went from 93.66% in January, 2009 to 92.21% - a drop of 1.45%. At that rate it would take Microsoft 30 years to drop below 50% market share. But that rate won't continue.

The trend is upwards for OS/X, 4.71% in January to 5.11% - an increase of 0.4%. And its upwards for Linux, 0.90% in January to 1.02% - an increase of 0.12%.

Another way to look at this:

Microsoft lost 1.6% of their market share
Apple gained 8.5%
Linux gained 13%

So Linux is increasing market share the fastest while Microsoft is losing share. You can rack that up to the increased popularity of netbooks. Which, despite the press, often come with Linux outside the US and don't get returned.

On the plus side for Microsoft, Windows 7 is a hit. It has easily outsold Vista for the same time period after launch. And, the market share for just Windows 7 is already larger then for OS/X.

But, Microsoft's biggest problem is the fact that 68.63% (slightly over 2/3) of all Windows installations are XP or earlier. Those installations don't have a straight upgrade path to Windows 7. That high bar for migration - coupled with strong on-line applications - makes upgrading them open to alternatives, from super-cheap Linux netbooks to high-end Macs.

My guess is that we'll see the overall market share of Windows drop at an increasing rate and that Linux market share will grow at an increasing rate while OS/X will continue to increase at a modest pace.

And all of this doesn't include mobile.

Will the next iPhone OS allow multitasking?

2010-01-19T22:13:36Z

It's not the hardware. And it's not a fundamental software issue. It's a combination of UI and trust.

From the UI perspective, Apple didn't want multiple apps running at the same time without visual feedback. So the few apps that they allow, all provide it. A background phone call shows as a throbbing green bar at the top of the screen. Data transfer shows as a throbbing blue bar. Running audio shows as a play icon in the top status bar. And that's about it.

So to allow more background apps Apple will either have to create a new UI metaphor or allow apps to wire into the existing mechanism. For example, allowing Pandora to wire into the play icon in the top status bar. Apple doesn't seem satisfied with the "standard" approach, e.g., let the user remember what's running without visual feedback and use a task list to switch/kill between apps. The Pre uses a card stack metaphor that technologists liked but the general public doesn't seem to have bought into.

Beyond the UI metaphor issue is the question of trust. Background apps chew up memory and battery life. Both are very limited on small devices. If you don't care how well or how poorly this is done, then you just let any app run in the background. If you _do_ care then you need to validate that background applications don't chew up too much of either resource. So it's entirely possible that Apple will require background apps to be "blessed" by running them through extra validation. It's also possible that they'll just expand out the list of "special functions" that won't interrupt an app. As a current example, creating an email from an iPhone app won't stop an app from running. Perhaps they'll expand that list to include phone calls. Right now, if your GPS is giving you driving directions and you get a phone call, you stop getting driving directions.

Apple is taking their sweet time. You couldn't do copy and paste on the phone for two years after its release. Now Android reviewers are complaining that copy and paste doesn't work nearly as well on Android as it does on the iPhone. Apple is trying to get the paradigm correct and work consistently and correctly everywhere. Whether that approach is good enough or acceptable is a question that consumers get to answer.

And then you throw the tablet into the mix. It has a much larger screen and a rumored new UI paradigm. And that has people guessing that the tablet will run multiple apps but the iPhone won't. It looks like we'll find out more on the 27th. Everything is just educated guesses until then.