ENCOUNTERING THE MONSTERS IN THE CAVE in Font

Creating Data Matrix 2d barcode in Font ENCOUNTERING THE MONSTERS IN THE CAVE

The attributes to the view element are not very intimidating either. Your BaseViewId is the Id of the field, used to address this particular view, such as when you want to add your view to a page in a site definition. The DisplayName is, as always, the name shown to users of the view. Type can be set to HTML, Pivot, or Chart to specify, well, what type of view this is.

When adding a view of a list to a web part page directly from the web interface, SharePoint looks for Tip a view with a BaseViewId of 0. As such, if you want your users to be able to add a view of your list to a web part page, make sure you have a view with a BaseViewId of 0.

The next three attributes define how the view will be built into a page. SetupPath works like it does in modules and other places in SharePoint and defines a path, relative to [12], to a file from which the page holding the view will be created. The page itself may be a web part page, but you can also use regular pages. WebPartZoneID specifies in which web part zone on the page the view will be placed. This assumes that you have SetupPath pointing to a web part page. Url is simply the list-relative URL where the final page will be placed. Note the fact that the URL is relative to the list. So, in our example, we will create a view, called Custom View, that will be placed inside the Main web part zone of a page. That page will be created based on the [12]\pages\viewpage.aspx page and stored at lists/[MyCustomList]/CustomView.aspx. Of course, our view does not actually contain anything, so it s a rather pointless view at this time. We need to add some content. First, let s add a toolbar to make sure we can add new items and get access to the actions and settings menus: <View BaseViewID="2" DisplayName="Custom View" Type="HTML" SetupPath="pages\viewpage.aspx" WebPartZoneID="Main" Url="CustomView.aspx"> <Toolbar Type="Standard"/> </View> By adding the Toolbar child element, at least now we have an easy way of doing basic list operations. Figure 7-4 shows the result of the previous code.

The cavern was quiet. Too quiet. The last stretch had been too easy. Not even the smaller monsters were roaming around; even the sound of dripping water had stopped. Now there was only silence. Wait! What s that noise Something is coming this way in a hurry by the sound of it. Time to quaff that potion of high alert.

When you are developing views, you should know that modifying the views is indeed possible without Tip re-creating the list for each change. Update and deploy your new list template, and do an IISReset before reloading your view. This way you do not have to delete sample data and create a new list for each change you make.

It is time to wake up. If you are reading this in a tired state, you might want to take a break. You are about to face your first serious challenge. Get a cup of coffee going. If you don t drink coffee, now would be a great time to start. View toolbars come in two distinct flavors. The first flavor, the standard toolbar, should be well known; you can see it in all standard views, and it contains the New button and Site Actions and Site Settings menus. The second flavor is called a freeform toolbar, and it holds some extremely powerful modification options. However, to tap into all that power, you need to have a deep understanding of CAML. Figure 7-5 shows a very familiar use of the freeform toolbar.