Our goal was to create an electronic form which built in the dynamic business rules of the process, but which did not overwhelm the user. The solution ended up being a blend of InfoPath for the input form, SharePoint for the data storage and workflow processing, and jQuery

We may not all get rich, but we’re doing good work and making a difference. The SharePoint community is the glue that hold it all together.

Well, better late than never, as I’m too fond of saying. In this series, you’ve seen how you can use some DVWPs, jQuery (and simple JavaScript), and the SharePoint Web Services to build a pretty slick and complex application.

If you’ve got SharePoint hosted in the cloud with Microsoft’s BPOS or one of the great other hosting companies out there like FPWeb or Rackspace, then this type of approach may well be optimal for you.

My goal was to start providing a library of useful XSL templates for people to use in Data View Web Parts (DVWPs) or Content Query Web Parts (CQWPs) in SharePoint.

Marko showed a deceptively simple, but very nice looking, way to show fancy check boxes and radio buttons using either JavaScript or jQuery.

To me, SharePoint implementations in a large percentage of the cases ought to be evolutionary rather than revolutionary

For some time now, I’ve felt the need to set down my thoughts on the power of development in the Middle Tier for SharePoint.

I showed you what templates SharePoint Designer usually creates when you set up a Data View Web Part (DVWP).

I showed you what templates SharePoint Designer usually creates when you set up a Data View Web Part (DVWP).