Class XmlModelHelper

This method duplicates the original one and added the customize argument. It is called from the LeftMenuItems.ascx.cs to return the navigation customized based on whether the navigation items have been added by publishing objects to the left menu.

The original call from MetaToolbar could not load generic configurations. The presence of a non-empty class name meant it tried to get a configuration hard-wired to that class; and all classes have names, regardless of their configuration. Upon failing, it quit and returned nothing.

The original two-argument call without a class name passed in a viewId as a selector, even when the viewId was null. This prevented the placeName from matching (e.g., { "", "Reference1N" } failed to match Reference1N.xml.

This implementation will attempt to load both class-specific configs and configs based only on viewId and/or placeName, and scan either one for a toolbar with items.

This implementation may still be fundamentally wrong. If configs exist for both the class-specific selector and the generic selector, they should probably be combined according to the xml operations. However, the FileProvider implementation cannot match the separate selectors to the same file group, so there isn't a good way aroudn this; and from a practical standpoint, current configs may depend on the files not being combined.

The GetXmlBy*() methods below aren't being called from client code with the arguments they advertise... they are just used to get xml with N strings in the selector. They dont even always get that right. GetXmlBySelector does exactly what it says it does, and pushes the ugly hacks up a little closer to the places that need them.

This method duplicates the orginail one and added the customize argument. It is called to return the navigation XML customized based on whether the navigation items have been added by publishing objects to the left menu.