Comments on: Build a SharePoint Scripting Resource Center http://www.endusersharepoint.com/2010/01/05/build-a-sharepoint-scripting-resource-center/ The SharePoint "How-To" Online Magazine Fri, 15 Jan 2010 01:46:45 -0600 http://wordpress.org/?v=2.8.6 hourly 1 By: spevilgenius http://www.endusersharepoint.com/2010/01/05/build-a-sharepoint-scripting-resource-center/comment-page-1/#comment-24122 spevilgenius Tue, 12 Jan 2010 01:06:28 +0000 http://www.endusersharepoint.com/?p=4760#comment-24122 This is awesome as usual Mark! By the way, am I the only one who likes the charting components built into .Net 3.5? I see a lot of different javascript solutions, but I guess I just like the .net ones. I really can't wait to see more in this series! This is awesome as usual Mark! By the way, am I the only one who likes the charting components built into .Net 3.5? I see a lot of different javascript solutions, but I guess I just like the .net ones. I really can’t wait to see more in this series!

]]> By: Sam Allgood http://www.endusersharepoint.com/2010/01/05/build-a-sharepoint-scripting-resource-center/comment-page-1/#comment-23597 Sam Allgood Thu, 07 Jan 2010 20:45:13 +0000 http://www.endusersharepoint.com/?p=4760#comment-23597 Mark, I did as you replied and am still getting the same results. Could this be because I did not create the resource center at the root of the site (do not have administrator rights), but in a sub-site where I do have admin rights? Mark, I did as you replied and am still getting the same results. Could this be because I did not create the resource center at the root of the site (do not have administrator rights), but in a sub-site where I do have admin rights?

]]> By: EndUserSharePoint http://www.endusersharepoint.com/2010/01/05/build-a-sharepoint-scripting-resource-center/comment-page-1/#comment-23583 EndUserSharePoint Thu, 07 Jan 2010 18:26:43 +0000 http://www.endusersharepoint.com/?p=4760#comment-23583 Sam - Wiki pages are documents in a library. If you create a content type from a "List" parent, it will not be available as a document content type. Rebuild your content type using document as the parent. During that process, you can use the columns you previously created without having to do them all over again. -- Mark Sam – Wiki pages are documents in a library. If you create a content type from a “List” parent, it will not be available as a document content type. Rebuild your content type using document as the parent. During that process, you can use the columns you previously created without having to do them all over again. — Mark

]]> By: Sam Allgood http://www.endusersharepoint.com/2010/01/05/build-a-sharepoint-scripting-resource-center/comment-page-1/#comment-23551 Sam Allgood Thu, 07 Jan 2010 15:42:27 +0000 http://www.endusersharepoint.com/?p=4760#comment-23551 Mark, great post ... looking forward to the rest of the series. I am trying to follow along in creating a resource center as suggested and, as a SP newbie, am running into some issues/questions on our SharePoint 2003 site. I created the resource center as a wiki site. Then I created the Resource Center content type within that site, with the Item content type from List content types since you did not specify and it obviously uses columns like items. When I try to add the columns using 'Add from existing site columns', none of them appear in the list, but when I try to add column 'Type' using 'Add from new site column', it tells me a column with that name already exists. What am I doing wrong? Mark, great post … looking forward to the rest of the series. I am trying to follow along in creating a resource center as suggested and, as a SP newbie, am running into some issues/questions on our SharePoint 2003 site. I created the resource center as a wiki site. Then I created the Resource Center content type within that site, with the Item content type from List content types since you did not specify and it obviously uses columns like items.

When I try to add the columns using ‘Add from existing site columns’, none of them appear in the list, but when I try to add column ‘Type’ using ‘Add from new site column’, it tells me a column with that name already exists.

What am I doing wrong?

]]> By: SharePoint Daily http://www.endusersharepoint.com/2010/01/05/build-a-sharepoint-scripting-resource-center/comment-page-1/#comment-23332 SharePoint Daily Wed, 06 Jan 2010 14:03:26 +0000 http://www.endusersharepoint.com/?p=4760#comment-23332 <strong>Office 2010 Starting at $99; Microsoft's New Lenovo Tablet; Azure Almost Ready...</strong> Top News Stories Is $99 Too Much for Office 2010? (ZDNet) Have you used the beta of Office 2010? I have... Office 2010 Starting at $99; Microsoft’s New Lenovo Tablet; Azure Almost Ready…

Top News Stories Is $99 Too Much for Office 2010? (ZDNet) Have you used the beta of Office 2010? I have…

]]> By: Christophe http://www.endusersharepoint.com/2010/01/05/build-a-sharepoint-scripting-resource-center/comment-page-1/#comment-23301 Christophe Wed, 06 Jan 2010 07:29:43 +0000 http://www.endusersharepoint.com/?p=4760#comment-23301 Some random comments: - keeping track of versions is important for jQuery, but even more for plugins (like the jQuery UI I see in the screenshot). - the YUI chart API requires Flash, and is still in beta. Note that Google also offers a visualization API (I haven't tried it). It is different from the charting API you mention, and doesn't require Flash. Your first paragraph (site architecture) actually makes a good introduction to content types! @Greg: yes, older scripts could potentially break with new jQuery versions, or new plugin versions. And calling two different versions in the same page will be an issue as the second library you call will overwrite the first one. Some random comments:
- keeping track of versions is important for jQuery, but even more for plugins (like the jQuery UI I see in the screenshot).
- the YUI chart API requires Flash, and is still in beta. Note that Google also offers a visualization API (I haven’t tried it). It is different from the charting API you mention, and doesn’t require Flash.

Your first paragraph (site architecture) actually makes a good introduction to content types!

@Greg: yes, older scripts could potentially break with new jQuery versions, or new plugin versions. And calling two different versions in the same page will be an issue as the second library you call will overwrite the first one.

]]> By: Marc D Anderson http://www.endusersharepoint.com/2010/01/05/build-a-sharepoint-scripting-resource-center/comment-page-1/#comment-23280 Marc D Anderson Wed, 06 Jan 2010 04:49:28 +0000 http://www.endusersharepoint.com/?p=4760#comment-23280 FYI -- I'm working on a function called <a href="http://spservices.codeplex.com/wikipage?title=%24%28%29.SPServices.SPScriptAudit" rel="nofollow">SPScriptAudit</a> for my jQuery Library for SharePoint Web Services (which Mark mentions above). This function will help keep track of the script usage across a Site Collection. Take a look at the <a href="http://www.sympraxisconsulting.com/Demos/Demo%20Pages/SPScriptAudit.aspx" rel="nofollow">demo page</a> for this work-in-progress and let me know whether it seems useful for you, if you have enhancement ideas, etc. M. FYI — I’m working on a function called SPScriptAudit for my jQuery Library for SharePoint Web Services (which Mark mentions above). This function will help keep track of the script usage across a Site Collection. Take a look at the demo page for this work-in-progress and let me know whether it seems useful for you, if you have enhancement ideas, etc.

M.

]]> By: EndUserSharePoint http://www.endusersharepoint.com/2010/01/05/build-a-sharepoint-scripting-resource-center/comment-page-1/#comment-23270 EndUserSharePoint Wed, 06 Jan 2010 02:56:13 +0000 http://www.endusersharepoint.com/?p=4760#comment-23270 Greg, Yes, always pointing to the most current version could break your solutions. Both Paul Grenier and Christophe Humbert have run into that situation. That's why I have the legacy scripts in place with the full version name. Mark Greg,

Yes, always pointing to the most current version could break your solutions. Both Paul Grenier and Christophe Humbert have run into that situation. That’s why I have the legacy scripts in place with the full version name.

Mark

]]> By: Greg Schaefer http://www.endusersharepoint.com/2010/01/05/build-a-sharepoint-scripting-resource-center/comment-page-1/#comment-23265 Greg Schaefer Wed, 06 Jan 2010 02:02:54 +0000 http://www.endusersharepoint.com/?p=4760#comment-23265 Mark, Really looking forward to this Series! If I understand it well, the CEWP should point to: J Query 'Current' (which is overwritten when a new version is issued) and the list also list JQuery V2 (the latest version issued - copy pasted as the JQuery Current JQuery V1 (1st revision) JQuery (initial version) right? Silly question...if 2 CEWPs are pointing to 2 separate scripts (from 2 different authors) intialy pointing to 2 different versions of J Query, should the 2 scripts be updated by pointing to the J Query 'Current'? Could pointing to a more recent JQuery version, 'break' a script? Greg Mark,
Really looking forward to this Series!
If I understand it well, the CEWP should point to:
J Query ‘Current’ (which is overwritten when a new version is issued)
and the list also list
JQuery V2 (the latest version issued – copy pasted as the JQuery Current
JQuery V1 (1st revision)
JQuery (initial version)
right?

Silly question…if 2 CEWPs are pointing to 2 separate scripts (from 2 different authors) intialy pointing
to 2 different versions of J Query, should the 2 scripts be updated by pointing to the J Query ‘Current’?
Could pointing to a more recent JQuery version, ‘break’ a script?

Greg

]]> By: Devin Walker http://www.endusersharepoint.com/2010/01/05/build-a-sharepoint-scripting-resource-center/comment-page-1/#comment-23252 Devin Walker Tue, 05 Jan 2010 23:13:59 +0000 http://www.endusersharepoint.com/?p=4760#comment-23252 Wow, this is a great post. Would be very helpful for development teams to have an implementation like this to house all their resources. Wow, this is a great post. Would be very helpful for development teams to have an implementation like this to house all their resources.

]]>