posted 14 January 2009 16:24 by AussieNigel

<script type="text/javascript">
    function GetElementByText(tagName, title)
    {
        var a = document.getElementsByTagName(tagName);

        for (var i=0; i < a.length; i++)
        {
            if (a[i].text)
            {
                if (a[i].text === title)
                {
                    return a[i];
                }
            }
        }

        return null;
    }

    if (window.onload)
    {
        var oLoad = window.onload;
        window.onload = function bodyLoad()
        {
            oLoad();

            var o = GetElementByText("ie:menuitem","Upload Document");
            if (o)
            {
                o.disabled = true;
            }
        }
    }
</script>

<script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.2.6/jquery.min.js"></script>
<script type="text/javascript">
  jQuery.jQueryRandom = 0;
  jQuery.extend(jQuery.expr[":"], {
    random: function(a, i, m, r) {
      if (i == 0) {
        jQuery.jQueryRandom = Math.floor(Math.random() * r.length);
      };
      return i == jQuery.jQueryRandom;
    }
  });
</script>
<script type="text/javascript">
$().ready(function() {
  var a = $("table.ms-summarystandardbody td.ms-vb2 a:random");
  a.parents("div[id^=WebPart]").html('<img src="' + a.attr("href") + '"/>');
});
</script>

What it does? First of all I extend the jQuery framework with the “:random” filter which allows me to pick a randomly chosen element. Then, as soon as the page has been loaded I select all the links from the Images Web Part and pick a random one to display. The last thing I do is to substitute the list of images with the random image I’ve just picked:

That’s all!

Each time you load this page another image will be picked and displayed.

What’s next?

The example I’ve presented is quite simple. Because we’re using a common SharePoint list here, you could store some metadata together with the images and make them appear on the page as well. You could extend the script to add the title, description and maybe even a link to a different site: the sky is the limit.

Summary

Providing custom functionality doesn’t necessarily have to mean development and deployment. By just extending the standard SharePoint functionality with JavaScript you can easily create great features which can enhance the overall experience of your application. Using the jQuery framework you can simplify creating these enhancements even more. jQuery covers for you all the basics and allows you to focus on the functionality you to provide to your users.

Quote

Sharepoint Marquee Scroll Listings

 

One of our clients approached us with an interesting idea. I welcomed his request because he was such an ambitious client. Anyway, the request was scrolling the listings of any area. He wanted to display the listings on a marquee tag. While researching it, I couldn't find anything similar on the net, so I thought I’d share this webpart with you .

 

I created a C# webpart to have the following features :

 

 

1- display area listings ordered by the created date (last created first shows)

2- an icon image (e.g. Company logo) separates between listings

  

Since I have attached the source code of this webpart; you can upgrade the solution to have other feature like:

1- show the top (n) number of  listings

2- stop scrolling when mouse over

3- you can set a scroll left/scroll right functions

 

Here are simple steps to deploy the webpart on your portal

 

Step 1

Download the the project from here http://cid-c6d240d97b073074.skydrive.live.com/self.aspx/Attachments/MarqueeListings_Zip.zip

 

Step 2

Go to the bin\Debug where the assembly file of the Marquee listing resides(MarqueeListings.dll) .this dll file has to be dragged and dropped to the GAC

(HD:\WINDOWS\assembly ).

 

 

Step 3

Copy the image MarqueeIcon.GIF to the sharepoint images

location :  HD:\Program Files\Common Files\Microsoft Shared\web server

extensions\60\TEMPLATE\LAYOUTS\1033\IMAGES  

 

Step 4

The webpart has to be registered as safe control. so copy the following script

 

<SafeControl Assembly="MarqueeListings, Version=1.0.0.0, Culture=Neutral, PublicKeyToken=78fabca6851eb8f0" Namespace="Sharepoint.Afkar.MarqueeListings" TypeName="*" Safe="True" />

      < P Assembly="MarqueeListings, Version=1.0.0.0, Culture=Neutral,

 

Then add it to the web.config  which resides on the virtual  directory of your portal

 

Step 5

Restart IIS.

 

Step 6

Import the webpart MarqueeGroupedListings.dwp to the portal. The web part displays the grouped listings of the home page of the server . if you want to change to display the listings of another area you need to modify the web part  .under the Marquee options write the Url of the area (e.g.  http://serverName/Area2)

 

Step 7

There is no step 7. Its Over!!!  But incase you want to display other area's listings you need to edit the webpart properties giving the correct area URL

 

Code Sample
private const string defaultURL = "";
  private string _URL = defaultURL;

  [Browsable(true),Category("Marquee Options"),
  DefaultValue(defaultURL),
  WebPartStorage(Storage.Personal),
  FriendlyName("Area URL"),Description("Area URL")]
  public string URL
  {
   get
   {
    return _URL;
   }

   set
   {
    _URL = value;
   }
  }
   protected override void RenderWebPart(HtmlTextWriter output)
  {
   try
   {
 //******************************This section to get the Grouped listings of any area***************
    AreaListingCollection areaListings=GetAreaListings(this.URL.ToString());
     if (areaListings!=null)
    {
     if (areaListings.Count>0)
     {
      string str="";
      int counter=0;
      ArrayList textArrayList = new ArrayList();
      ArrayList linkArrayList = new ArrayList();
      //this is order the last one entered appears in the first
      int TotalNewNUm=0;

      foreach (AreaListing areaListing in areaListings)
      {
       textArrayList.Add (areaListing.Title.ToString()  )  ;
       linkArrayList.Add (areaListing.URL.ToString()  )  ;
       TotalNewNUm++;
               
      }//foreach
      int i ;
      for(i=TotalNewNUm-1 ;i>=0  ;i--)
      {
       str+= "<a href=" + linkArrayList[i] + " target=_blank > <span style='font-family:verdana ; font-size: 8pt ;  height:5px; margin-bottom:3px; '>" + textArrayList[i] + "</span> </a>" ;         
       counter++;
       if (i !=0)
       {
        str+=   "<img style='margin-top:5px;' src='/_layouts/1033/images/MarqueeIcon.GIF' >" ;
       }
      }

      output.Write( " <marquee>" + str + "</marquee>" );
         
     }
     else
     {
     output.WriteLine (" There is No listings in this area  " + this.URL.ToString() + "   !");
     }
    }
    else
    {
     output.Write ("Wrong area URL, Go back to the webpart properties to correct the area URL (e.g http://serverName:port/areaName)");
    }

   }
     
   catch (Exception ee)
   {
    output.Write (   "Errorr : " + ee.Message   );
    
   }
  }
  private AreaListingCollection GetAreaListings(string url)
  {

   SPSite siteCollection;
   SPWeb site ;

   try
   {
    if (url=="")
    {
     siteCollection = SPControl.GetContextSite(Context);
     site = SPControl.GetContextWeb(Context);   
    }
    else
    {
     siteCollection = new SPSite(url);
     site = siteCollection.OpenWeb();
    }
   
    TopologyManager topologyManager = new TopologyManager();
    Uri uri =new Uri(siteCollection.Url);//new Uri("http://MyPortal");
    PortalSiteCollection sites = topologyManager.PortalSites;
    PortalContext portalContext = PortalApplication.GetContext(sites[uri]);
    Area newsArea = AreaManager.GetArea(portalContext, site.ID);
    return newsArea.Listings;
    
   }
   catch (Exception ee)
   {
     return null;
   }
  }

  

This Article Published on:

http://ahmadadainat.spaces.live.com

 

http://www.msd2d.com/Content/Tip_viewitem_03.aspx?section=SharePoint&category=Development&id=2aeb45ef-c623-4b79-b6cf-1e5354276422

 

Please drop me an email if you have any comments or enquiries.  ahmad.adainat@gmail.com , dont forget to swing by my blog to see my latests.

 

ref:http://www.ie-soft.de/blog/PermaLink,guid,968b0588-f306-467b-be51-54f7a8f2079d.aspx

ref:http://www.ie-soft.de/blog/PermaLink,guid,cb97a3df-6725-468c-97fa-725e2c4ceb4c.aspx

Okay, this one took me a while to figure out, but nonetheless I found it and will share it.

In order to turn off or disable the MySite or MyLinks functionality you need to be an Sharepoint administrator.

Go to the Central Administration Web Page
Click on the link for Shared Services Administration
     --If you have more than one SSP, select the one that is running the MySites functionality
Under "User Profiles and My Sites" click Personalization Services Permissions

Select the group you want to limit the functionality for.  More than likely you will just have NTAuthority\Authenticated Users.

In the next screen you will see a list of checkboxes,
     --To disable MySites uncheck "Create Personal Site"
     --To disable MyLinks uncheck "Use Personal Features"

Once you find it, disabling the functionality is pretty easy, but if you are new to 2007 like I am it will take a while to find.  Hopefully this will save you a few cycles.

ref:http://geekswithblogs.net/RogueCoder/archive/2006/11/01/95766.aspx

Quote

SharePoint Usage Analytics

 

We must enable usage analytics to measure our SharePoint site usage and performance through the Site Usage Reports and Site Collection Usage Reports of Microsoft Office SharePoint Server 2007 or through Site Usage Reports provided by Microsoft Office SharePoint Designer 2007.

In Windows SharePoint Services 3.0/Microsoft Office SharePoint Server 2007, the following are the usage analytical reports:

Site Usage Reports:

1. Site Usage Summary

2. Requests

3. Users

4. Referrers

5. Destination Pages

Site Collection Usage Reports:

1. Site Usage Summary

2. Requests

3. Users

4. Referrers

5. Destination Pages

6. Search Queries

7. Search Results

The Microsoft Office SharePoint Designer 2007 provides the following SharePoint usage reports:

1. Usage Summary

2. Page Hits

3. Visiting Users

4. Operating Systems

5. Browsers

6. Referring Domains and URLs

7. Search Strings

To enable usage analytics, we need to perform the following:

1. Enable Windows SharePoint Services usage logging

2. Enable the usage reporting shared service

3. Activate the reporting feature

 

    

 

 

   

 

   

That's it! Thanks...

Our main service is providing nearshore outsourcing to customers around the globe. It is very important for us to track effort spent as much detailed as possible, and report it to our customers, usually on a weekly basis.

After trying with other tools and not being 100% satisfied, we decided to take advantage of Microsoft tools and start using Project Server 2007 for time management here in our company.

I spent some hours doing research about this topic, and I found different articles and posts explaining just one chapter at a time, without finding a complete guide to install and configure this tool for this particular goal.

Even after we followed all the steps found around several sources, we were still not able to generate the reports with the time spent by the resources selected for this pilot, due to some issues with the browser and also with the Cube (Project integrates with Analysis Services) used for populating the data.

Then after several hours of effort with one of our Senior developers, we had our Project Server running and some of our team members were able to enter their timesheets using Project Web Access, a web interface exposed by this technology.

Using Project Server also enabled us to integrate Sharepoint workspaces for centralizing project documentation, risks, issues and tasks, with project schedule, costs and time management that we can also publish through web so our customers can have a snapshot of the project anytime. We can generate customized reports through Pivot Tables and Analysis Services integration.

Having this said, this is a powerful tool with a complete set of features, ideal for small, medium or enterprise organizations. Some features such as the web interface are really helpful for our nearshore software development practice, enabling both customers and remote teams to access the data everywhere.

These are the steps you should follow in order to install and configure Project Server 2007 for timesheet management:

1. Install Sharepoint Server 2007 in a brand new Virtual Machine with Windows Server 2003.

Step by step and different deployment scenarios can be found here: http://technet.microsoft.com/en-us/library/cc197758.aspx#section2

2. After installed, the project web access is located in a url like http://servername:port/PWA

3. Add a few domain users to the Project Server using the Server Settings / Security / Manage Users link.

4. Add your team members into Project Server resources list, using the Resources Center. These will be the team members you will allocate to each project and task.

5. Even when you can do almost everything from the Project Server web interface, it is faster to use your desktop version of Office Project 2007 to create projects, tasks and allocate resources. This requires the PM to have MS Office Project 2007 Professional version installed (Standard doesn´t support it)

6. To connect your Office Project to the Project Server 2007, you need to configure it through the Enterprise Options under the Tools menu.

7. Create a test project using the Project Center link / Add Project.

8. After adding a few test tasks, you must assign the team to the project and each task. This will allow the team members to see the assigned tasks and

a. Go to Build Team From Enterprise

b. Select the task(s)

c. Go to Assign Resources

d. Select the resources you want to assign. You can set costs and effort allocated.

9. Project Server requires timesheets periods to be defined (in most of the cases these will be mapped to each week of the year). You should go through each link in the Timesheets section under the Server Settings section.

There is a complete ebook for this topic which you should download and read from here http://technet.microsoft.com/en-us/library/cc197478.aspx

10. Once the timesheets periods have been defined, your team member should be able to view the assigned tasks after login into the PWA with his credentials.

11. Each resource will be responsible for creating the timesheet and reporting it. The timesheet can be populated with the assigned tasks, or can be blank and then populated using the Add New Line link

12. Resource should submit his timesheet. These will be usually automatically approved unless you configure it. The timesheet cannot be updated except for the admin, once it is submitted.

Once all of this is done, the database will have the data but you won´t be able to retrieve it using the reports yet.

First, you need to configure this feature, otherwise you will see just a blank page when clicking the Data Analysis link

In order to configure the Reports follow these steps:

1. Go to Create Server Settings, Views, New View, and select Data Analysis as the view type

2. Select your Data Analysis Services. If is it not populated you should go to check if Analysis Services was installed and all services are running.

3. Configure the settings and the data view properties (just follow the sections in the screen)

4. Configure the fields you want to display in the default timesheet view

5. Add the project server URL to the list of Local Intranet sites in your browser settings.

6. Configure your browser settings to allow ActiveX.

7. Configure your browser settings to allow Data Sources across domains.

And that´s all!

So if you follow these steps then you will be able to take advantage of Project Server reporting features:

I hope this guide is useful and ping us if you face any issues when using this powerful tool !

So far we are really satisfied with it.

Post written by - Marcelo Lopez, Project Manager @ UruIT Global IT Services