Difference between revisions of "AppGranule"

From DocDataFlow
Jump to: navigation, search
 
(2 intermediate revisions by one user not shown)
Line 1: Line 1:
 +
= General Info =
 +
 
An AppGranule represents a particular application - e.g. Adobe InDesign, Illustrator, QuarkXPress...
 
An AppGranule represents a particular application - e.g. Adobe InDesign, Illustrator, QuarkXPress...
  
Line 11: Line 13:
 
E.g. when running an InDesign-to-something conversion, the 'host' application will be InDesign, and there will be a single InDesignAppGranule available.
 
E.g. when running an InDesign-to-something conversion, the 'host' application will be InDesign, and there will be a single InDesignAppGranule available.
  
[[AppGranule Code|AppGranule info for developers]]
+
= Developer Info =
 +
[[AppGranule Code|AppGranule Documentation]]

Latest revision as of 01:23, 30 December 2013

General Info

An AppGranule represents a particular application - e.g. Adobe InDesign, Illustrator, QuarkXPress...

AppGranule normally don't roam the data flow. Instead they represent the application that's hosting the current Crawler conversion.

The AppGranule provides an easy 'repository' for application-specific data.

Another function of the AppGranule is to serve as the 'parent granule' of all 'top level' granules.

Normally, there is only a single AppGranule for the current Crawler session.

E.g. when running an InDesign-to-something conversion, the 'host' application will be InDesign, and there will be a single InDesignAppGranule available.

Developer Info

AppGranule Documentation