Archive for the ‘Software Development’ Category.

WPF / Silverlight Links

09/15/2009 – Edit: I now have a static page dedicated to these links.

I’m just starting go through my WPF books, so I wanted to capture some useful WPF / Silverlight links that I’ve discovered over the last year.

Windows Client – Winforms and WPF Home. Information, tutorials, links.
http://windowsclient.net/default.aspx

Silverlight Home – Information, tutorials, links.
http://silverlight.net/default.aspx

Web Platform – Microsoft Web Platform Information. Web Platform Installer download.
http://www.microsoft.com/web/default.aspx

Codeplex WPF Home – Portal for accessing the WPF Toolkit and the WPF Futures releases.
http://www.codeplex.com/wpf

WPF Toolkit – Additional Controls, Themes, and Tools for WPF.
http://wpf.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=29117

Silverlight Toolkit – Additional Controls, Themes, and Tools for Silverlight.
http://silverlight.codeplex.com/

Patterns and Practicies: Composite WPF and Silverlight (Prism) – WPF /Silverlight Application Framework and Patterns.
http://compositewpf.codeplex.com/

Caliburn – WPF / Silverlight Application Framework.
http://caliburn.codeplex.com/

Visifire – Free (for GPL’d works) Silverlight and WPF Charting Controls. Has dual licensing model for closed source usage.
http://www.visifire.com/

Kaxaml – Lightweight XAML Editor.
http://www.kaxaml.com/

WebAii – Free Web Application Testing Framework for IE and Firefox. V2 Will support Silverlight.
http://www.artoftest.com/products/webaii.aspx

Ninject – Fast, Lightweight .Net Dependency Injection
http://www.ninject.org/

  • email
  • DotNetKicks
  • Digg
  • del.icio.us
  • Technorati
  • StumbleUpon
  • LinkedIn
  • Facebook
  • Twitter
  • Google Bookmarks
  • Live

Positive Feedback Systems in Line of Business Applications

Last week I was having one of those “what if” conversations with a coworker regarding our application and I mentioned jokingly that we should add an achievement system into the app, kind of like Xbox or StackOverflow. The more I thought about it, the more I started asking myself, why *don’t* businesses consider this kind of functionality for applications? I know there are always time and resource pressures for software projects which might make the priority of such a feature float to the bottom of any project teams task bucket, but there may be something more to this. If you figure that the average end user is stuck using the same set of software on a daily basis to complete their work day after day, adding features to business applications that actually reward them in subtle ways for being productive and make using the software more fun may not be so superfluous after all.

I’ve heard that it’s not uncommon for sales teams to have “scores” and leader boards to encourage friendly competition among the various members of the team, why shouldn’t business software contain similar concepts if the data allows it? The fun part is, such a system would be relatively trivial to implement with the average data set that a line of business application collects about user activity. Maybe you just made $10,000 in sales today, how great would it be if your CRM application rewarded you with a little badge to display on your user profile?

  • email
  • DotNetKicks
  • Digg
  • del.icio.us
  • Technorati
  • StumbleUpon
  • LinkedIn
  • Facebook
  • Twitter
  • Google Bookmarks
  • Live

.Net Developer News & Downloads

Retroactive Browser Compatibility

When working on an existing web application you may be placed in a situation where you need to support new browsers, or just other browsers that your app wasn’t originally coded for or tested in. In my case, this took the form of a web app developed exclusively for Internet Explorer that now needed to support other browsers. As I went through and corrected many of the browser incompatibilities, I noticed a few common ones, and wanted to mention them in case it’s beneficial to others in the same situation.

I should mention up front that jQuery was an indispensible tool when I was working on this project as in many cases I was able to replace the offending JavaScript with a jQuery equivalent that was cross browser compatible. If you’re a web developer and are not familiar with jQuery, you probably should be. ;-)

So a couple of things to look out for… I wanted to list the easiest ones to spot first as you can do a text search and usually find all of them:

  1. CSS Expressions:
    • Were implemented in IE5 and allow you to assign a JavaScript expression to a CSS property.
    • Were deprecated in IE8 standards mode, see http://blogs.msdn.com/ie/archive/2008/10/16/ending-expressions.aspx for details.
    • IE specific.
    • Search for: “expression(”
    • Replace with JavaScript that dynamically modifies the CSS properties in response to specific browser events (onresize, etc).
      • In many cases this can be more performant than CSS expressions because you can choose to bind to specific events (CSS expressions are reevaluated *every* time a JavaScript event with at least 1 listener fires.
  2. outerHTML:
    • “Get or set the HTML of the entire node x, including the outermost tag (element x itself).”
    • Example: x.outerHTML = “Let’s <u>change</u> it!”
    • IE specific.
    • Search for: “outerHTML”
    • Replace with innerHTML or W3C DOM methods. innerHTML is in theory faster, but IE and Konquerer have some issues when innerHTML is used with tables. Replacing outerHTML with calls to innerHTML will also require some changes to the logic using outerHTML as innerHTML is slightly different in behavior.
  3. Visual Filters:
    • Used commonly to create gradients without using images.
    • More information on Visual Filters: http://msdn.microsoft.com/en-us/library/ms532853.aspx
    • IE specific.
    • Example: <ELEMENT STYLE=”filter:progid:DXImageTransform.Microsoft.Gradient(sProperties)” … >
    • Search for: “DXImageTransform”
    • Replace with… Unfortunately there really isn’t an equivalent for this. Some of the visual filters can be replicated using standard CSS properties, but not all of them. As convenient as the visual filters are, they will only work in internet explorer at the moment.
  4. Window.Event:
    • Used to access JavaScript event information in IE.
    • IE Specific.
    • Search for: “window.event”
    • This item could have several pages written about it, but the short story is that IE handles passing JavaScript event information differently than other browsers. You will need to code your JavaScript to accommodate this difference. jQuery can again be useful here as it can abstract a lot of this problem away from you. I recommend reading the section on events here: http://www.reloco.com.ar/mozilla/compat.html as it will give you an overview of the problem and how to address it.
  5. Custom Attributes:
    • Used to defined custom element attributes.
    • Getting or setting custom attributes without using DOM methods is not cross browser compatible.
      • Example: element.MyProp = “This doesn’t work in all browsers.”
    • Search for… No good search string for these. You just need to keep your eyes out for JavaScript that makes calls to custom attributes without using DOM methods (or jQuery).
    • Replace with: calls to .getAttribute(“MyProp”) or setAttribute(“MyProp”) or if using jQuery, element.attr() as shown here: http://docs.jquery.com/Attributes/attr.

This list is by no means exhaustive, but I wanted to point out many of the common issues I have come across. Your mileage may vary. I recommend checking out the references listed below for a lot more good compatibility information. I’ve tried to check all of my facts, but if you notice anything that seems off, let me know so I can fix it!

References:

  • http://www.reloco.com.ar/mozilla/compat.html – “Making your web browser compatible with Firefox”
    • A good overview of many of the common browser compatibility problems faced when making an web app written for IE work in Firefox
  • http://www.quirksmode.org/compatibility.html – “Compatibility Master Table”
    • The holy grail of browser compatibility information. Seriously… Want to know if a browser fully supports CSS2, CSS3, DOM, etc? It’s here.
  • http://reference.sitepoint.com/ – “CSS/HTML/JavaScript Reference”
    • Reference site for CSS, HTML, and JavaScript information. Its got a clean layout and additionally contains browser compatibility information for each of the items.
  • http://blogs.msdn.com/ie/archive/2009/03/12/site-compatibility-and-ie8.aspx – “Site Compatibility and IE8”
    • A page detailing potential issues and fixes for making your pages compatible with IE8 in Standards Mode. This is actually a good reference for potential cross browser problems as most of the items listed are cross browser compatibility issues as well.
  • email
  • DotNetKicks
  • Digg
  • del.icio.us
  • Technorati
  • StumbleUpon
  • LinkedIn
  • Facebook
  • Twitter
  • Google Bookmarks
  • Live

Official jQuery 1.3.0, 1.3.1 Visual Studio Intellisense Files

It looks like this weekend while I was at the South Florida Code Camp the jQuery team has posted the official jQuery 1.3.1 Visual Studio intellisense file. You can get it from the jQuery downloads page, or more directly from the jQuery Google Code download page.

The official 1.3.0 documentation was posted this weekend as well and is also available from the downloads link above, or this Google Code download page.

Keep your eyes peeled for a jQuery 1.3.2 release anytime in the next few days as John Resig has mentioned there is still one last 1.3 regression they are working on fixing.

For those interested, the regression has to do with the $(document).ready() function waiting until images are fully loaded in Internet Explorer 6 & 7. The jQuery bug ticket ID is #3988 and here’s a Stack Overflow question in which John Resig talks about the issue in some detail.

  • email
  • DotNetKicks
  • Digg
  • del.icio.us
  • Technorati
  • StumbleUpon
  • LinkedIn
  • Facebook
  • Twitter
  • Google Bookmarks
  • Live