Adobe 29180248 User Guide - Page 38

menu, The name of the menu to insert, as it will appear in the menu bar. To set the menu's access

Page 38 highlights

id ID for the new menu bar. Your menu IDs should start with a company name or some other namespace prefix to ensure uniqueness. In particular, don't start your menu IDs with DW, which is the prefix used by Dreamweaver menu IDs. platform Indicates that the menu bar should appear only on the given platform. Valid values are "win" and "mac". Contents None. Container This tag must be contained in a menu-insert tag. Example menu Description Describes a menu or submenu to be inserted into the application's menu structure during installation of an extension. Attributes name, id, {platform} name The name of the menu to insert, as it will appear in the menu bar. To set the menu's access key (mnemonic) on Windows, use an underscore (_) in front of the access letter. The underscore is automatically removed on Mac OS. id The menu ID of the new menu. Your menu IDs should start with a company name or some other namespace prefix to ensure uniqueness. In particular, don't start your menu IDs with DW, which is the prefix used by the Dreamweaver menu IDs. One useful approach is to prefix every ID with your domain name (with the elements reversed); for example, if your domain name is joe.com, you could start every ID with com.joe. to ensure uniqueness. platform Indicates that the menu should appear only on the given platform. Valid values are "win" and "mac". Contents None. Note: Always use a tag to close a tag. Although the tag in the MXI file has no contents, it corresponds to the tag in the menus.xml file, which does have contents. Therefore, the tag is not defined as an empty tag, so you can't use the /> XML syntax to close the tag. Container This tag must be contained in a menu-insert tag. Example 38 Packaging Extensions with Extension Manager CS5

  • 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

38
Packaging Extensions with Extension Manager CS5
id
ID for the new menu bar. Your menu IDs should start with a company name or some other
namespace prefix to ensure uniqueness. In particular, don’t start your menu IDs with
DW
, which is
the prefix used by Dreamweaver menu IDs.
platform
Indicates that the menu bar should appear only on the given platform. Valid values
are
"win"
and
"mac"
.
Contents
None.
Container
This tag must be contained in a
menu-insert
tag.
Example
<menubar name = "Mugwump Context menu" id = “JMMugwumpContext"
platform = "mac"></menubar>
menu
Description
Describes a menu or submenu to be inserted into the application’s menu structure during
installation of an extension.
Attributes
name
,
id
,
{platform}
name
The name of the menu to insert, as it will appear in the menu bar. To set the menu’s access
key (mnemonic) on Windows, use an underscore (_) in front of the access letter. The underscore
is automatically removed on Mac OS.
id
The menu ID of the new menu. Your menu IDs should start with a company name or some
other namespace prefix to ensure uniqueness. In particular, don’t start your menu IDs with
DW
,
which is the prefix used by the Dreamweaver menu IDs. One useful approach is to prefix every
ID with your domain name (with the elements reversed); for example, if your domain name is
joe.com, you could start every ID with
com.joe.
to ensure uniqueness.
platform
Indicates that the menu should appear only on the given platform. Valid values are
"win"
and
"mac"
.
Contents
None.
Note:
Always use a
</menu>
tag to close a
<menu>
tag. Although the
<menu>
tag in the MXI file has no contents, it
corresponds to the
<menu>
tag in the menus.xml file, which does have contents. Therefore, the
<menu>
tag is not
defined as an empty tag, so you can’t use the
/>
XML syntax to close the tag.
Container
This tag must be contained in a
menu-insert
tag.
Example
<menu name = "Recent Frobs Converted" id = "JMMenu_Commands_RecentFrobs"
platform = "mac" >
</menu>