Create a multilevel submenu in Visual Studio Tools menu - vspackage

Create a multilevel submenu in Visual Studio Tools menu
I am looking to create a multilevel menu within the Visual Studio Tools menu.
I would want the structure as seen to be something like below.
Tools
|->GC
|->Licenses--------------------------->|
|->Samples |-> Activate
|-> Deactivate
From the below code in the .vsct file, I am able to get to the structure as below
Tools|
|->GC->|
|->Licenses
|->Samples.
How would I be able to add a submenu "Licenses" into the GC menu and add the Activate/Deactivate buttons to it?
<CommandTable xmlns="http://schemas.microsoft.com/VisualStudio/2005-10-18/CommandTable" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<Extern href="stdidcmd.h"/>
<Extern href="vsshlids.h"/>
<Commands package="guidComponentOneMenuPackage">
<Menus>
<Menu guid="guidComponentOneMenuPackageCmdSet" id="TopLevelMenu" priority="0x700" type="Menu">
<Parent guid="guidSHLMainMenu" id="IDG_VS_TOOLS_EXT_TOOLS" />
<Strings>
<ButtonText>GC</ButtonText>
<CommandName>GC</CommandName>
</Strings>
</Menu>
</Menus>
<Groups>
<Group guid="guidComponentOneMenuPackageCmdSet" id="MyMenuGroup" priority="0x0600">
<Parent guid="guidComponentOneMenuPackageCmdSet" id="TopLevelMenu"/>
</Group>
</Groups>
<Buttons>
<Button guid="guidComponentOneMenuPackageCmdSet" id="LicenseManagerId" priority="0x0100" type="Button">
<Parent guid="guidComponentOneMenuPackageCmdSet" id="MyMenuGroup" />
<Icon guid="guidImages" id="bmpPic1" />
<Strings>
<ButtonText>Licenses</ButtonText>
</Strings>
</Button>
<Button guid="guidComponentOneMenuPackageCmdSet" id="SamplesExplorerId" priority="0x0101" type="Button">
<Parent guid="guidComponentOneMenuPackageCmdSet" id="MyMenuGroup" />
<Icon guid="guidImages" id="bmpPic1" />
<Strings>
<ButtonText>Samples</ButtonText>
</Strings>
</Button>
</Buttons>
<Bitmaps>
<Bitmap guid="guidImages" href="Resources\GC.png" usedList="bmpPic1"/>
</Bitmaps>
</Commands>
<Symbols>
<GuidSymbol name="guidComponentOneMenuPackage" value="{458b53ac-7a4e-440d-aebf-d3eec4fd24e2}" />
<GuidSymbol name="guidComponentOneMenuPackageCmdSet" value="{d2b0b608-ab47-47c6-a9a3-d0cf3b64157b}">
<IDSymbol name="MyMenuGroup" value="0x1020" />
<IDSymbol name="LicenseManagerId" value="0x0100" />
<IDSymbol name="SamplesExplorerId" value="0x0101" />
<IDSymbol name="TopLevelMenu" value="0x1021"/>
</GuidSymbol>
<GuidSymbol name="guidImages" value="{6e5edeb3-274c-4147-a06d-7f50f10160b9}" >
<IDSymbol name="bmpPic1" value="1" />
</GuidSymbol>
</Symbols>
</CommandTable>

We will be able to create multilevel menus by merely adding more groups and setting their priority as below.
<CommandTable xmlns="http://schemas.microsoft.com/VisualStudio/2005-10-18 /CommandTable" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<Extern href="stdidcmd.h"/>
<Extern href="vsshlids.h"/>
<Commands package="guidComponentOneMenuPackage">
<Menus>
<Menu guid="guidComponentOneMenuPackageCmdSet" id="TopLevelMenu" priority="0x700" type="Menu">
<Parent guid="guidSHLMainMenu" id="IDG_VS_TOOLS_EXT_TOOLS" />
<Strings>
<ButtonText>GC</ButtonText>
<CommandName>GC</CommandName>
</Strings>
</Menu>
<Menu guid="guidComponentOneMenuPackageCmdSet" id="GCMenu" priority="0x0200" type="Menu">
<Parent guid="guidComponentOneMenuPackageCmdSet" id="MyMenuGroup" />
<Strings>
<ButtonText>Main</ButtonText>
<CommandName>Main</CommandName>
</Strings>
</Menu>
</Menus>
<Groups>
<Group guid="guidComponentOneMenuPackageCmdSet" id="GCGroup" priority="0x0600">
<Parent guid="guidComponentOneMenuPackageCmdSet" id="GCMenu"/>
</Group>
<Group guid="guidComponentOneMenuPackageCmdSet" id="MyMenuGroup" priority="0x0600">
<Parent guid="guidComponentOneMenuPackageCmdSet" id="TopLevelMenu"/>
</Group>
</Groups>
<Buttons>
<Button guid="guidComponentOneMenuPackageCmdSet" id="LicenseManagerId" priority="0x0201" type="Button">
<Parent guid="guidComponentOneMenuPackageCmdSet" id="GCGroup" />
<Icon guid="guidImages" id="bmpPic1" />
<Strings>
<ButtonText>Licenses</ButtonText>
</Strings>
</Button>
<Button guid="guidComponentOneMenuPackageCmdSet" id="SamplesExplorerId" priority="0x0202" type="Button">
<Parent guid="guidComponentOneMenuPackageCmdSet" id="GCGroup" />
<Icon guid="guidImages" id="bmpPic1" />
<Strings>
<ButtonText>Samples</ButtonText>
</Strings>
</Button>
</Buttons>
<Bitmaps>
</Bitmaps>
</Commands>
<Symbols>
<IDSymbol name="MyMenuGroup" value="0x1020" />
<IDSymbol name="GCGroup" value="0x0202" />
<IDSymbol name="LicenseManagerId" value="0x0100" />
<IDSymbol name="SamplesExplorerId" value="0x0101" />
<IDSymbol name="TopLevelMenu" value="0x1021"/>
<IDSymbol name="GCMenu" value="0x1022"/>
</GuidSymbol>
</Symbols>
</CommandTable>

Related

UI to manage one to many relationship between classes in custom module in Kentico

I have created a Clinic module within Kentico V12 with two classes: Doctor and Appointment. There is a 1 to many relationship between Doctor and Appointment. How could I display the name and surname of the doctors in the Appointment grid?
<?xml version="1.0" encoding="utf-8" ?>
<grid>
<actions>
<action name="edit" caption="$General.Edit$" fonticonclass="icon-edit" fonticonstyle="allow" />
<action name="#delete" caption="$General.Delete$" fonticonclass="icon-bin" fonticonstyle="critical" confirmation="$General.ConfirmDelete$" />
</actions>
<columns>
<column source="AppointmentPatientFirstName" caption="First name" wrap="false" localize="true">
<filter type="text" size="200" />
</column>
<column source="AppointmentPatientLastName" caption="Last name" wrap="false" localize="true">
<filter type="text" size="200" />
</column>
<column source="AppointmentPatientEmail" caption="Email" wrap="false" localize="true">
<filter type="text" size="200" />
</column>
<column source="AppointmentPatientPhoneNumber" caption="Phone Number" wrap="false" localize="true">
<filter type="text" size="15" />
</column>
<column source="Date" caption="Date" wrap="false" localize="true">
<filter type="text" size="200" />
</column>
<column source="AppointmentPatientBirthDate" caption="BirthDate" wrap="false" localize="true">
<filter type="text" size="200" />
</column>
<column source="AppointmentDoctorID" caption="Doctor ID" wrap="false" localize="true">
<filter type="text" size="200" />
</column>
</columns>
<options>
<key name="DisplayFilter" value="true" />
</options>
</grid>
Kind regards.
Appointment List: https://i.stack.imgur.com/Ft1pE.png
Using this column AppointmentDoctorID modify the XML to use a transformation like so:
<column source="AppointmentDoctorID" caption="Doctor" externalsourcename="#transform: yournamespace.doctor: {%FirstName%} {%LastName%}" wrap="false" localize="true"></column>
Check out more documentation on unigrids in the Kentico Documentation.

When implementing a VSPackage (VSIX) for VS2015, how do I get my new commands listed in Options-Keyboard?

I have just created my first VSPackage (since VS2015 doesn't support AddIns).
While I have managed to assign keyboard shortcuts within my VSPackage (using KeyBindings), I have found that the commands themselves do not seem to be listed within the Options-Keyboard tab in Visual Studio.
I notice that the other extensions that I have installed include their commands for assigning within Options-Keyboard.
What must I do to get mine included?
Here are the full contents of my VSCT file - apologies if there's a better way to attach this, but I couldn't find one:
<?xml version="1.0" encoding="utf-8"?>
<CommandTable xmlns="http://schemas.microsoft.com/VisualStudio/2005-10-18/CommandTable" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<!-- This is the file that defines the actual layout and type of the commands.
It is divided in different sections (e.g. command definition, command
placement, ...), with each defining a specific set of properties.
See the comment before each section for more details about how to
use it. -->
<!-- The VSCT compiler (the tool that translates this file into the binary
format that VisualStudio will consume) has the ability to run a preprocessor
on the vsct file; this preprocessor is (usually) the C++ preprocessor, so
it is possible to define includes and macros with the same syntax used
in C++ files. Using this ability of the compiler here, we include some files
defining some of the constants that we will use inside the file. -->
<!--This is the file that defines the IDs for all the commands exposed by VisualStudio. -->
<Extern href="stdidcmd.h" />
<!--This header contains the command ids for the menus provided by the shell. -->
<Extern href="vsshlids.h" />
<!--The Commands section is where commands, menus, and menu groups are defined.
This section uses a Guid to identify the package that provides the command defined inside it. -->
<Commands package="guidDanBarPackage">
<!-- Inside this section we have different sub-sections: one for the menus, another
for the menu groups, one for the buttons (the actual commands), one for the combos
and the last one for the bitmaps used. Each element is identified by a command id that
is a unique pair of guid and numeric identifier; the guid part of the identifier is usually
called "command set" and is used to group different command inside a logically related
group; your package should define its own command set in order to avoid collisions
with command ids defined by other packages. -->
<Menus>
<Menu guid="guidDanBarPackageCmdSet" id="MyToolbar" type="Toolbar">
<CommandFlag>DefaultDocked</CommandFlag>
<Strings>
<ButtonText>Dan Bar</ButtonText>
<CommandName>Dan Bar</CommandName>
</Strings>
</Menu>
</Menus>
<Menus>
<Menu guid="guidDanBarPackageCmdSet" id="BriefToolbar" type="Toolbar">
<CommandFlag>DefaultDocked</CommandFlag>
<Strings>
<ButtonText>Dan Brief Bar</ButtonText>
<CommandName>Dan Brief Bar</CommandName>
</Strings>
</Menu>
</Menus>
<!-- In this section you can define new menu groups. A menu group is a container for
other menus or buttons (commands); from a visual point of view you can see the
group as the part of a menu contained between two lines. The parent of a group
must be a menu. -->
<Groups>
<Group guid="guidDanBarPackageCmdSet" id="MyToolbarGroup" priority="0x0000">
<Parent guid="guidDanBarPackageCmdSet" id="MyToolbar" />
</Group>
<Group guid="guidDanBarPackageCmdSet" id="BriefToolbarGroup" priority="0x0000">
<Parent guid="guidDanBarPackageCmdSet" id="BriefToolbar" />
</Group>
</Groups>
<!--Buttons section. -->
<!--This section defines the elements the user can interact with, like a menu command or a button
or combo box in a toolbar. -->
<Buttons>
<!--To define a menu group you have to specify its ID, the parent menu and its display priority.
The command is visible and enabled by default. If you need to change the visibility, status, etc, you can use
the CommandFlag node.
You can add more than one CommandFlag node e.g.:
<CommandFlag>DefaultInvisible</CommandFlag>
<CommandFlag>DynamicVisibility</CommandFlag>
If you do not want an image next to your command, remove the Icon node /> -->
<Button guid="guidDanBarPackageCmdSet" id="cmdidConcurrentBuilds" priority="0x0100" type="Button">
<Parent guid="guidDanBarPackageCmdSet" id="MyToolbarGroup" />
<Icon guid="guidDanBarImages" id="bmpPic1" />
<Strings>
<ButtonText>Set Concurrent Builds</ButtonText>
</Strings>
</Button>
<Button guid="guidDanBarPackageCmdSet" id="cmdidTrackInSolutionExplorer" priority="0x0100" type="Button">
<Parent guid="guidDanBarPackageCmdSet" id="MyToolbarGroup" />
<Icon guid="guidDanBarImages" id="bmpPic2" />
<Strings>
<ButtonText>Track In Solution Explorer</ButtonText>
</Strings>
</Button>
<Button guid="guidDanBarPackageCmdSet" id="cmdidBuildStartupProject" priority="0x0100" type="Button">
<Parent guid="guidDanBarPackageCmdSet" id="MyToolbarGroup" />
<Icon guid="guidDanBarImages" id="bmpPic3" />
<Strings>
<ButtonText>Build Startup Project</ButtonText>
</Strings>
</Button>
<Button guid="guidDanBarPackageCmdSet" id="cmdidCommentOutParam" priority="0x0100" type="Button">
<Parent guid="guidDanBarPackageCmdSet" id="MyToolbarGroup" />
<Icon guid="guidDanBarImages" id="bmpPic4" />
<Strings>
<ButtonText>Comment Out Parameter</ButtonText>
</Strings>
</Button>
<Button guid="guidDanBarPackageCmdSet" id="cmdidInsertRegion" priority="0x0100" type="Button">
<Parent guid="guidDanBarPackageCmdSet" id="MyToolbarGroup" />
<Icon guid="guidDanBarImages" id="bmpPic5" />
<Strings>
<ButtonText>Insert Region</ButtonText>
</Strings>
</Button>
<Button guid="guidDanBarPackageCmdSet" id="cmdidXMLCommentFull" priority="0x0100" type="Button">
<Parent guid="guidDanBarPackageCmdSet" id="MyToolbarGroup" />
<Icon guid="guidDanBarImages" id="bmpPic6" />
<Strings>
<ButtonText>Full XML Comment</ButtonText>
</Strings>
</Button>
<Button guid="guidDanBarPackageCmdSet" id="cmdidXMLCommentSmall" priority="0x0100" type="Button">
<Parent guid="guidDanBarPackageCmdSet" id="MyToolbarGroup" />
<Icon guid="guidDanBarImages" id="bmpPic7" />
<Strings>
<ButtonText>Small XML Comment</ButtonText>
</Strings>
</Button>
<Button guid="guidDanBarPackageCmdSet" id="cmdidXMLCommentTiny" priority="0x0100" type="Button">
<Parent guid="guidDanBarPackageCmdSet" id="MyToolbarGroup" />
<Icon guid="guidDanBarImages" id="bmpPic8" />
<Strings>
<ButtonText>Tiny XML Comment</ButtonText>
</Strings>
</Button>
<Button guid="guidDanBarPackageCmdSet" id="cmdidXMLCommentMember" priority="0x0100" type="Button">
<Parent guid="guidDanBarPackageCmdSet" id="MyToolbarGroup" />
<Icon guid="guidDanBarImages" id="bmpPic9" />
<Strings>
<ButtonText>Member XML Comment</ButtonText>
</Strings>
</Button>
<Button guid="guidVSStd97" id="cmdidMoreWindows" priority="0x0100" type="Button">
<Parent guid="guidDanBarPackageCmdSet" id="MyToolbarGroup" />
<Icon guid="guidDanBarImages" id="bmpPic10" />
<Strings>
<ButtonText>Win...</ButtonText>
</Strings>
</Button>
<!--BRIEF buttons-->
<Button guid="guidDanBarPackageCmdSet" id="cmdidBriefAltD" priority="0x0100" type="Button">
<Parent guid="guidDanBarPackageCmdSet" id="BriefToolbarGroup" />
<Icon guid="guidBriefBarImages" id="bmpPic1" />
<Strings>
<ButtonText>Brief Alt D - Line Delete</ButtonText>
</Strings>
</Button>
<Button guid="guidDanBarPackageCmdSet" id="cmdidBriefAltMinus" priority="0x0100" type="Button">
<Parent guid="guidDanBarPackageCmdSet" id="BriefToolbarGroup" />
<Icon guid="guidBriefBarImages" id="bmpPic3" />
<Strings>
<ButtonText>Brief Num-Minus - Line Cut</ButtonText>
</Strings>
</Button>
<Button guid="guidDanBarPackageCmdSet" id="cmdidBriefAltPlus" priority="0x0100" type="Button">
<Parent guid="guidDanBarPackageCmdSet" id="BriefToolbarGroup" />
<Icon guid="guidBriefBarImages" id="bmpPic4" />
<Strings>
<ButtonText>Brief Num-Plus - Line Copy</ButtonText>
</Strings>
</Button>
<Button guid="guidDanBarPackageCmdSet" id="cmdidBriefAltC" priority="0x0100" type="Button">
<Parent guid="guidDanBarPackageCmdSet" id="BriefToolbarGroup" />
<Icon guid="guidBriefBarImages" id="bmpPic2" />
<Strings>
<ButtonText>Brief Alt C - Block Select</ButtonText>
</Strings>
</Button>
<Button guid="guidDanBarPackageCmdSet" id="cmdidBriefLinePaste" priority="0x0100" type="Button">
<Parent guid="guidDanBarPackageCmdSet" id="BriefToolbarGroup" />
<Icon guid="guidBriefBarImages" id="bmpPic5" />
<Strings>
<ButtonText>Brief Insert - Line Paste</ButtonText>
</Strings>
</Button>
</Buttons>
<!--The bitmaps section is used to define the bitmaps that are used for the commands.-->
<Bitmaps>
<!-- The bitmap id is defined in a way that is a little bit different from the others:
the declaration starts with a guid for the bitmap strip, then there is the resource id of the
bitmap strip containing the bitmaps and then there are the numeric ids of the elements used
inside a button definition. An important aspect of this declaration is that the element id
must be the actual index (1-based) of the bitmap inside the bitmap strip. -->
<Bitmap guid="guidDanBarImages" href="Resources\DanBar.png" usedList="bmpPic1, bmpPic2, bmpPic3, bmpPic4, bmpPic5, bmpPic6, bmpPic7, bmpPic8, bmpPic9, bmpPic10" />
<Bitmap guid="guidBriefBarImages" href="Resources\BriefBar.png" usedList="bmpPic1, bmpPic2, bmpPic3, bmpPic4, bmpPic5, bmpPic6" />
</Bitmaps>
</Commands>
<KeyBindings>
<KeyBinding guid="guidDanBarPackageCmdSet" id="cmdidXMLCommentSmall" editor="guidVSStd97" key1="q" mod1="Alt" />
<KeyBinding guid="guidDanBarPackageCmdSet" id="cmdidBriefAltD" editor="guidVSStd97" key1="d" mod1="Alt" />
<KeyBinding guid="guidDanBarPackageCmdSet" id="cmdidBriefAltMinus" editor="guidVSStd97" key1="VK_SUBTRACT" />
<KeyBinding guid="guidDanBarPackageCmdSet" id="cmdidBriefAltPlus" editor="guidVSStd97" key1="VK_ADD" />
<KeyBinding guid="guidDanBarPackageCmdSet" id="cmdidBriefAltC" editor="guidVSStd97" key1="c" mod1="Alt" />
<KeyBinding guid="guidDanBarPackageCmdSet" id="cmdidBriefLinePaste" editor="guidVSStd97" key1="VK_INSERT" />
</KeyBindings>
<Symbols>
<!-- This is the package guid. -->
<GuidSymbol name="guidDanBarPackage" value="{69fa005b-6bae-4a69-84e6-ed7cf75cc180}" />
<!-- This is the guid used to group the menu commands together -->
<GuidSymbol name="guidDanBarPackageCmdSet" value="{a2ce5715-189e-4bfc-bc37-4d1b6e0c1122}">
<IDSymbol name="MyToolbar" value="0x1000" />
<IDSymbol name="MyToolbarGroup" value="0x1050" />
<IDSymbol name="BriefToolbar" value="0x1100" />
<IDSymbol name="BriefToolbarGroup" value="0x1150" />
<IDSymbol name="cmdidConcurrentBuilds" value="256" />
<IDSymbol name="cmdidTrackInSolutionExplorer" value="257" />
<IDSymbol name="cmdidBuildStartupProject" value="258" />
<IDSymbol name="cmdidCommentOutParam" value="259" />
<IDSymbol name="cmdidXMLCommentFull" value="260" />
<IDSymbol name="cmdidXMLCommentSmall" value="261" />
<IDSymbol name="cmdidXMLCommentTiny" value="262" />
<IDSymbol name="cmdidXMLCommentMember" value="263" />
<IDSymbol name="cmdidInsertRegion" value="264" />
<IDSymbol name="cmdidBriefAltD" value="270" />
<IDSymbol name="cmdidBriefAltMinus" value="271" />
<IDSymbol name="cmdidBriefAltPlus" value="272" />
<IDSymbol name="cmdidBriefAltC" value="273" />
<IDSymbol name="cmdidBriefLinePaste" value="274" />
</GuidSymbol>
<GuidSymbol name="guidDanBarImages" value="{ffb25733-9517-4411-bae2-4deda791fd6c}">
<IDSymbol name="bmpPic1" value="1" />
<IDSymbol name="bmpPic2" value="2" />
<IDSymbol name="bmpPic3" value="3" />
<IDSymbol name="bmpPic4" value="4" />
<IDSymbol name="bmpPic5" value="5" />
<IDSymbol name="bmpPic6" value="6" />
<IDSymbol name="bmpPic7" value="7" />
<IDSymbol name="bmpPic8" value="8" />
<IDSymbol name="bmpPic9" value="9" />
<IDSymbol name="bmpPic10" value="10" />
</GuidSymbol>
<GuidSymbol name="guidBriefBarImages" value="{f1a36fcd-2c27-4151-ae23-42fff88c212c}">
<IDSymbol name="bmpPic1" value="1" />
<IDSymbol name="bmpPic2" value="2" />
<IDSymbol name="bmpPic3" value="3" />
<IDSymbol name="bmpPic4" value="4" />
<IDSymbol name="bmpPic5" value="5" />
<IDSymbol name="bmpPic6" value="6" />
</GuidSymbol>
</Symbols>
</CommandTable>
Usually, a command belongs to a menu and is included in Options-Keyboard from this menu. As your commands belong only to a toolbar, this is not the case.
You can add the LocCanonicalName tag to your .vsct button definitions to include your commands to Options-Keyboard like this:
<Strings>
<LocCanonicalName>DanBar.TrackInSolutionExplorer</LocCanonicalName>
<ButtonText>Track In Solution Explorer</ButtonText>
</Strings>
You should define your commands in Visual Studio Command Table (.vsct) file and create event handlers for them in code. See Commands, Menus, and Toolbars.
VS 2015 includes the Custom Command template that you can add to your project to quickly get started:

Ext Net TimeField in an editable grid

I have a grid panel which display two TimeSpans in two columns and all is well when I load the page but when I go server side the validation on my editors always fail. I don't understand why the store can display the TimeSpans but cannot return it after...
Here my code :
<ext:GridPanel ID="WeekParams" runat="server" >
<Store>
<ext:Store runat="server">
<Reader>
<ext:JsonReader IDProperty="GUID">
<Fields>
<ext:RecordField Name="Day" Type="String" />
<ext:RecordField Name="UATNumber" Type="int" />
<ext:RecordField Name="From" Type="Date" />
<ext:RecordField Name="To" Type="Date" />
</Fields>
</ext:JsonReader>
</Reader>
</ext:Store>
</Store>
<ColumnModel>
<Columns>
<ext:Column ColumnID="Day" DataIndex="Day" />
<ext:NumberColumn ColumnID="UATNumber" DataIndex="UATNumber" Format="0" />
<ext:DateColumn ColumnID="From" DataIndex="From" Format="dd/MM/yyyy" >
<Renderer Format="Date" FormatArgs="'HH:mm'" />
<Editor>
<ext:TimeField runat="server" />
</Editor>
</ext:DateColumn>
<ext:DateColumn ColumnID="To" DataIndex="To" Format="dd/MM/yyyy" >
<Renderer Format="Date" FormatArgs="'HH:mm'" />
<Editor>
<ext:TimeField runat="server" />
</Editor>
</ext:DateColumn>
</Columns>
</ColumnModel>
<Plugins>
<ext:EditableGrid runat="server" />
</Plugins>
</ext:GridPanel>
And here the result when I'm going to the server side :

GridPane: RowConstraints percentHeight not working as expected

Having a GridPane with 2 rows and 2 columns, setting the row constraints to 50 percent height results in unwanted behaviour.
Code:
<BorderPane xmlns:fx="http://javafx.com/fxml" fx:controller="..." stylesheets="#general.css" prefWidth="800" prefHeight="600">
<top>
<VBox>
<!-- ... -->
</VBox>
</top>
<bottom>
<HBox>
<!-- ... -->
</HBox>
</bottom>
<center>
<GridPane >
<children>
<ScrollPane fx:id="tilePane" GridPane.columnIndex="0" GridPane.rowIndex="0">
<content>
</content>
<GridPane.margin>
<Insets bottom="2" left="2" right="2" top="2" />
</GridPane.margin>
</ScrollPane>
<TreeView fx:id="listPane" GridPane.columnIndex="0" GridPane.rowIndex="1">
<root>
<TreeItem value="Stages" />
</root>
<GridPane.margin>
<Insets bottom="2" left="2" right="2" top="2" />
</GridPane.margin>
</TreeView>
<ScrollPane fx:id="mapPane" GridPane.columnIndex="1" GridPane.rowIndex="0" GridPane.rowSpan="2">
<content>
</content>
<GridPane.margin>
<Insets bottom="2" left="2" right="2" top="2" />
</GridPane.margin>
</ScrollPane>
</children>
<columnConstraints>
<ColumnConstraints hgrow="ALWAYS" percentWidth="25"/>
<ColumnConstraints hgrow="ALWAYS" />
</columnConstraints>
<rowConstraints>
<RowConstraints vgrow="ALWAYS" percentHeight="50" />
<RowConstraints vgrow="ALWAYS" percentHeight="50" />
</rowConstraints>
</GridPane>
</center>
</BorderPane>
(mentioned attribute at the bottom)
I expected that the two rows would share their available height at a 50% rate. They do this, but they also consume a lot more space than needed.
Picture of the result with, and without percentHeight specified:
Do I understand percentHeight wrong, or is there another approach?

Ribbon Contextual Groups and Tabs in SharePoint

I am new to SharePoint ribbon. Why do I not see the View and Edit buttons in the Manage group of my tab?
Here are my definitions for your reference:
<ContextualGroup Id="Ribbon.MyWorkContextualTabGroup"
Color="Blue" Title="{title}"
Command="MyWorkContextualTab.EnableContextualGroup"
Sequence="502"
ContextualGroupId="MyWorkContextualTabGroup">
<Tab Id="Ribbon.MyWorkTab"
Title="My Work"
Description="My Work tab description"
Command="MyWorkContextualTab.EnableMyWorkTab"
Sequence="501">
<Scaling Id="Ribbon.MyWorkTab.Scaling">
<MaxSize Id="Ribbon.MyWorkTab.MaxSize_New"
GroupId="Ribbon.MyWorkTab.MyWorkGroup_New"
Size="MyWorkLayout"
Sequence="10"/>
<MaxSize Id="Ribbon.MyWorkTab.MaxSize_Manage"
GroupId="Ribbon.MyWorkTab.MyWorkGroup_Manage"
Size="MyWorkLayout"
Sequence="20" />
<Scale Id="Ribbon.MyWorkTab.Scalling.MyWorkTabScalling_New"
GroupId="Ribbon.MyWorkTab.MyWorkGroup_New"
Size="MyWorkLayout"
Sequence="30" />
<Scale Id="Ribbon.MyWorkTab.Scalling.MyWorkTabScalling_Manage"
GroupId="Ribbon.MyWorkTab.MyWorkGroup_Manage"
Size="MyWorkLayout"
Sequence="40"/>
</Scaling>
<Groups Id="Ribbon.MyWorkTab.Groups">
<Group Id="Ribbon.MyWorkTab.MyWorkGroup_New"
Description="New group description"
Title="New"
Command="MyWorkContextualTab.EnableMyWorkGroup_New"
Sequence="52"
Template="Ribbon.Templates.MyWorkTemplate">
<Controls Id="Ribbon.MyWorkTab.MyWorkGroup_New.Controls">
<Button Id="Ribbon.MyWorkTab.MyWorkGroup_New.NewItem"
Command="MyWorkContextualTab.NewItemCommand"
Sequence="15"
Description="Add a new item"
LabelText="New Item"
TemplateAlias="ONE_R1"
Image32by32="_layouts/images/mywork/ribbon/newitem.png" />
</Controls>
</Group>
<Group Id="Ribbon.MyWorkTab.MyWorkGroup_Manage"
Description="Manage group description"
Title="Manage"
Command="MyWorkContextualTab.EnableMyWorkGroup_Manage"
Sequence="53"
Template="Ribbon.Templates.MyWorkTemplate">
<Controls Id="Ribbon.MyWorkTab.MyWorkGroup_Manage.Controls">
<Button Id="Ribbon.MyWorkTab.MyWorkGroup_Manage.ViewItem"
Command="MyWorkContextualTab.ViewItemCommand"
Sequence="25"
Description="View this item"
LabelText="View Item"
TemplateAlias="ONE_R1"
Image32by32="_layouts/images/mywork/ribbon/viewitem.png" />
<Button Id="Ribbon.MyWorkTab.MyWorkGroup_Manage.EditItem"
Command="MyWorkContextualTab.EditItemCommand"
Sequence="35"
Description="Edit this item"
LabelText="Edit Item"
TemplateAlias="ONE_R1"
Image32by32="_layouts/images/mywork/ribbon/edititem.png" />
</Controls>
</Group>
</Groups>
</Tab>
</ContextualGroup>
<GroupTemplate Id="Ribbon.Templates.MyWorkTemplate">
<Layout Title="MyWorkLayout" LayoutTitle="MyWorkLayout">
<Section Alignment="Top" Type="OneRow">
<Row>
<ControlRef DisplayMode="Large" TemplateAlias="ONE_R1"/>
</Row>
</Section>
<Section Alignment="Top" Type="ThreeRow">
<Row>
<ControlRef DisplayMode="Medium" TemplateAlias="THE_R1"/>
</Row>
<Row>
<ControlRef DisplayMode="Medium" TemplateAlias="THE_R2"/>
</Row>
<Row>
<ControlRef DisplayMode="Medium" TemplateAlias="THE_R3"/>
</Row>
</Section>
</Layout>
</GroupTemplate>
I havent worked with Sharepoint's Ribbon much, but from what I understand it is almost identical to CRM 2011 ribbon structure. When the issue of missing buttons crop up in CRM it is usually a sequence issue with Scaling and MaxSize.
All of the MaxSize element need to come before the Scale elements in terms of sequence. I would try adding the sequence numbers to the MaxSize/Scale elements in your Scaling section and adjust the numbers to make sure maxsize appears before scale.
Hope this helps.
example:
<Scaling Id="Ribbon.MyWorkTab.Scaling">
<MaxSize Id="Ribbon.MyWorkTab.MaxSize_New"
GroupId="Ribbon.MyWorkTab.MyWorkGroup_New"
Size="MyWorkLayout"
Sequence="10"/>
<MaxSize Id="Ribbon.MyWorkTab.MaxSize_Manage"
GroupId="Ribbon.MyWorkTab.MyWorkGroup_Manage"
Size="MyWorkLayout"
Sequence="20" />
<Scale Id="Ribbon.MyWorkTab.Scalling.MyWorkTabScalling_New"
GroupId="Ribbon.MyWorkTab.MyWorkGroup_New"
Size="MyWorkLayout"
Sequence="30" />
<Scale Id="Ribbon.MyWorkTab.Scalling.MyWorkTabScalling_Manage"
GroupId="Ribbon.MyWorkTab.MyWorkGroup_Manage"
Size="MyWorkLayout"
Sequence="40"/>
</Scaling>
Okay this is what I had to do:
Do not use _ (underscore) in the Id.
Change my layout to use OverflowSection
Here are my final definitions in case if you need:
<ContextualGroup Id="Ribbon.MyWorkContextualTabGroup"
Color="Blue" Title="{title}"
Command="MyWorkContextualTab.EnableContextualGroup"
Sequence="502"
ContextualGroupId="MyWorkContextualTabGroup">
<Tab Id="Ribbon.MyWorkTab"
Title="My Work"
Description="My Work tab description"
Command="MyWorkContextualTab.EnableMyWorkTab"
Sequence="501">
<Scaling Id="Ribbon.MyWorkTab.Scaling">
<MaxSize Id="Ribbon.MyWorkTab.MaxSizeNew"
GroupId="Ribbon.MyWorkTab.MyWorkGroupNew"
Size="MyWorkLayout"
Sequence="10"/>
<MaxSize Id="Ribbon.MyWorkTab.MaxSizeManage"
GroupId="Ribbon.MyWorkTab.MyWorkGroupManage"
Size="MyWorkLayout"
Sequence="20" />
<Scale Id="Ribbon.MyWorkTab.Scaling.MyWorkTabScalingNew"
GroupId="Ribbon.MyWorkTab.MyWorkGroupNew"
Size="MyWorkLayout"
Sequence="30" />
<Scale Id="Ribbon.MyWorkTab.Scaling.MyWorkTabScalingManage"
GroupId="Ribbon.MyWorkTab.MyWorkGroupManage"
Size="MyWorkLayout"
Sequence="40"/>
</Scaling>
<Groups Id="Ribbon.MyWorkTab.Groups">
<Group Id="Ribbon.MyWorkTab.MyWorkGroupNew"
Description="New group description"
Title="New"
Command="MyWorkContextualTab.EnableMyWorkGroupNew"
Sequence="52"
Template="Ribbon.Templates.MyWorkTemplate">
<Controls Id="Ribbon.MyWorkTab.MyWorkGroupNew.Controls">
<Button Id="Ribbon.MyWorkTab.MyWorkGroupNew.NewItem"
Command="MyWorkContextualTab.NewItemCommand"
Sequence="15"
Description="Add a new item"
LabelText="New Item"
TemplateAlias="ONERW"
Image32by32="_layouts/images/mywork/ribbon/newitem-32.png" />
</Controls>
</Group>
<Group Id="Ribbon.MyWorkTab.MyWorkGroupManage"
Description="Manage group description"
Title="Manage"
Command="MyWorkContextualTab.EnableMyWorkGroupManage"
Sequence="53"
Template="Ribbon.Templates.MyWorkTemplate">
<Controls Id="Ribbon.MyWorkTab.MyWorkGroupManage.Controls">
<Button Id="Ribbon.MyWorkTab.MyWorkGroupManage.ViewItem"
Command="MyWorkContextualTab.ViewItemCommand"
Sequence="25"
Description="View this item"
LabelText="View Item"
TemplateAlias="ONERW"
Image32by32="_layouts/images/mywork/ribbon/viewitem-32.png" />
<Button Id="Ribbon.MyWorkTab.MyWorkGroupManage.EditItem"
Command="MyWorkContextualTab.EditItemCommand"
Sequence="35"
Description="Edit this item"
LabelText="Edit Item"
TemplateAlias="ONERW"
Image32by32="_layouts/images/mywork/ribbon/edititem-32.png" />
</Controls>
</Group>
</Groups>
</Tab>
</ContextualGroup>
<GroupTemplate Id="Ribbon.Templates.MyWorkTemplate">
<Layout Title="MyWorkLayout" LayoutTitle="MyWorkLayout">
<OverflowSection Type="OneRow" DisplayMode="Large" TemplateAlias="ONERW"/>
</Layout>
</GroupTemplate>

Resources