Click on this icon to open the XML page.Tom Van Gaever - Blog
Search:   

new .NET logo 
Tuesday, October 28, 2008, 09:40 - .NET
Posted by Administrator

add comment ( 2 views )   |  permalink   |  related link   |   ( 3 / 741 )
Custom_AddDocLibMenuItems - ctx and m objects properties 
Monday, October 13, 2008, 08:54
Posted by Administrator

Ever wondered what the ctx object properties are when creating a custom context menu?

here they are:

-----ctx---------

0: ctx[listBaseType] : 1

1: ctx[listTemplate] : 101

2: ctx[listName] : {5726BE86-34A8-47F8-AB73-105E34D807F2}

3: ctx[view] : {475151F9-6C22-45FB-B19E-FFE7EC13ADC3}

4: ctx[listUrlDir] : /projects/scans

5: ctx[HttpPath] : /projects/_vti_bin/owssvr.dll?CS=65001

6: ctx[HttpRoot] : http://xxx/projects

7: ctx[serverUrl] : null

8: ctx[imagesPath] : /_layouts/images/

9: ctx[PortalUrl] : null

10: ctx[RecycleBinEnabled] : -1

11: ctx[isWebEditorPreview] : 0

12: ctx[rootFolderForDisplay] : null

13: ctx[isPortalTemplate] : null

14: ctx[isModerated] : false

15: ctx[recursiveView] : false

16: ctx[displayFormUrl] : /projects/scans/Forms/DispForm.aspx

17: ctx[editFormUrl] : /projects/scans/Forms/EditForm.aspx

18: ctx[newFormUrl] : null

19: ctx[ctxId] : 1

20: ctx[CurrentUserId] : 24

21: ctx[isForceCheckout] : false

22: ctx[EnableMinorVersions] : false

23: ctx[ModerationStatus] : 0

24: ctx[verEnabled] : 1

25: ctx[isVersions] : 0

26: ctx[WorkflowsAssociated] : true

27: ctx[ContentTypesEnabled] : false

28: ctx[SendToLocationName] :

29: ctx[SendToLocationUrl] :

30: ctx[OfficialFileName] :

31: ctx[WriteSecurity] : 1

32: ctx[SiteTitle] : Projects

33: ctx[ListTitle] : scans

-----m---------

0: m[language] :

1: m[scrollHeight] : 0

2: m[isTextEdit] : false

3: m[currentStyle] : [object]

4: m[document] : [object]

5: m[onmouseup] : null

6: m[oncontextmenu] : null

7: m[isMultiLine] : true

8: m[clientHeight] : 0

9: m[onrowexit] : null

10: m[onbeforepaste] : null

11: m[onactivate] : null

12: m[scrollLeft] : 0

13: m[lang] :

14: m[onmousemove] : null

15: m[onmove] : null

16: m[onselectstart] : null

17: m[parentTextEdit] : [object]

18: m[oncontrolselect] : null

19: m[canHaveHTML] : true

20: m[onkeypress] : null

21: m[oncut] : null

22: m[onrowenter] : null

23: m[onmousedown] : null

24: m[onpaste] : null

25: m[className] : ms-SrvMenuUI

26: m[id] : 14_menu

27: m[onreadystatechange] : null

28: m[onbeforedeactivate] : null

29: m[hideFocus] : false

30: m[dir] :

31: m[isContentEditable] : false

32: m[onkeydown] : null

33: m[clientWidth] : 0

34: m[onlosecapture] : null

35: m[parentElement] : [object]

36: m[ondrag] : null

37: m[ondragstart] : null

38: m[oncellchange] : null

39: m[recordNumber] : null

40: m[onfilterchange] : null

41: m[onrowsinserted] : null

42: m[ondatasetcomplete] : null

43: m[onmousewheel] : null

44: m[ondragenter] : null

45: m[onblur] : null

46: m[onresizeend] : null

47: m[onerrorupdate] : null

48: m[onbeforecopy] : null

49: m[ondblclick] : null

50: m[scopeName] : HTML

51: m[onkeyup] : null

52: m[onresizestart] : null

53: m[onmouseover] : null

54: m[onmouseleave] : null

55: m[outerText] :

56: m[innerText] :

57: m[onmoveend] : null

58: m[tagName] : MENU

59: m[title] :

60: m[offsetWidth] : 0

61: m[onresize] : null

62: m[contentEditable] : inherit

63: m[runtimeStyle] : [object]

64: m[filters] : [object]

65: m[ondrop] : null

66: m[onpage] : null

67: m[onrowsdelete] : null

68: m[tagUrn] :

69: m[offsetLeft] : -1

70: m[clientTop] : 0

71: m[style] : [object]

72: m[onfocusout] : null

73: m[clientLeft] : 0

74: m[ondatasetchanged] : null

75: m[canHaveChildren] : true

76: m[ondeactivate] : null

77: m[isDisabled] : false

78: m[onpropertychange] : null

79: m[ondragover] : null

80: m[onhelp] : null

81: m[ondragend] : null

82: m[onbeforeeditfocus] : null

83: m[disabled] : false

84: m[onfocus] : null

85: m[behaviorUrns] : [object]

86: m[accessKey] :

87: m[onscroll] : null

88: m[onbeforeactivate] : null

89: m[onbeforecut] : null

90: m[readyState] : complete

91: m[all] : [object]

92: m[sourceIndex] : 1421

93: m[onclick] : null

94: m[scrollTop] : 0

95: m[oncopy] : null

96: m[onfocusin] : null

97: m[tabIndex] : 0

98: m[onbeforeupdate] : null

99: m[outerHTML] :


100: m[innerHTML] :

101: m[ondataavailable] : null

102: m[offsetHeight] : 0

103: m[onmovestart] : null

104: m[onmouseout] : null

105: m[scrollWidth] : 0

106: m[offsetTop] : -1

107: m[onmouseenter] : null

108: m[onlayoutcomplete] : null

109: m[offsetParent] : [object]

110: m[onafterupdate] : null

111: m[ondragleave] : null

112: m[children] : [object]

113: m[nodeName] : MENU

114: m[nodeValue] : null

115: m[ownerDocument] : [object]

116: m[firstChild] : null

117: m[lastChild] : null

118: m[childNodes] : [object]

119: m[nextSibling] : null

120: m[parentNode] : [object]

121: m[type] :

122: m[compact] : false

123: m[nodeType] : 1

124: m[previousSibling] : [object]

125: m[attributes] : [object]

-------------------------------------------------

Create a content editor webpart and add to the source editor:

<script language="javascript">

function Custom_AddDocLibMenuItems(m, ctx)
{
text = "<p>-----ctx---------</p>"
var teller= 0;
for(att in ctx){
text = text + "<p>"+teller+": ctx["+att+"]"+" : "+ctx[att]+"</p>"
teller++;
}

text = text + "<p>-----m---------</p>"


var teller= 0;
for(att in m){
text = text + "<p>"+teller+": m["+att+"]"+" : "+m[att]+"</p>"
teller++;
}

document.write(text);
}

</script>

1 comment ( 22 views )   |  permalink   |   ( 3 / 860 )
SharePoint Workaholic? 
Thursday, September 25, 2008, 07:50
Posted by Administrator

add comment ( 1 view )   |  permalink   |  related link   |   ( 3 / 599 )
The SharePoint Customization Hippocratic Oath 
Monday, September 22, 2008, 19:50
Posted by Administrator


I love this post by Woody Windschman:

First, Do No Harm

Use the Product : Don't customize where SharePoint already does what you need.

Do it with Style : Don't build a Master Page when a CSS theme will suffice.

Take the Data View : Don't build a binary web part when a Data View or Content Editor can do the job just as easily.

Master It : When you do need to make major changes to the layout of your pages, customize the Master, but don't throw the baby out with the bath water.

Feature it at Staples : Don't build a Site Definition when you can achieve your goals with Features and Feature Stapling.

The Definition of Success
: If you must use a Site Definition, understand the ramifications.

Original post: http://www.thesanitypoint.com/archive/2 ... -harm.aspx

2 comments ( 18 views )   |  permalink   |  related link   |   ( 3 / 640 )
Bulk Convert DOC to DOCX 
Friday, September 19, 2008, 13:53 - SharePoint
Posted by Administrator
Microsoft has a bulk conversion utility that can convert multiple DOC files to DOCX files. This blog post presents very basic information on its use. This utility has been around for a while, but a fair number of people don’t know of its existence. Because it’s a powerful tool designed to convert all files on a server (or even a bunch of servers), its use is a little cryptic. This is fine for IT professionals, but if all you want to do is bulk convert a single directory of DOC files, this post shows what you need to do.

Before you can use this tool, you need to install the Microsoft Office Compatibility Pack. While the compatibility pack is primarily used with Office 2003 to allow it to load and save Open XML files, in essence, the compatibility pack is comprised of file format converters, which the Office File Converter (OFC) uses. To use OFC, you need to install the compatibility pack even if you only have Office 2007 installed. Download the compatibility pack here.

Next, you need to download and install the Microsoft Office Migration Planning Manager (OMPM). This contains a bunch of stuff, but for bulk file conversion, we are primarily interested in just one tool, OFC.EXE. Download the Microsoft Office Migration Planning Manager here.

When installing, as usual, you will select the installation directory. OFC.EXE is in the Tools directory under the installation directory. In addition, in that directory, there is a sample OFC.INI file. To run OFC.EXE, you need to create an OFC.INI, and place it in the directory where you run OFC.EXE from.


Cross Post From http://blogs.msdn.com/ericwhite/archive ... -docx.aspx

add comment ( 1 view )   |  permalink   |  related link   |   ( 3 / 535 )

<<First <Back | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | Next> Last>>