Dr. Dobb's is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.


Channels ▼
RSS

.NET

.NET Components For Image Management


Vendor Support

Our customers rely on our software for their day-to-day business operations of managing and processing photographs, and excuses such as, "Oh, we get that code from someone else," are not acceptable. Once we ship a library, we need to stand behind it and ensure it works at the customer site. That means we rely on our vendors not just to support their products, but also to provide workable solutions to customer problems on a timely basis. In fact, I think one of the reasons component vendors continue to thrive despite the increasing functionality built into platform libraries is this support. After all, if the Windows .NET library doesn't read a particular TIFF file at a customer site, we're unlikely to get a Microsoft patch for our customer in real time.

The Selection Process

Given the small size of our team, our selection process needed to be efficient and quick. But at the same time, a mistake would be very expensive in terms of customer satisfaction—if we picked and shipped a library that didn't perform as expected. There was no shortage of Windows imaging toolkits on the market, but by going through our checklist of requirements, it was winnowed down to two. Feature for feature, the two looked almost the same. We decided that before committing to one, we needed to do some prototyping to really see how they would work. When we prototyped a portion of our functionality in each, we quickly began to see that it was only the "marketing hype" that was the same. With dotImage, we were able to implement the functionality we needed with a consistent API entirely in .NET. The competitor required us to use three different API sets—.NET, COM objects, and "C" DLLs—to get the functions we needed. This was a huge advantage for dotImage and nearly made our decision for us right there.

One of the most important requirements for professional photographers is accurate color rendering through color management—displaying images tagged with a particular color profile by calculating how they should appear given a second profile for the display, and optionally soft-proofing how they will appear on a printer by using a third printer profile in the display pipeline. We'd implemented our own color-management code, but it required two steps to display each image—render it in the vendor toolkit, then color correct it. We really wanted a toolkit that had this functionality built-in. Unfortunately, Atalasoft did not have color management in its products, while the competitor did.

Because Atalasoft's architecture was so elegant, rather than give up, we contacted the company and asked about plans for color management. Atalasoft said they were open to the idea and that if we were willing to give them a detailed specification on how it should work for photographic applications and test the results, they'd implement it in their next release. Obviously, this was appealing. By contrast, we had asked the competing vendor when they'd have a full .NET solution, but still had not received a solid answer. So we began to work with Atalasoft.

Not only did the original effort to help shape its color-management features work out, it also led to several years of productive cooperation on other topics that were of interest to our customers, including reading/writing metadata and viewing raw files directly from cameras. Atalasoft clearly takes customer requirements very seriously.


Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.