SharePoint Foundation 2010: Demos: Using the Built-in Silverlight Media Player of SharePoint 2010:
'via Blog this'
<script type="text/javascript" src="/_layouts/mediaplayer.js"></script>
<DIV ID="VIDEOS">
<a href="https://home360.balfourbeatty.com/pb/corp/WorkingAtPB/BD/Prometheus/Videos/video.mp4"><img src="https://home360.balfourbeatty.com/news/newscentre/pb/corp/PublishingImages/GeorgePierson204x204.png"></a>
</DIV>
<script type="text/javascript">
_spBodyOnLoadFunctionNames.push('mediaPlayer.createOverlayPlayer');
mediaPlayer.attachToMediaLinks
(
(document.getElementById('VIDEOS')),
['wmv', 'avi', 'mp3','mp4']
);
</script>
Wednesday, November 21, 2012
Monday, August 13, 2012
Thursday, August 2, 2012
Wednesday, July 18, 2012
MVPs for SharePoint 2010: Rolling up News Articles in SharePoint Server 2010 with the Content Query Web Part - The Microsoft MVP Award Program Blog - Site Home - MSDN Blogs
Thursday, July 12, 2012
Tuesday, July 3, 2012
Tuesday, March 6, 2012
Building HTML5 Applications - Adding HTML5 Drag and Drop to SharePoint Lists
Building HTML5 Applications - Adding HTML5 Drag and Drop to SharePoint Lists: "id development of SharePoint applications. SharePoint 2010 is greatly improved as compared with SharePoint 2007, and now it’s exceedingly useful, even for developers. The idea is that you can use the SharePoint Designer GUI to generate some really complex XSLT code and then just copy and paste the generated code into your Visual Studio project instead of writing the typo-prone and not always well-documented XML/XSLT by hand. I often use this trick in real-world projects and, I promise you, it saves plenty of time.
I open SharePoint Designer and navigate to the dashboard page I created earlier. I select a cell in the Assigned To column (right-click and choose Select | Cell). Now"
'via Blog this'
I open SharePoint Designer and navigate to the dashboard page I created earlier. I select a cell in the Assigned To column (right-click and choose Select | Cell). Now"
'via Blog this'
Wednesday, February 22, 2012
SharePoint lytebox with link to dispform.aspx
Building on the work of the codeplex project:
http://lyteboxsp.codeplex.com/
Note to change the Title/link of the webpart, modify the parameters binding either on the web or in designer. The binding must match the name of the library, not the url.
I updated the code slightly in the dataview to include a link to the dispform.aspx for the picture. It seems the key is to write the link with escaped characters. I also update the javascript to ver 5.5.
Also, you can update preferences for lytebox in the section "data-lyte-options"
http://lyteboxsp.codeplex.com/
Note to change the Title/link of the webpart, modify the parameters binding either on the web or in designer. The binding must match the name of the library, not the url.
I updated the code slightly in the dataview to include a link to the dispform.aspx for the picture. It seems the key is to write the link with escaped characters. I also update the javascript to ver 5.5.
Also, you can update preferences for lytebox in the section "data-lyte-options"
---Copy and Replace below in the Dataview----<a> <xsl:attribute name="href"> <xsl:choose> <xsl:when test="starts-with(@FileRef, '/')"> <xsl:value-of select="@FileRef"> </xsl:value-of></xsl:when> <xsl:otherwise> <xsl:value-of select="concat("/",@FileRef)"> </xsl:value-of></xsl:otherwise> </xsl:choose> </xsl:attribute><xsl:attribute name="class">lytebox</xsl:attribute> <xsl:attribute name="data-lyte-options">autoResize:true slide:true group:name slideInterval:6000 showNavigation:true</xsl:attribute> <xsl:attribute name="data-title">Title:<xsl:value-of select="@Title"></xsl:value-of></xsl:attribute><xsl:attribute name="data-description"> Description: <xsl:value-of select="@Description"> ; Link: <a href="/<xsl:value-of select="@FileDirRef">/Forms/DispForm.aspx?ID=<xsl:value-of select="@ID">" target="_parent"> See more details </a> </xsl:value-of></xsl:value-of></xsl:value-of></xsl:attribute> <img style="border: 3px solid white; margin: 5px;" src="" /> <xsl:attribute name="src"> <xsl:value-of select="concat("/",@FileDirRef,"/_t/",translate(@FileLeafRef, ".", "_"),".",@FileType)"> </xsl:value-of></xsl:attribute></a>
Friday, February 10, 2012
Show Quick Launch on SharePoint 2010 Webpart Page
A dies in vita: Show Quick Launch on SharePoint 2010 Webpart Page: "body #s4-leftpanel"
'via Blog this'
With SharePoint 2007 all you needed to do was edit the page in SharePoint Designer and remove the following 2 lines:
< asp:Content ContentPlaceHolderId="PlaceHolderNavSpacer" runat="server">
< asp:Content ContentPlaceHolderId="PlaceHolderLeftNavBar" runat="server">
With SharePoint 2010 you also need to delete the following:
< style type="text/css">
body #s4-leftpanel {
display:none;
}
.s4-ca {
margin-left:0px;
}
'via Blog this'
With SharePoint 2007 all you needed to do was edit the page in SharePoint Designer and remove the following 2 lines:
< asp:Content ContentPlaceHolderId="PlaceHolderNavSpacer" runat="server">
< asp:Content ContentPlaceHolderId="PlaceHolderLeftNavBar" runat="server">
With SharePoint 2010 you also need to delete the following:
< style type="text/css">
body #s4-leftpanel {
display:none;
}
.s4-ca {
margin-left:0px;
}
Wednesday, February 8, 2012
Monday, February 6, 2012
Thursday, January 26, 2012
Display All Tasks in Site Collection
From: http://blog.mastykarz.nl/inconvenient-user-tasks-web-part-display-all-tasks/
The out of the box available User Tasks Web Part allows you to show tasks assigned to the current user. This Web Part is a great building block for end users since it doesn’t require any configuration whatsoever. All you have to do is to add it to a page and it will automatically display all tasks assigned to the current user. Unfortunately by default the User Tasks Web Part displays only tasks assigned to the current user located in tasks lists in the current Site.
The scenario
Imagine you’ve been given the assignment of creating an overview of tasks assigned to users. To make it user friendly all you want to display are the tasks for the user currently visiting the site. Although there are multiple projects where the tasks can be created you were asked to provide a single overview for the users.
Choices, choices, every time choices
Reading the first part of the requirement you might start considering using the out of the box available User Tasks Web Part, which displays a list of all tasks assigned to the current user. Each task has a link attached to it so that it’s easy for users to quickly see more information about a specific task. However, because of the last part of the requirement, you cannot really use the User Tasks Web Part: after all it displays tasks from the current site only. So what are the options?
Embrace the development
If you are a developer or a power-user you know that aggregating all tasks assigned to the current user isn’t that complicated. Depending on your experience and knowledge of the platform you might come up with a custom solution: either some using the SharePoint API or a Data View Web Part-like solution configured through SharePoint Designer.
While there is nothing wrong with any of those approaches there is an easier way to get things done, especially if all you need to do is to display tasks from all sites using the default User Experience.
Content Query Web Part almighty
Content Query Web Part (CQWP) is probably the best content aggregation solution available on the SharePoint platform. Thanks to its built-in caching mechanisms it’s very well performing and since the presentation of the aggregated data relies on XSLT you it is very flexible and can be used in virtually any situation.
The great thing about using the CQWP for this purpose is the ability of configuring it through the UI. Using the standard properties you can configure just the right query to retrieve tasks assigned to the current user. If you however would like to present the retrieved tasks similarly to the standard User Tasks Web Part, it would take quite some effort to achieve the same result.
There is yet another way to get things done without too much work.
Customization through configuration
While it might seem impossible at first, the User Tasks Web Part ships with a hidden gem that allows you to display all tasks assigned to the current user.
Let’s start with adding the User Tasks Web Part. By default it will display all tasks assigned to the current user, stored in tasks lists in the current Site.
Although there are is one more task assigned to the current user, stored in the Team 1 site, it is not being picked up by the User Tasks Web Part we have just added.
As mentioned before, the property that allows you to change the default behavior of the User Tasks Web Part is hidden and cannot be modified through the UI. So in order to make the User Tasks Web Part display all tasks, you need to export the Web Part and change the value in the .dwp file.
After you open the .dwp file in your favorite text editor, you have to add the following snippet just before the tag:
?
1
true
Important: It is important to include the xmlns attribute. If you omit it, the setting won’t work and the User Tasks Web Part will display tasks from the current site only as it does by default.
Once you do that, save the file, move back to SharePoint, upload the .dwp file and add the imported User Tasks Web Part. You should see all tasks assigned to the current user being displayed in the overview:
And that’s it: from now on, no matter where in the Site Collection a task will be created and assigned to a user, it will be displayed on the overview that you have just created.
One more important thing to notice is, that although I’ve used SharePoint 2010 as sample for this article, exactly the same approach can be used with SharePoint 2007.
Summary
Out of the box SharePoint ships with the User Tasks Web Part which allows you to display tasks assigned to the current user. By default this Web Part shows only tasks stored in the current Site. If all you need to do is to modify the overview and include all tasks from all sites in the Site Collection, the best approach is to change the value of a hidden property of the User Tasks Web Part.
The out of the box available User Tasks Web Part allows you to show tasks assigned to the current user. This Web Part is a great building block for end users since it doesn’t require any configuration whatsoever. All you have to do is to add it to a page and it will automatically display all tasks assigned to the current user. Unfortunately by default the User Tasks Web Part displays only tasks assigned to the current user located in tasks lists in the current Site.
The scenario
Imagine you’ve been given the assignment of creating an overview of tasks assigned to users. To make it user friendly all you want to display are the tasks for the user currently visiting the site. Although there are multiple projects where the tasks can be created you were asked to provide a single overview for the users.
Choices, choices, every time choices
Reading the first part of the requirement you might start considering using the out of the box available User Tasks Web Part, which displays a list of all tasks assigned to the current user. Each task has a link attached to it so that it’s easy for users to quickly see more information about a specific task. However, because of the last part of the requirement, you cannot really use the User Tasks Web Part: after all it displays tasks from the current site only. So what are the options?
Embrace the development
If you are a developer or a power-user you know that aggregating all tasks assigned to the current user isn’t that complicated. Depending on your experience and knowledge of the platform you might come up with a custom solution: either some using the SharePoint API or a Data View Web Part-like solution configured through SharePoint Designer.
While there is nothing wrong with any of those approaches there is an easier way to get things done, especially if all you need to do is to display tasks from all sites using the default User Experience.
Content Query Web Part almighty
Content Query Web Part (CQWP) is probably the best content aggregation solution available on the SharePoint platform. Thanks to its built-in caching mechanisms it’s very well performing and since the presentation of the aggregated data relies on XSLT you it is very flexible and can be used in virtually any situation.
The great thing about using the CQWP for this purpose is the ability of configuring it through the UI. Using the standard properties you can configure just the right query to retrieve tasks assigned to the current user. If you however would like to present the retrieved tasks similarly to the standard User Tasks Web Part, it would take quite some effort to achieve the same result.
There is yet another way to get things done without too much work.
Customization through configuration
While it might seem impossible at first, the User Tasks Web Part ships with a hidden gem that allows you to display all tasks assigned to the current user.
Let’s start with adding the User Tasks Web Part. By default it will display all tasks assigned to the current user, stored in tasks lists in the current Site.
Although there are is one more task assigned to the current user, stored in the Team 1 site, it is not being picked up by the User Tasks Web Part we have just added.
As mentioned before, the property that allows you to change the default behavior of the User Tasks Web Part is hidden and cannot be modified through the UI. So in order to make the User Tasks Web Part display all tasks, you need to export the Web Part and change the value in the .dwp file.
After you open the .dwp file in your favorite text editor, you have to add the following snippet just before the tag:
?
1
Important: It is important to include the xmlns attribute. If you omit it, the setting won’t work and the User Tasks Web Part will display tasks from the current site only as it does by default.
Once you do that, save the file, move back to SharePoint, upload the .dwp file and add the imported User Tasks Web Part. You should see all tasks assigned to the current user being displayed in the overview:
And that’s it: from now on, no matter where in the Site Collection a task will be created and assigned to a user, it will be displayed on the overview that you have just created.
One more important thing to notice is, that although I’ve used SharePoint 2010 as sample for this article, exactly the same approach can be used with SharePoint 2007.
Summary
Out of the box SharePoint ships with the User Tasks Web Part which allows you to display tasks assigned to the current user. By default this Web Part shows only tasks stored in the current Site. If all you need to do is to modify the overview and include all tasks from all sites in the Site Collection, the best approach is to change the value of a hidden property of the User Tasks Web Part.
Monday, January 23, 2012
SharePoint 2010 Granular Backup-Restore Part 1 - SharePoint Brew - Site Home - MSDN Blogs
SharePoint 2010 Granular Backup-Restore Part 1 - SharePoint Brew - Site Home - MSDN Blogs: "ll granular backup and restore operations were only available using stsadm. SharePoint 2010 has integrated granular backup restore operations into both Central Administrat"
'via Blog this'
'via Blog this'
Friday, January 13, 2012
Monday, January 9, 2012
Subscribe to:
Posts (Atom)