Monday, October 1, 2012

Sharepoint Web parts Sample Projects



Sharepoint Web parts sample projects list


  1. Pull from 3 lists, post the data the the web part, calculate the amounts (item total, grand total) save to Invoice list (increment invoice # value), send to Word or html 5 for print view.
  2. A basic SharePoint Web Part is required to facilitate a user search via a SOAP API and return the results to the user. SOAP API This is an existing well -established (documented) Web Service - no development of at the Web Service level will be required. The successful bidder will be provided with the necessary code used to interface directly with the Web Service. Interface The interface will consist of the following elements: Search (textbox) to allow the user to specify a search term Department (dropdown) to allow the user to provide a single search filter Company (dropdown) to allow the user to provide a single search filter Location (dropdown) to allow the user to provide a single search filter A search button Results The following results fields will be returned (by the Web Service) and displayed to the user: First name Surname Job title Email address Telephone number Mobile number Department Company Location The Web Part should handle adequate paging to make the interface more useable. Please note that the Web Service will not page the results - this must be handled within the Web Part. Additional The Web Part should be compatible with both 2007 and 2010. Design We are looking a good level of design work to integrated into this Web Part, we wanted to be presented with the a well polished well presented Web Part. Installation We would require that the Web Part is delivered with an MSI (or similar) to facilitate installation on a live SharePoint Site.
  3. It would have four web part configurations on web part when user adds the web part: show/hide images, show number of items in new list and two url links to news. This web part will be linked to two modules: home and news. Then it should display the images, new summary, title, date and links to itself on web page = i think we need to have user control for the form for the user to enter the details before they can appear on webpage.
  4. A basic SharePoint Web Part is required to facilitate a user search via a SOAP API and return the results to the user. SOAP API This is an existing well -established (documented) Web Service - no development of at the Web Service level will be required. The successful bidder will be provided with the necessary code used to interface directly with the Web Service. Interface The interface will consist of the following elements: Search (textbox) to allow the user to specify a search term Department (dropdown) to allow the user to provide a single search filter Company (dropdown) to allow the user to provide a single search filter Location (dropdown) to allow the user to provide a single search filter A search button Results The following results fields will be returned (by the Web Service) and displayed to the user: First name Surname Job title Email address Telephone number Mobile number Department Company Location The Web Part should handle adequate paging to make the interface more useable. Please note that the Web Service will not page the results - this must be handled within the Web Part. Additional The Web Part should be compatible with both 2007 and 2010. Design We are looking a good level of design work to integrated into this Web Part, we wanted to be presented with the a well polished well presented Web Part. Installation We would require that the Web Part is delivered with an MSI (or similar) to facilitate installation on a live SharePoint Site.
  5. Create a SharePoint web part for showing 3rd party media content using existing APIs. The web part must be able to work in two modes. In mode #1, it shows a single predefined Flash object loaded from a 3rd party website. In mode #2, it shows a list of titles for such Flash objects. When the end-user selects one of them on the list, the web part then shows the corresponding Flash object. The web part's end-user GUI consists of only the list object and the window for showing the Flash object. The web part must load the list dynamically by an AJAX call. In Edit mode, the owner of the web part can select which of the 2 modes it is used in, the width and height, and the content to be shown to the end-user. In order to achieve this, the web part must make some REST API calls to retrieve the information. A short but precise English documentation of the web part source code is required, sufficient to explain how the web part can be further developed, and how it can be deployed into a SharePoint instance. What I already have versus what the contractor will deliver: The Flash object already exists and can be loaded by simple 3rd party JavaScript API commands. The lists of objects can be retrieved by using an existing HTTP REST interface, and parsed from an XML format. The web part needs to make the correct REST API calls to access the list, and use the correct JavaScript API calls to show the Flash component. Other context/requirements that contractors will need to know: The minimal standard-looking GUI for the web part should be designed for a regular non-knowledgeable web user.

Saturday, July 14, 2012

First book in the world and my first book in my BLOG too--HOLY BIBLE(online KJV bible) for all in online


Click here to start
"But without faith it is impossible to please him: for he that cometh to God must believe that he is, and that he is a rewarder of them that diligently seek him." - Hebrews 11:6