Datei: NDOPackage/VSCommandTable.vsct

Last Commit (8c4b1f0)
1 <?xml version="1.0" encoding="utf-8"?>
2 <CommandTable xmlns="http://schemas.microsoft.com/VisualStudio/2005-10-18/CommandTable" xmlns:xs="http://www.w3.org/2001/XMLSchema">
3
4 ····<!--··This is the file that defines the actual layout and type of the commands.
5 ········It is divided in different sections (e.g. command definition, command
6 ········placement, ...), with each defining a specific set of properties.
7 ········See the comment before each section for more details about how to
8 ········use it. -->
9
10 ····<!--··The VSCT compiler (the tool that translates this file into the binary
11 ········format that VisualStudio will consume) has the ability to run a preprocessor
12 ········on the vsct file; this preprocessor is (usually) the C++ preprocessor, so
13 ········it is possible to define includes and macros with the same syntax used
14 ········in C++ files. Using this ability of the compiler here, we include some files
15 ········defining some of the constants that we will use inside the file. -->
16
17 ····<!--This is the file that defines the IDs for all the commands exposed by VisualStudio. -->
18 ····<Extern href="stdidcmd.h"/>
19
20 ····<!--This header contains the command ids for the menus provided by the shell. -->
21 ····<Extern href="vsshlids.h"/>
22 ····<Include href="VSGlobals.vsct"/>
23
24
25 ····<!--The Commands section is where we the commands, menus and menu groups are defined.
26 ······This section uses a Guid to identify the package that provides the command defined inside it. -->
27 ····<Commands package="NDOPackage">
28 ········<!-- Inside this section we have different sub-sections: one for the menus, another··
29 ····for the menu groups, one for the buttons (the actual commands), one for the combos
30 ····and the last one for the bitmaps used. Each element is identified by a command id that··
31 ····is a unique pair of guid and numeric identifier; the guid part of the identifier is usually··
32 ····called "command set" and is used to group different command inside a logically related··
33 ····group; your package should define its own command set in order to avoid collisions··
34 ····with command ids defined by other packages. -->
35
36 ········<Menus>
37 ············<Menu guid="guidNDOPackageCmdSet" id="NDOToolbar" type="Toolbar">
38 ················<CommandFlag>DefaultDocked</CommandFlag>
39 ················<Strings>
40 <ButtonText>. NET Data Objects 4</ButtonText>
41 <CommandName>. NET Data Objects 4</CommandName>
42 ················</Strings>
43 ············</Menu>
44 ········</Menus>
45 ········<!-- In this section you can define new menu groups. A menu group is a container for
46 ········ other menus or buttons (commands); from a visual point of view you can see the
47 ········ group as the part of a menu contained between two lines. The parent of a group
48 ········ must be a menu. -->
49 ········<Groups>
50
51 ············<Group guid="guidNDOPackageCmdSet" id="NDOMenuGroup" priority="0x0000">
52 ················<Parent guid="guidNDOPackageCmdSet" id="NDOToolbar"/>
53 ············</Group>
54
55
56
57 ········</Groups>
58
59 ········<!--Buttons section. -->
60 ········<!--This section defines the elements the user can interact with, like a menu command or a button
61 ········or combo box in a toolbar. -->
62 ········<Buttons>
63 ············<!--To define a menu group you have to specify its ID, the parent menu and its display priority.
64 ··········The command is visible and enabled by default. If you need to change the visibility, status, etc, you can use
65 ··········the CommandFlag node.
66 ··········You can add more than one CommandFlag node e.g.:
67 ··············<CommandFlag>DefaultInvisible</CommandFlag>
68 ··············<CommandFlag>DynamicVisibility</CommandFlag>
69 ··········If you do not want an image next to your command, remove the Icon node /> -->
70
71 ············<Button guid="guidNDOPackageCmdSet" id="cmdidNDOConfiguration" priority="0x0100" type="Button">
72 ················<Parent guid="guidNDOPackageCmdSet" id="NDOMenuGroup" />
73 ················<Icon guid="guidImages" id="bmpConfiguration" />
74 ················<CommandFlag>DefaultDisabled</CommandFlag>
75 ················<Strings>
76 ····················<ButtonText>NDO Configuration</ButtonText>
77 ················</Strings>
78 ············</Button>
79
80 ············<Button guid="guidNDOPackageCmdSet" id="cmdidAddRelation" priority="0x0100" type="Button">
81 ················<Parent guid="guidNDOPackageCmdSet" id="NDOMenuGroup" />
82 ················<Icon guid="guidImages" id="bmpAddRelation" />
83 ················<CommandFlag>DefaultDisabled</CommandFlag>
84 ················<Strings>
85 ····················<ButtonText>Add Relation</ButtonText>
86 ················</Strings>
87 ············</Button>
88 ············
89 ············<Button guid="guidNDOPackageCmdSet" id="cmdidAddAccessor" priority="0x0100" type="Button">
90 ················<Parent guid="guidNDOPackageCmdSet" id="NDOMenuGroup" />
91 ················<Icon guid="guidImages" id="bmpAddAccessor" />
92 ················<CommandFlag>DefaultDisabled</CommandFlag>
93 ················<Strings>
94 ····················<ButtonText>Add Accessor Property</ButtonText>
95 ················</Strings>
96 ············</Button>
97 ················
98 ············<Button guid="guidNDOPackageCmdSet" id="cmdidAddClass" priority="0x0100" type="Button">
99 ················<Parent guid="guidNDOPackageCmdSet" id="NDOMenuGroup" />
100 ················<Icon guid="guidImages" id="bmpAddClass" />
101 ················<CommandFlag>DefaultDisabled</CommandFlag>
102 ················<Strings>
103 ····················<ButtonText>Add Persistent Class</ButtonText>
104 ················</Strings>
105 ············</Button>
106 ················
107 ············<Button guid="guidNDOPackageCmdSet" id="cmdidOpenMappingTool" priority="0x0100" type="Button">
108 ················<Parent guid="guidNDOPackageCmdSet" id="NDOMenuGroup" />
109 ················<Icon guid="guidImages" id="bmpOpenMappingTool" />
110 ················<CommandFlag>DefaultDisabled</CommandFlag>
111 ················<Strings>
112 ····················<ButtonText>Open Mapping Tool</ButtonText>
113 ················</Strings>
114 ············</Button>
115
116 ······<!--Button guid="guidNDOPackageCmdSet" id="cmdidOpenClassGenerator" priority="0x0100" type="Button">
117 ················<Parent guid="guidNDOPackageCmdSet" id="NDOMenuGroup" />
118 ················<Icon guid="guidImages" id="bmpOpenClassGenerator" />
119 ················<CommandFlag>DefaultDisabled</CommandFlag>
120 ················<Strings>
121 ····················<ButtonText>Open Class Generator</ButtonText>
122 ················</Strings>
123 ············</Button-->················
124
125 ········</Buttons>
126
127 ········<!--The bitmaps section is used to define the bitmaps that are used for the commands.-->
128 ········<Bitmaps>
129 ············<!--··The bitmap id is defined in a way that is a little bit different from the others:
130 ············the declaration starts with a guid for the bitmap strip, then there is the resource id of the
131 ············bitmap strip containing the bitmaps and then there are the numeric ids of the elements used
132 ············inside a button definition. An important aspect of this declaration is that the element id
133 ············must be the actual index (1-based) of the bitmap inside the bitmap strip. -->
134 ············<Bitmap guid="guidImages" href="Resources\Images.png" usedList="bmpConfiguration, bmpAddRelation, bmpAddAccessor, bmpAddClass, bmpOpenMappingTool, bmpOpenClassGenerator"/>
135
136 ········</Bitmaps>
137
138 ····</Commands>
139
140
141
142
143
144 ····<Symbols>
145 ········<!-- This is the package guid. -->
146 ········<GuidSymbol name="NDOPackage" value="{9a3bfde0-3b01-4a99-9ddc-1544345635fc}" />
147
148 ········<!-- This is the guid used to group the menu commands together -->
149 ········<GuidSymbol name="guidNDOPackageCmdSet" value="{7bf3372d-80b5-47ce-8104-704a904fcb3e}">
150
151 ············<IDSymbol name="NDOMenuGroup" value="0x1020" />
152 ············<IDSymbol name="cmdidNDOConfiguration" value="0x0100" />
153 ············<IDSymbol name="cmdidAddRelation" value="0x101" />
154 ············<IDSymbol name="cmdidAddAccessor" value="0x102" />
155 ············<IDSymbol name="cmdidAddClass" value="0x103" />
156 ············<IDSymbol name="cmdidOpenMappingTool" value="0x104" />
157 ············<IDSymbol name="cmdidOpenClassGenerator" value="0x105" />
158 ············<IDSymbol name="NDOToolbar" value="0x1000"/>
159 ········</GuidSymbol>
160
161
162
163 ········<GuidSymbol name="guidImages" value="{1c2bee68-81ce-4f37-bb4f-6460b14e8ed8}" >
164 ············<IDSymbol name="bmpConfiguration" value="1" />
165 ············<IDSymbol name="bmpAddRelation" value="2" />
166 ············<IDSymbol name="bmpAddAccessor" value="3" />
167 ············<IDSymbol name="bmpAddClass" value="4" />
168 ············<IDSymbol name="bmpOpenMappingTool" value="5" />
169 ············<IDSymbol name="bmpOpenClassGenerator" value="6" />
170 ········</GuidSymbol>
171 ····</Symbols>
172
173 </CommandTable>
174
New Commit (db278e7)
1 <?xml version="1.0" encoding="utf-8"?>
2 <CommandTable xmlns="http://schemas.microsoft.com/VisualStudio/2005-10-18/CommandTable" xmlns:xs="http://www.w3.org/2001/XMLSchema">
3
4 ····<!--··This is the file that defines the actual layout and type of the commands.
5 ········It is divided in different sections (e.g. command definition, command
6 ········placement, ...), with each defining a specific set of properties.
7 ········See the comment before each section for more details about how to
8 ········use it. -->
9
10 ····<!--··The VSCT compiler (the tool that translates this file into the binary
11 ········format that VisualStudio will consume) has the ability to run a preprocessor
12 ········on the vsct file; this preprocessor is (usually) the C++ preprocessor, so
13 ········it is possible to define includes and macros with the same syntax used
14 ········in C++ files. Using this ability of the compiler here, we include some files
15 ········defining some of the constants that we will use inside the file. -->
16
17 ····<!--This is the file that defines the IDs for all the commands exposed by VisualStudio. -->
18 ····<Extern href="stdidcmd.h"/>
19
20 ····<!--This header contains the command ids for the menus provided by the shell. -->
21 ····<Extern href="vsshlids.h"/>
22 ····<Include href="VSGlobals.vsct"/>
23
24
25 ····<!--The Commands section is where we the commands, menus and menu groups are defined.
26 ······This section uses a Guid to identify the package that provides the command defined inside it. -->
27 ····<Commands package="NDOPackage">
28 ········<!-- Inside this section we have different sub-sections: one for the menus, another··
29 ····for the menu groups, one for the buttons (the actual commands), one for the combos
30 ····and the last one for the bitmaps used. Each element is identified by a command id that··
31 ····is a unique pair of guid and numeric identifier; the guid part of the identifier is usually··
32 ····called "command set" and is used to group different command inside a logically related··
33 ····group; your package should define its own command set in order to avoid collisions··
34 ····with command ids defined by other packages. -->
35
36 ········<Menus>
37 ············<Menu guid="guidNDOPackageCmdSet" id="NDOToolbar" type="Toolbar">
38 ················<CommandFlag>DefaultDocked</CommandFlag>
39 ················<Strings>
40 <ButtonText>. NET Data Objects 5</ButtonText>
41 <CommandName>. NET Data Objects 5</CommandName>
42 ················</Strings>
43 ············</Menu>
44 ········</Menus>
45 ········<!-- In this section you can define new menu groups. A menu group is a container for
46 ········ other menus or buttons (commands); from a visual point of view you can see the
47 ········ group as the part of a menu contained between two lines. The parent of a group
48 ········ must be a menu. -->
49 ········<Groups>
50
51 ············<Group guid="guidNDOPackageCmdSet" id="NDOMenuGroup" priority="0x0000">
52 ················<Parent guid="guidNDOPackageCmdSet" id="NDOToolbar"/>
53 ············</Group>
54
55
56
57 ········</Groups>
58
59 ········<!--Buttons section. -->
60 ········<!--This section defines the elements the user can interact with, like a menu command or a button
61 ········or combo box in a toolbar. -->
62 ········<Buttons>
63 ············<!--To define a menu group you have to specify its ID, the parent menu and its display priority.
64 ··········The command is visible and enabled by default. If you need to change the visibility, status, etc, you can use
65 ··········the CommandFlag node.
66 ··········You can add more than one CommandFlag node e.g.:
67 ··············<CommandFlag>DefaultInvisible</CommandFlag>
68 ··············<CommandFlag>DynamicVisibility</CommandFlag>
69 ··········If you do not want an image next to your command, remove the Icon node /> -->
70
71 ············<Button guid="guidNDOPackageCmdSet" id="cmdidNDOConfiguration" priority="0x0100" type="Button">
72 ················<Parent guid="guidNDOPackageCmdSet" id="NDOMenuGroup" />
73 ················<Icon guid="guidImages" id="bmpConfiguration" />
74 ················<CommandFlag>DefaultDisabled</CommandFlag>
75 ················<Strings>
76 ····················<ButtonText>NDO Configuration</ButtonText>
77 ················</Strings>
78 ············</Button>
79
80 ············<Button guid="guidNDOPackageCmdSet" id="cmdidAddRelation" priority="0x0100" type="Button">
81 ················<Parent guid="guidNDOPackageCmdSet" id="NDOMenuGroup" />
82 ················<Icon guid="guidImages" id="bmpAddRelation" />
83 ················<CommandFlag>DefaultDisabled</CommandFlag>
84 ················<Strings>
85 ····················<ButtonText>Add Relation</ButtonText>
86 ················</Strings>
87 ············</Button>
88 ············
89 ············<Button guid="guidNDOPackageCmdSet" id="cmdidAddAccessor" priority="0x0100" type="Button">
90 ················<Parent guid="guidNDOPackageCmdSet" id="NDOMenuGroup" />
91 ················<Icon guid="guidImages" id="bmpAddAccessor" />
92 ················<CommandFlag>DefaultDisabled</CommandFlag>
93 ················<Strings>
94 ····················<ButtonText>Add Accessor Property</ButtonText>
95 ················</Strings>
96 ············</Button>
97 ················
98 ············<Button guid="guidNDOPackageCmdSet" id="cmdidAddClass" priority="0x0100" type="Button">
99 ················<Parent guid="guidNDOPackageCmdSet" id="NDOMenuGroup" />
100 ················<Icon guid="guidImages" id="bmpAddClass" />
101 ················<CommandFlag>DefaultDisabled</CommandFlag>
102 ················<Strings>
103 ····················<ButtonText>Add Persistent Class</ButtonText>
104 ················</Strings>
105 ············</Button>
106 ················
107 ············<Button guid="guidNDOPackageCmdSet" id="cmdidOpenMappingTool" priority="0x0100" type="Button">
108 ················<Parent guid="guidNDOPackageCmdSet" id="NDOMenuGroup" />
109 ················<Icon guid="guidImages" id="bmpOpenMappingTool" />
110 ················<CommandFlag>DefaultDisabled</CommandFlag>
111 ················<Strings>
112 ····················<ButtonText>Open Mapping Tool</ButtonText>
113 ················</Strings>
114 ············</Button>
115
116 ······<!--Button guid="guidNDOPackageCmdSet" id="cmdidOpenClassGenerator" priority="0x0100" type="Button">
117 ················<Parent guid="guidNDOPackageCmdSet" id="NDOMenuGroup" />
118 ················<Icon guid="guidImages" id="bmpOpenClassGenerator" />
119 ················<CommandFlag>DefaultDisabled</CommandFlag>
120 ················<Strings>
121 ····················<ButtonText>Open Class Generator</ButtonText>
122 ················</Strings>
123 ············</Button-->················
124
125 ········</Buttons>
126
127 ········<!--The bitmaps section is used to define the bitmaps that are used for the commands.-->
128 ········<Bitmaps>
129 ············<!--··The bitmap id is defined in a way that is a little bit different from the others:
130 ············the declaration starts with a guid for the bitmap strip, then there is the resource id of the
131 ············bitmap strip containing the bitmaps and then there are the numeric ids of the elements used
132 ············inside a button definition. An important aspect of this declaration is that the element id
133 ············must be the actual index (1-based) of the bitmap inside the bitmap strip. -->
134 ············<Bitmap guid="guidImages" href="Resources\Images.png" usedList="bmpConfiguration, bmpAddRelation, bmpAddAccessor, bmpAddClass, bmpOpenMappingTool, bmpOpenClassGenerator"/>
135
136 ········</Bitmaps>
137
138 ····</Commands>
139
140
141
142
143
144 ····<Symbols>
145 ········<!-- This is the package guid. -->
146 ········<GuidSymbol name="NDOPackage" value="{9a3bfde0-3b01-4a99-9ddc-1544345635fc}" />
147
148 ········<!-- This is the guid used to group the menu commands together -->
149 ········<GuidSymbol name="guidNDOPackageCmdSet" value="{7bf3372d-80b5-47ce-8104-704a904fcb3e}">
150
151 ············<IDSymbol name="NDOMenuGroup" value="0x1020" />
152 ············<IDSymbol name="cmdidNDOConfiguration" value="0x0100" />
153 ············<IDSymbol name="cmdidAddRelation" value="0x101" />
154 ············<IDSymbol name="cmdidAddAccessor" value="0x102" />
155 ············<IDSymbol name="cmdidAddClass" value="0x103" />
156 ············<IDSymbol name="cmdidOpenMappingTool" value="0x104" />
157 ············<IDSymbol name="cmdidOpenClassGenerator" value="0x105" />
158 ············<IDSymbol name="NDOToolbar" value="0x1000"/>
159 ········</GuidSymbol>
160
161
162
163 ········<GuidSymbol name="guidImages" value="{1c2bee68-81ce-4f37-bb4f-6460b14e8ed8}" >
164 ············<IDSymbol name="bmpConfiguration" value="1" />
165 ············<IDSymbol name="bmpAddRelation" value="2" />
166 ············<IDSymbol name="bmpAddAccessor" value="3" />
167 ············<IDSymbol name="bmpAddClass" value="4" />
168 ············<IDSymbol name="bmpOpenMappingTool" value="5" />
169 ············<IDSymbol name="bmpOpenClassGenerator" value="6" />
170 ········</GuidSymbol>
171 ····</Symbols>
172
173 </CommandTable>
174