How to get a good visual presentation of the SharePoint 2010 Visio Web Access web part.June 3, 2010 17:27
However, the default display behavior of the Visio Web Access part is a bit nasty, especially when you try to display information inline of the page. The content position of the Visio document is positioned completely wrong and the user has to correct the zoom or even has to drag the information. As you can see in the example below, my Visio information is shown incorrectly. This problem can be fixed by modifying the XML configuration of the web part. Before you can modify the XML configuration, make sure you enable the checkbox of the web part option “Override the Web Drawing’s default initial view using the web part’s current page, pan and zoom”. Never turn off this option again, because it will completely reset the view settings in the xml. After you have saved the web part with the override setting, export it to your desktop and open it in an editor. Notepad will do fine. Search inside the XML for a property called “ViewSettings”.
<property name=”HelpUrl” type=”string” />
<property name=”ExportMode” type=”exportmode”>All</property> <property name=”ViewSettings” type=”string”>{”pageIndex”:0,”viewBounds”:{”x”:120,”y”:0,”width”:489, “height”:175},”zoomValue”:90}</property>
<property name=”OverrideViewSettings” type=”bool”>True</property> This property allows you to alter the default display option of the web part, but only when the property “OverrideViewSettings” is set to true. Try to play around with the X and Y setting and perhaps the zoomValue. Save the web part file and import it again to your page. You might have to repeat the process a few times to get it right, but after a few tries the web part will show your information correctly. This way Visio is a great option to show KPI information. Tags: 2010, KPI, Office, Positioning, rendering, settings, Visio, web part, xml.SharePoint 2010 Mobile Web Part developmentJanuary 17, 2010 22:15
The mobile rendering engine of SharePoint provides mobile users access to the sites with a completely stripped interface. Its main function is to list all libraries and to provide basic access to them. For wiki and blog sites the rendering engine also provides some content rendering. To keep the amount of data as low as possible, almost all web parts are completely stripped from the mobile site. Only when a web part developer provided a special mobile version of the web part, the web part will be accessible in the interface and to keep the mobile screen as empty as possible, the user must first expand the web part via its title to see it. Documentation about SharePoint Mobile development is provided at MSDN. At first it all looks quite complex, but building a mobile version of a web part is actually not that hard. Below I will explain the required steps with a ‘Hello world’ example. For this sample I will not rename the default object names provided by the Visual Studio templates. Tags: 2010, demo, Mobile, SharePoint, web part. |
||