Browsed by
Month: February 2009

jQuery Performace Problem & Solution

jQuery Performace Problem & Solution

One of my current tasks is to refactor our SharePoint portal’s design. The original design was heavily laden with tables and large images.And each new subsite had its own master page, style sheet, and images directory. It was performing poorly in the browsers, and making it painful to create new subsites. So I’m making a CSS-based version, removing all the images, simplifying the design while improving performance and flexibility. The end result was much faster, but the look was too…

Read More Read More

Notes Dev Hall of Shame #2

Notes Dev Hall of Shame #2

Standard disclaimer – the ‘migratenotes’ posts come from a Notes Migration blog that I wrote from 2007-2010.  More Info ——- The main topic for today is user-configurable data. It is true that hard-coding data is bad. The values in various drop-down lists, etc, would ideally be populated from data that the business owners can update. But somehow, the idea of “hard-coding is bad” got misunderstood. One former developer obviously missed the point… that the idea was to not require code…

Read More Read More

Roadmap for functions in the SharePoint World

Roadmap for functions in the SharePoint World

Standard disclaimer – the ‘migratenotes’ posts come from a Notes Migration blog that I wrote from 2007-2010.  More Info ——- When people say “SharePoint”, they usually mean any application accessed through a SharePoint portal. In truth, this may actually be SharePoint, but could also mean .NET or InfoPath applications. One of the challenges we’ve had is defining which types of applications really are a SharePoint app vs. InfoPath vs. .NET. But before I go there… why does it matter? It…

Read More Read More

Code Quality vs. Platform Quality

Code Quality vs. Platform Quality

Standard disclaimer – the ‘migratenotes’ posts come from a Notes Migration blog that I wrote from 2007-2010.  More Info ——- If you’ve read the previous post, you know that the code quality at my current job is… questionable. Not all of it, to be sure. There is some good work. But… one bad app spoils the bunch, so to speak. That form that took 10 minutes to open? It made people believe that Notes was a poor platform that could…

Read More Read More

Notes Dev Hall of Shame — #1

Notes Dev Hall of Shame — #1

Standard disclaimer – the ‘migratenotes’ posts come from a Notes Migration blog that I wrote from 2007-2010.  More Info ——- I wanted to share a few choice items that have not only boggled our minds, but also caused endless amounts of helpdesk tickets. 1) The EmployeeID field in names.nsf At first glance, it almost looks reasonable. They added a field to the person document, labelled “Employee ID”, called EmployeeID, and updated nightly from our HR system. All applications look to…

Read More Read More

Bad News From Work…

Bad News From Work…

Standard disclaimer – the ‘migratenotes’ posts come from a Notes Migration blog that I wrote from 2007-2010.  More Info ——- I got bad news today at work… No, not a layoff. But the economy has shut down some projects, as I may have mentioned before. Specifically, it shut down projects there were intended to replace my largest, most complex Notes apps. These two apps are the ones that will make or break this migration, as they are used across the…

Read More Read More

Philosophy on Tools

Philosophy on Tools

Standard disclaimer – the ‘migratenotes’ posts come from a Notes Migration blog that I wrote from 2007-2010.  More Info ——- I’m always very resistant to buying tools for development work, and that is part of the reason that I have not pursued any tools for this migration. The other reason being that, while we are migrating away from Notes, it is intended to be a slow attrition, not an active push to get rid of the platform, so we don’t…

Read More Read More