Adobe 29180248 User Guide - Page 58

Creating plug-in extension packages for InDesign CS5 and InCopy CS5 (version 5.0 only)

Get Adobe 29180248 - Photoshop Elements 5.0 PDF manuals and user guides
UPC - 883919001661
View all Adobe 29180248 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 58 highlights

Creating plug-in extension packages for InDesign CS5 and InCopy CS5 (version 5.0 only) Extension Manager CS5 supports plug-in extension package, which let you to include plug-ins for InDesign CS5 or InCopy CS5 in extensions. On Mac OS, one plug-in is one package. On Windows, one plug-in includes one binary file(usually have file extension ".pln") and one resource directory. To allow Extension Manager recognize plug-in, you need to specify its file type. On Mac OS, specify the plug-in file's type as "plugin", while on Windows, you need to specify the type of binary file(with file extension pln) as "plugin", but not for resource directory. File type of resource directory should be "ordinary". To specify file type, you need to specify attribute "file-type" in tag or attribute "default-file-type" in tag. There are two kinds of plug-in extensions: Enable_for_all_disable_for_one extension and Enable_for_one_disable_for_one extension. Creating Enable_for_all_disable_for_one extension packages Plug-ins included in an Enable_for_all_disable_for_one extension works for every user on the machine after one user installs this extension. While if one user disables or even removes the extension, plug-ins still work for other users in operating system. To create Enable_for_all_disable_for_one extension packages, you need to specify the attribute "plugin-manager-type" in tag as "all-users". And the destination of plug-ins needs to be inside the folder $indesign/Plug-Ins. Example Creating Enable_for_one_disable_for_one extension packages Plug-ins included in an Enable_for_one_disable_for_one works only for the user who installs this extension. And when user disables or removes this extension, no user in operating system could use plug-ins any more. To create Enable_for_one_disable_for_one extension packages, you need to specify the attribute "plugin-manager-type" in tag as "current-user". And the destination of plug-ins should not be inside the folder "$indesign/Plug-Ins". Example

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
58
Packaging Extensions with Extension Manager CS5
<file source="foo2" destination="$dreamweaver/configuration" />
</files>
Creating plug-in extension packages for InDesign CS5 and InCopy CS5 (version
5.0 only)
Extension Manager CS5 supports plug-in extension package, which let you to include plug-ins
for InDesign CS5 or InCopy CS5 in extensions. On Mac OS, one plug-in is one package. On
Windows, one plug-in includes one binary file(usually have file extension “.pln”) and one
resource directory. To allow Extension Manager recognize plug-in, you need to specify its file
type. On Mac OS, specify the plug-in file’s type as "
plugin
", while on Windows, you need to
specify the type of binary file(with file extension pln) as "
plugin
", but not for resource directory.
File type of resource directory should be "
ordinary
". To specify file type, you need to specify
attribute "
file-type
" in <
file
> tag or attribute "
default-file-type
" in <
files
> tag.
There are two kinds of plug-in extensions: Enable_for_all_disable_for_one extension and
Enable_for_one_disable_for_one extension.
Creating Enable_for_all_disable_for_one extension packages
Plug-ins included in an Enable_for_all_disable_for_one extension works for every user on the
machine after one user installs this extension. While if one user disables or even removes the
extension, plug-ins still work for other users in operating system.
To create Enable_for_all_disable_for_one extension packages, you need to specify the attribute
"
plugin-manager-type
" in tag <
macromedia-extension
> as "
all-users
". And the
destination of plug-ins needs to be inside the folder $indesign/Plug-Ins.
Example
<macromedia-extension
name="Enable_for_all_disable_for_one_sample"
version="1.0.0"
plugin-manager-type="all-users" >
<files>
<file source="sample.pln" destination="$indesign/Plug-Ins/sample/
sample.pln" platform="win" file-type="plugin" />
<file source="(sample Resources)" destination="$indesign/Plug-Ins/sample"
platform="win" />
<file source="sample.InDesignPlugin" destination="$indesign/Plug-Ins/
sample/sample.pln" platform="mac" file-type="plugin" />
</files>
Creating Enable_for_one_disable_for_one extension packages
Plug-ins included in an Enable_for_one_disable_for_one works only for the user who installs this
extension. And when user disables or removes this extension, no user in operating system could
use plug-ins any more.
To create Enable_for_one_disable_for_one extension packages, you need to specify the attribute
"
plugin-manager-type
" in tag <
macromedia-extension
> as "
current-user
". And the
destination of plug-ins should not be inside the folder "$indesign/Plug-Ins".
Example
<macromedia-extension