September 2010 Archives

My trip to Seattle was going great until I got to Seattle. There, I learned that all of the luggage from the Portland, Maine connection had been lost or misdirected in JFK, so I am without the majority of my clothes. Thankfully, My Prescient Wife, Rori, hinted that I should split my clothes between my carry-on and my checked bag. My mother's experience this summer while traveling to Germany of being without luggage for a good portion of her trip was also on my mind, so I had kept one change of clothes in the carry-on as well as all of my toiletries. I must assume that JetBlue will find the bag and get it here sometime tomorrow.

With this news weighing heavy on my mind, I get on the Enterprise bus to go get the rental car. When I hand the agent my reservation (that had been made my Hewins AAA Travel in Portland, Maine, from whom I had specified Enterprise), he showed me that it was in fact for Hertz. Imagine my delight when he asked me if I had rented with Enterprise before, and I told him that I had a corporate account and that I rented locally in Maine about once a month. Having found my account, he was able to match the rate and get me out the door in about 5 minutes.

Hooray, Enterprise, for redeeming one part of this trip. Next time you need a car, give them a try.
Enhanced by Zemanta
I'll be back in Chicago for another GraphExpo, this time speaking as part of the IDEAlliance G7 Summit. If you're in town, stop in and say "Hi!"

The talk is called "Using RGB in your PDF/X Workflow," and should be an eye opener for many printers who thing that RGB is a four letter word.

Here's the session description:

When we think of PDF/X workflows, we typically think of PDF/X-1a and its promise of a file with high quality graphics, embedded fonts, and no transparency, RGB or color management. Our production workflows have evolved, however, and now transparency, RGB and color management can help make our print workflows accurate and profitable. As extended gamut printing and complete digital workflows become the norm, we need to be prepared for PDF/X-3 and PDF/X-4. These two specifications within the PDF/X family allow for and expect color-managed content in PDF files. In addition, PDF/X-4 allows transparency for workflows that take advantage of the Adobe PDF Print Engine. In this session, we will explore how to implement PDF/X-3 and PDF/X-4 workflows.
Enhanced by Zemanta
Adobe released an extension to Illustrator CS5 that enables greater SVG interactivity and better export for HTML5. While Flash Catalyst enables communication between designer and Flex developer, the Illustrator HTML5 Plug-in Pack enables communication between designers and HTML5 developers.

The SVG, or Scalable Vector Graphic, format has been around for a long time, and Illustrator has been able to write SVG for about as long as the format has been around. The plugin enables creation of certain tags that allow HTML5 pages to render on different screen sizes, include CSS, enable variables in the design attributes, and more.

It works in combination with the HTML 5 Pack for Dreamweaver CS5 that was included in the Dreamweaver CS5 11.0.3 update. It can also produce stand-alone HTML, but in practice, artwork will be handed over to a developer for coding and inclusion in larger applications. According to the User Guide, 

Using the HTML5 Pack you can do the following:

        • Parameterized SVG
        • Multi-screen SVG
        • Mark object as canvas in SVG
        • Export named character styles as CSS
        • Export artwork appearances as CSS
        • Include Selected Graphic Style as CSS in SVG
Here's a summary of what's possible.

Parametrized SVG allows a designer to create objects with variable attributes. These might include fill and stroke color, opacity, and a few others. As variables, the developer can then address these programmatically after the designer hands over the artwork.

Multi-screen SVG allows a designer to create different versions of their design that will then display on the appropriate screen. For instance, we are all familiar with iPhone apps that switch from Portrait to Landscape mode. Multi-screen SVG enables a designer to design for those orientations and also for specific screen sizes. This will help designers create more consistent designs across multiple mobile devices.

Marking an object as a canvas in SVG allows the designer to designate an object as a canvas. This will rasterize the content within the canvas and make it available for the developer in javascript or other scripting languages.

Exporting character styles and artwork appearances to CSS does just that. Character Styles become CSS that the developer can use to maintain consistency when they are creating new elements in the application. An object's Fill, Stroke, Opacity, Gradient and also the absolute position and dimensions are also exportable as CSS.

You can also Include a Graphic Style as CSS in your SVG. Using this option, the designer can send graphic styles that aren't currently used in the artwork, with the expectation that the developer will enable and disable these styles programmatically. Using this option, the designer can designate exactly how objects should appear under specific conditions, and then the developer can enable that behavior.

Why is all this important? One of the most challenging parts of developing content for the Web and Mobile devices is that the designers and developers speak different languages. This language barrier is very real; developers sneer at designers who don't know how to code, and designers can't understand the ham-handed way that developers carve up their work to turn it into functional code. Any tool that helps designers better inform developers of their desires, and also enables developers to use the content that developers provide without having to carve it up will empower both sides to work more productively and harmoniously.

Over at Forrst, I asked who is likely to use this new feature. While I haven't gotten feedback yet (it's only been a few minutes!) I anticipate that there will be a lot of interest. Whether there is widespread adoption depends on how well the plug-in works in real-world situations. I look forward to the results of the survey.

Enhanced by Zemanta
I purchased and installed Parallels Desktop 6 yesterday. As a "loyal customer," I was offered a chance to purchase the upgrade ahead of the public launch on the 14th. However, the upgrade is freely available at parallels.com, so I don't feel so special after all.

From an interface perspective, Parallels doesn't feel that much different. From a performance perspective, though, changes are sometimes subtle and sometimes dramatic.

I have several Virtual Machines that I use on a regular basis. I have a Black MacBook 2Ghz Core 2 Duo machine with 3 GB of RAM and a 500 GB 7200 rpm hard drive. It is missing advanced graphics processing, so I can't say much about improvements in graphics performance.

The first thing I noticed when starting my Windows 7 Ultimate 64bit machine was how long it took to update Parallels tools. A very long wait looking at a black screen, and then finally a few restarts and updates to get things going, then success. It took about a half hour to go through all of the updates.

One of the things I find interesting is that the emulated hardware drivers have changed. I assume that there are performance and compatibility benefits, but I am not sure. I do know that Windows installed drivers for the newly detected hardware before Parallels tools installed.

I next wanted to install Kaspersky 2011, which comes "free" with Parallels Desktop. In Parallels 5, security was provided by Parallels Internet Security, which was a rebranded Kaspersky. This time around, it seems that we get the 3 month trial for free, and if we want to upgrade to a full subscription, then we can do this through a Parallels branded portal. This feels like a bait and switch to me. I did install the Kaspersky 2011 for Macintosh that is available now from Parallels' File menu, and it, too, offers the 3 month trial with offer to upgrade. I believe that if the marketing says "free," it should be clear that it's not a trial or limited time offer.

Operationally, Parallels feels a lot snappier than previous versions. I have commented on earlier version upgrades and also on dot releases that have been very, very welcome. This version seems to be one of them.

Starting Windows takes about 20% less time for me. Very obvious is a change in how the spinning ring cursors display. In Parallels 5, the Windows cursors would stutter. With Parallels 6, the stuttering is almost gone. I never knew the source of the stuttering, but the folks at Parallels have managed to smooth it out. Applications launch much, much faster and do not pause as long when displaying windows and menus. Another benefit is that my fans on the MacBook don't immediately max out when I start Windows. 

I find the reduced fans to be the most telling indicator of how well the folks at Parallels have optimized the virtual machine code to pass as much as possible on to the Mac without having to do the heavy lifting. Perhaps that's the new drivers I noticed when upgrading the VM? I don't know, but it's welcome!

All in all, I find this to be a buyworthy upgrade. Hopefully, there will be a better path to virus protection that doesn't make me buy a subscription to my "free" virus protection. I have a Norton subscription already with at least a year remaining; I'd rather transfer that than buy a new Kaspersky.
Enhanced by Zemanta
Adobe announced today that it would resume development of the Packager for iPhone, a feature of Flash Professional CS5 that lets developers export their Flash projects to iPhone apps and also to publish them to the App store.


It also states that in addition to renewing a commitment to the iPhone platform, 

Adobe will continue to work with key industry partners, including Google, RIM, Nokia, Motorola and Palm/HP to enable their device users to browse the full web through Flash Player 10.1 and run standalone applications on AIR.

All in all, this is more great news for all mobile developers. Having Flash as a single point of development with deployment options to web, AIR, and iOS, will accelerate innovation in the mobile sector in the coming months. It will also lead to consistency in applications across platforms, which is a big help for companies when making branding decisions.
Enhanced by Zemanta
Apple announced today that it has relaxed restrictions on development for iPhone and other iOS devices.


Quoting the statement,

We have listened to our developers and taken much of their feedback to heart. Based on their input, today we are making some important changes to our iOS Developer Program license in sections 3.3.1, 3.3.2 and 3.3.9 to relax some restrictions we put in place earlier this year.

This is HUGE and welcome by the folks who have been both building apps and app development environments. Adobe announced that Flash Professional CS5 would enable iPhone development, and Apple responded by cutting off all non-XCode developers. This reversal is great news for the developer community, and will bring more innovative content to the iOS platform.
Enhanced by Zemanta
Enfocus Software, an Esko Artwork company, announced that its PitStop Server 10 will feature automated transparency flattening.

While this may not seem like big news to a lot of folks, to print shops that rely on PostScript or PDF 1.3 RIPs will find this to be a welcome addition. Customers who use Adobe Creative Suite applications and QuarkXPress can produce PDFs with transparent content. Drop shadows, for instance, are used by a lot of designers and are transparent objects. These become problems when the prepress departments try to RIP these PDFs when they don't have a RIP that can flatten transparency.

Transparency flattening in these workflows then falls to the designer or to the prepress department before the file gets to the RIP. Acrobat is frequently used to flatten transparent PDFs, as is InDesign. Alternatively, shops demand PDF/X-1a files, since PDF/X-1a doesn't allow transparency and will force the creating application to flatten the transparency when the PDF gets created.

Having the ability to flatten transparency in a PitStop Server workflow removes this manual step in the workflow, and allows shops to fully automate preflight, transparency flattening, and correction of PDFs.
Enhanced by Zemanta
Adobe killed off Version Cue when it released Creative Suite 5. Unfortunately, I have several customers (including myself!) who continue to rely on Version Cue's integration with InDesign and InCopy, for instance. For some, it makes Creative Suite 5 untenable until a decision can be made about version control systems. Imagine our surprise, then, when Adobe released Adobe Drive 2 at Adobe Labs.

Adobe Drive CS4 enabled desktop connections to Version Cue and other Content Management Systems (CMS), but there were few CMS connectors other than the built-in Version Cue connector that ever saw the light of day. It also included connectors that allowed CS4 apps to display and manage versions within the application. In addition, it allowed checkin and checkout of files as well as version inspection from the desktop. Drive promised further integration with a broader range of content management systems, but when Adobe announced the demise of Version Cue, we all assumed the worst for Drive.

Adobe Drive 2 is software in Adobe Labs, so please be sure to back up your work frequently. Adobe calls it a Technology Preview, so consider yourself warned.

Adobe Drive 2 is the next iteration of Drive, and it does offer desktop access to both Version Cue and to other Digital Asset Management (DAM) systems through connectors. According to the CMIS for Adobe Drive Tech Note, 
Adobe provides some ready-made connectors. The CMIS Connector enables basic access to servers that implement the Content Management Interoperability Services (CMIS) specification. CMIS is a standard for improving interoperability between Digital Asset Management servers. It specifies a domain model, plus a set of services and protocol bindings for web services (SOAP) and AtomPub. See http://en.wikipedia.org/wiki/Content_Management_Interoperability_Services

Installing Drive 2 is done through the Adobe Application Manager. It installs the Adobe Drive application and infrastructure for Finder/Explorer, adds Version Cue and Adobe Drive support to Bridge CS5, and enables version control support in point products. InDesign, InCopy, Photohop and Illustrator all can talk directly to projects connected through Drive 2.

To connect to a CMS, start Drive 2 and click Add Drive. While Drive CS4 would automatically sniff out Version Cue servers, you need to tell Drive 2 the address and protocol for the connection. For a Version Cue server, enter: "versioncue://servername.com" without the quotes, and click Connect. 

VersionCue.png

You may want Version Cue to remember you to make future login faster. You can also choose to automatically mount the Version Cue server when your computer starts.

Once connected, you can browse existing projects in your file browser (Finder, Explorer) or Bridge CS5. You will need to login to the VC server from its web console to create new projects. While many people understand using Bridge to access Version Cue servers, let's talk about using the Finder (or Explorer).

To check out a file, select it in Finder or Explorer, then right click. Choose Adobe Drive... or Services... (Snow Leopard) then Adobe Drive... to see your Version Cue options. Choose Check Out to check out the file.

VersionCueFolderrightclickSL.png

Once you have it checked out, any changes you make will be local until you check the file back in to the project. 

VersionCueFolderrightclickCheckOut.png

Also, while you have the file checked out, other people who have access to the project will not be able to check it out. They need to check out a file to make changes, so you're the only one who can make changes while you have it checked out. Once you have saved your changes, check it back in to the Version Cue project. Right click on the file again to get the Drive menu, and choose Check In... If you choose Cancel Check out..., then any changes you have made to the file since you checked it out will be abandoned.

VersionCueFolderrightclickCheckIn.png

You will be asked to add version comments. This is important later when you are trying to find a specific previous version of the file. Comments will be visible when you choose Show Versions, or when users look at versions in either Bridge or CS5 applications.

VersionCueFolderrightclickCheckInComment.png

You can view versions at a later date by right clicking on the file and choosing Show Versions... from the contextual menu.

VersionCueFolderrightclickShowVersions.png

While many people think that Version Cue is only useful when used with Creative Suite apps, from Finder or Explorer, you can use any file type. This means that you can manage your Word or Powerpoint files as well as your QuarkXPress and Google Sketchup files. The important thing to remember is that the workflow requires that you check out and check in files when you want to make changes. If you double click on a file from Finder, it will open without checking it out. You've then removed it from the workflow.

So, what happens when I remove a file from the workflow by opening it without checking it out? You can still make changes, but the file is read only. If you want to keep the changes in the Version Cue project, you will simply need to check it out, then save it. Easy! When you're done editing, save it and check it in, remembering to add your version comments.

You can also promote previous versions to the current version as well as open previous versions on their own. Right click on the file, then choose Show Versions... from the Drive menu. From here, you can select a version and either promote it to the current version or open that previous version without promoting it. This is very handy when there's some content in a previous version that you want to use, but you don't want the entire file. You can open the previous version, then copy and paste that older version's content to the current version.

VersionCueFolderrightclickShowVersionsChoices.png

I encourage you to try out Drive 2, particularly if you used to use Version Cue with your CS4 or even CS3 projects. Having access to your Version Cue projects in CS5 is huge for those of us with legacy content in those servers, and also for those of us who don't want to have to learn a new CMS workflow.

For those of you who want to explore other CMS, Drive 2 also includes a content transfer function that lets you move files from your Version Cue projects to another project in a different CMS or to a folder. From Drive 2, choose Admin and then enter your credentials.

VersionCueProjectMigration.png

It is important to remember that this is software out of Labs and that it's not considered Released software. That having been said, it is certainly useful to try Drive to regain Version Cue functionality in your Creative Suite 5 apps. Using Drive as a connector to VC for other applications is functionality that existed in Drive CS4, but not many people used it. Perhaps we can change that with Drive 2.
Enhanced by Zemanta

About this Archive

This page is an archive of entries from September 2010 listed from newest to oldest.

August 2010 is the previous archive.

October 2010 is the next archive.

Find recent content on the main index or look in the archives to find all content.