Adobe Desktop Technologies Ascend to the Cloud

Adobe Photoshop is the premiere desktop tool for editing images. It offers the most powerful algorithms for image processing available anywhere, and is loved by creative people around the world. Not only is it ubiquitous in design shops, it is also used by companies (like ourselves) who generate dynamic content with it.

Photoshop is well-exposed to automation: it has actions that are easy for non-developers (yet quite powerful), and it also supports ExtendScript, as well as C++ and CEP (Adobe's Common Extensibility Platform). XMPie is a company that has actually built a product, uImage, that runs Photoshop desktop like a server to produce one-to-one marketing pieces.

Until now, the Photoshop rendition engine has only been available through the desktop application. However, Adobe has just announced the pre-release program for Photoshop as a Service.

How do I keep previous versions of an Adobe CC application as I install the new one?

What is the trick? On install, select "Advanced Options" and uncheck "Remove Previous Versions". That's it! And you'll keep your older versions of InDesign (or Photoshop, or whatever).

How do I get back a previous version of an Adobe CC application that was unintentionally removed?

Adobe has answered this really well here. We hope you don't wind up there, but the bottom line is that earlier versions of Creative Cloud are easily available as needed. It really is quite simple:

Seven years ago, Silicon Publishing stumbled into an opportunity to connect Adobe InDesign to remote assets in a very powerful and efficient way. Through the work of our developers, several of whom were part of the original team that built Adobe InDesign, we were able to make a very direct connection from InDesign to remote assets via URLs. Since that time, InDesign DAM Connectivity has become a significant part of our work.

While other approaches rely on technologies such as WebDAV, which is known for latency and headaches, our direct approach has proven itself to be far more efficient, and is now the way that most leading DAMs handle such connectivity. We have over 25 DAM partnerships so far, with more on the way.

This post talks about 10 of the DAMs we've encountered, which happen to represent a great cross-section of the DAMs out there today. First, I will share an overview of what DAM is, heavily borrowing from the wonderful work of DAM guru Theresa Regli, whose book Digital and Marketing Asset Managment: the Real Story about DAM Technology and Practice is an essential guide for anyone in this space.

Adobe InDesign is the tool of choice for page layout, yet it is a relatively old piece of software, originating in the late 1990s. While InDesign has a concept of "links", its initial approach to graphic references was fundamentally that of desktop software prior to the age of the world wide web. Concepts of linked text in InDesign have evolved slowly over the past 15 years.

A link in InDesign is not, by default, a URL, as one might expect of today's programs. Instead, InDesign links are pointers to assets that are local (on the physical drive of the computer running InDesign) or available across the local network (via a network share). A simple plug-in (our Silicon Connector) can bring InDesign into the modern age, where true URLs enable cloud-based workflows, but we'll get to that later.

Historically, Silicon Publishing has delivered publishing solutions across a gamut of communications channels. In the first place, our Silicon Paginator product (first released in 2005 as the "XML Formatting Engine"), is a platform for flowing data through InDesign templates. As in traditional XML publishing, Paginator generates web, email, print and mobile app output from a single rendition-agnostic content source (or from diverse, orchestrated, content sources).

Multi-channel rendition, connectivity and interfacing are persistent themes in our practice, ever since the late 1990s when "multi-channel" became a buzzword to deer-in-the-headlights printers faced with the need to generalize into "communications" from the too-physical, too-easily-commoditized, craft of print.

I remember a channel called "CD-ROM" and now face channels such as "WebVR", "IoT", and "geolocated social" - the only constant is change.

It started with a naive InDesign user

Silicon Connector first saw the light of day in 2010, when we at Silicon Publishing were building a large-scale online editing solution for a major client. Our solution was based on Adobe InDesign and Adobe InDesign Server, which were brand-new to this tech-savvy and ambitious organization we were working with. Although the client instantly understood the superiority of InDesign for page rendition and output quality, they looked at InDesign with very fresh eyes and came up with a big feature request.

“These links are barbaric!” said their brilliant technology lead. “They go to the file system, not to URLs as a real link should in this day and age.”

As leading resellers of the product, we are asked time and time again to help people to try Adobe InDesign Server, and how to install the trial or licensed versions of the product. We have distilled simple instructions here for trying the latest version, and installing the licensed version once you're certain you wish to buy it. We love this product and want others to enjoy it.

Silicon Publishing co-founder and CEO talks of Silicon Publishing's origins, where they are today, and where they are headed in the future in this interview with Superb Crew.

Since the year 2000, we at Silicon Publishing have carried on a tradition we first encountered from our former life at Bertelsmann Industry Services (a now defunct company with its own 20-year history): database publishing. We automate the flow of data through templates, producing the entire spectrum of documents that can be generated from data:

  • Catalogs
  • Directories
  • Financial statements
  • Insurance documents
  • Report cards
  • One-to-one marketing pieces
  • Practically anything you can think of...

 

The diversity of "data-generated documents" has surprised me ever since I started working in this business. 20 years ago, we were still producing internal phone directories for companies such as Chevron and Mobile, large organizations that spewed forth paper to communicate information before the web took over.

SVG certainly crashed and burned before it rose like a phoenix from the ashes...

Sometime in 1998, a former co-worker who had gone to work at Adobe came by my office at Bertlesmann to inform me of a brand new technology that she knew would excite me: PGML, or "Precision Graphics Markup Language." This was the Adobe flavor of XML for Vector Graphics. As Jon Warnock put it at the time:

"The PGML proposal solves a growing need for a precise specification that enables members of the Web community to readily and reliably post, control and interact with graphics on the Web."

I fell for it, hook, line and sinker, and ever since that time, I have followed the standards for XML-based vector graphics closely. PGML (mainly from Adobe) and VML (mainly from Microsoft), as well as a few other similar efforts (Web Schematics, Hyper Graphics Markup Language, WebCGM, and DrawML) soon merged into a "real" W3C standard, called Scalable Vector Graphics (SVG). This promised to serve as a format for rendering interactive vector graphics in Web browsers, which at that time (the era of Netscape Navigator 4.7 and Internet Explorer 5) was only possible with Macromedia Flash.

Completely obvious in the year 2000

What made SVG so cool? It could almost be considered "PostScript for the Web," so it certainly made sense for Adobe to sponsor and support it in its infancy: with SVG (as with PostScript), art was primarily described via vectors, a method far more efficient (and more naturally "scalable") than using raster images.

1 2 3

Recent Posts