“Microsoft Word 2010 Developer Building Blocks” and other wordy links…

Eric White: “The altChunk functionality of the Open XML file formats enables easy merging of documents.  You can merge content from multiple sources (other Open XML documents, HTML, plain text, and more) into a single document.  After using the Open XML SDK to set up the document that imports alternative content, if you want to convert the document so that the new content is transformed to typical Open XML WordprocessingML, you need to open and save the document using Word 2010.  Alternatively, you can use Word Automation Services to process the document and import the alternative content.”

“For your OOXML Conspiracy Theories”

Miguel de Icaza: “The energy that went into stopping OOXML could have been better used in actually completing the formula spec for ODF, which almost four years later is still not part of the ISO spec. In the eyes of the ISO world, it remains an "implementation specific" work. But "advocacy" is a little bit like watching the TV, it is relatively easy. While actually working on improving open source, or open standards is equivalent to going to work. It requires skills, time and longs hours of difficult work (particularly if you are working on the OpenOffice code base).”

listsync.codeplex.com

Sync between file folder and SharePoint list for large file scenario. Huge file ( such as media file, cad etc.) was not recommended to be directly stored in SharePoint document library. This project is focused on Huge file storing problem.”

writers.stackexchange.com

Writers is a collaboratively edited question and answer site for people who love writing. It’s 100% free, no registration required.”

“Better Handwriting For You: Book 4”

I was raised on this book!

“Silverlight 3 Released” and other links…

Sharepoint Design - 2

ScottGu’s Blog: “Silverlight 3 includes new media codec support for H.264 video, AAC audio and MPEG-4 content.  This enables you to easily play and stream media encoded using these standards.  Silverlight 3 also includes raw bitstream audio/video APIs that enable you to create additional codecs (in any .NET language) that support playing any other media format.  Silverlight 3 also adds a variety of additional media features that enable better logging (for media analytics and ad monetization scenarios), provide the ability to disable screen-savers when playing long-form video content, and enable content protection.”

“Announcing SharePoint 2010 Technical Preview”

Microsoft SharePoint Team Blog: “Today, we’re announcing that SharePoint 2010 has reached the technical preview engineering milestone. The SharePoint team is running a limited, invitation only Technical Preview program. While we’re not sharing SharePoint 2010 details at this point, we did want to give our customers & partners a sneak peek at SharePoint 2010! We’re very excited about SharePoint 2010 and looking forward to the SharePoint Conference this October where we’ll talk about all the investment areas across workloads and the platform. What we’re sharing today is just a fraction of what will be in SharePoint 2010!”

“SharePoint 2010 Sneak Peek”

Paul Andrew: “Today we introduced a sneak peek of SharePoint 2010. We’re only announcing a few of the many new features right now, but there’s some exciting stuff in the list today to talk about.” I’ve looked at the videos (especially the “Developer Sneak Peak”) and am only slightly enthused about the “SharePoint Client Object Model”—however, the formalization of this concept by Microsoft (which exists informally for SharePoint 2007) is considered here an indirect admission that the “option” to easily bypass the SharePoint UI customization hell (and use SharePoint as a data entry/access layer) is very necessary. Yes, I understand that the original physicist that envisioned the Web wanted a read-write experience but this idea that data must be edited in place everywhere it appears should be considered one strategy among many instead of the only way to go…

“Introducing the SharePoint object model”

Nick Grattan: “As an alternative to programming against the SharePoint web services you can use the SharePoint object model. The object model can be used when the application will run on the server where SharePoint is installed (such as a console or WinForm application) or in assemblies that are run within a site (such as a Web Part).” Okay, this does not sound like ‘bypassing’ SharePoint and more like tight coupling from the 1990s… This is not a superior loose-coupling option over SharePoint Web Services.

“Using XamlReader.Load”

MSDN: “…the ability to create managed objects from XAML input is still available in the managed API, by using the static method XamlReader..::.Load. This topic explains how to use the Load method, provides requirements for the input XAML, explains how to connect the output to the object tree, and discusses the XAML namescope issues that can affect using the FindName method against parts of the object tree that originated from a call to Load.” This method should allow me to use the same AJAX-friendly server(s) that I use for XHTML with XAML. All I need to do on the server side is use different XSL templates that render XAML against XML data instead of XHTML.

Random Screenshot: A “Blank” SharePoint Site in a GNOME Folder

Random Screenshot: A “Blank” SharePoint Site in a GNOME Folder

So let’s take a peek at what Windows SharePoint Services (WSS) generates for a “Blank” Collaboration Site. What jumps out at my inexperience with the inelegant innards of SharePoint is the absence of .ASPX files. There’s locale resources, some FrontPage-looking (WebDAV) stuff, some kind of browser capability database (see “Add Blackberry support to Forms Server 2007 or SharePoint 2007”), a *.DLL file for SOAP, a *.DLL file for ‘application pages,’ two different web.config files and the global.asax file that is probably doing most of the heavy lifting.

I assume the rest of the site is in the Content Database. And, oh, by the way, I had some kind of disk catastrophe yesterday and lost a 300meg WSS Content Database! Because the log had some open transactions I could not recover the database. I got almost everything back as disk files (not in SharePoint) from a backup.

Ted Pattison, Spencer Harbar and Why I Uninstalled Expression Web

The future of FrontPage Hello. I uninstalled Expression Web because I use SharePoint and Visual Studio. I uninstalled Expression Web in order to install SharePoint Designer. It was Ted Pattison that finally explained to me in “Customizing a Windows SharePoint Services V3 site with the SharePoint Designer 2007” why I need SharePoint Designer. Ted is a very special guy. He seems to be the only person on Earth who can explain SharePoint in ways that I can understand. Too many SharePoint presenters get lost in more than six details of this ridiculously complex product, dramatizing “Business Intelligence” scenarios that I do not care about. But a strong dude like Ted Pattison can leap up to the 30,000-foot level to provide a clear overview and then jump back into the details. He can do this several times during his presentations casually and easily. I appreciate this strength.

Here are two sad facts for Visual Studio users, who have installed extensions for SharePoint about why you still need SharePoint Designer:

  • One: try to open a SharePoint web site in Visual Studio. You should get an error message.
  • Two: SharePoint Designer can open SharePoint webs and provide version control for pages using the native SharePoint database.

Now are you worried about the differences between SharePoint designer and Expression Web? Spencer Harbar explains in “SharePoint Designer and Expression Web”:

Currently there is really only one key difference—Expression Web cannot open SharePoint sites. Otherwise it’s basically the same (Expression Web has a nicer splash screen). Now this won’t always be the case, and you can expect divergence in the future.

Also, Microsoft has a cute diagram leading MOSS and WSS developers to SharePoint Designer. Of course, since I am guy that’s so “negative,” I cannot leave this journal entry without expressing my undying hatred for FrontPage. FrontPage sucks—and a “portion” of FrontPage technology lives on in SharePoint Designer (and Expression Web).

And one more rant: it will be a bright sunny day in rainy Redmond when someone among the tens of thousands employees announces that SharePoint will be XHTML compliant. It is intellectually and technically disgusting to see 1990s HTML tag shit that makes hundreds of SharePoint pages so filthy. Ask any professional Web developer the last time they saw HTML tags in upper case… When you get through with that, check out this awesome post, “Guide to making SharePoint XHTML Compliant.”

Also:

A bunch of SharePoint “How We Did It” Testimonials

The idea behind my collecting all of these links was to read on and on through the marketing-biased fluff just to find a valuable nugget here and there that would actually help me grasp the freaking hugeness of SharePoint.