A long long time ago, in what seems now like another world, I worked for a company as a Clipper programmer. While I was there I heard this story about a lady named Debbie.
I was told that Debbie was a programmer who used to work for this company. Debbie was a lazy programmer. She worked harder at avoiding work than if she just did the job she was supposed to do.
Several years ago, long before the community was actively talking about Test Driven Development, I worked for a short time at a company as a “bug fixer.” That was my role. They had hired me because they had some software that was “basically done” but “had some issues.” It should only take a few weeks.
The first thing they needed me to fix was that the website was supposed to send out email. It turns out it was a configuration problem. But they were so impressed (“the last guy we had in here spent two weeks on that problem and still hadn’t solved the problem.”) that they gave me more and more bugs.
On Monday 2/17/14 I gave a presentation at the CT .NET User’s Group on using Selenium and NUnit to test your web application. The following is a list of resources from that presentation:
The IF statement we looked at on Tuesday was pretty tame compared to the WHILE construct. Actually, the main thing you need to keep in mind is that WHILE is all you have. There is no such thing as a FOR loop or a DO WHILE loop. So, you have to force WHILE to do those for you. The basic syntax of WHILE looks like this:
SQL has long had the ability to specify that a value is NULL even if it is a primitive type, but the only way you could have a NULL value in VB.NET is if you were dealing with an object. That is, until .NET 2.0
Yesterday, I spent the bulk of the day converting a DataList to a ListView. I thought I’d spend a little time relating the process for those of you who might be interested in doing the same.
Several weeks ago I presented jQuery at the DotNet User’s Group in Connecticut. As part of that presentation, I mentioned that I handle errors from my WebServices in a slightly different way than what most authors teach.
Many times in our queries, we aren’t looking for an exact match. We are looking for one string that exists in another. There are a couple statements available to us that will allow us to do this. The first of these is the LIKE statement, and if you are familiar with DOS or the Linux equivalent, this should look familiar to you. The most common usage of LIKE looks like this:
A couple of weeks ago I mentioned that I had built a tooltip using jQuery. We focused mostly on the positioning of the tooltip at the time because, historically, that’s where most of the work has been. But there are other time-saving features that also make the tooltip code I wrote a lot more flexible. For example, in the past, the javascript code we wrote for tooltips often required us to place the HTML for the tooltip in the HTML page we wanted the tooltip on. This has two drawbacks. First, if you need the tooltip on multiple pages, you need to include the HTML on multiple pages. You could, of course, use master pages in ASP.NET or includes of some sort in other web development languages to get around this, but the fact remains that you still need to do this. Second, the HTML is not as modular as it might be. This isn’t as big of an issue, since we could argue that most of our HTML is not as modular as it might be, but when I show you how you can overcome this with jQuery, I think you will recognize the improvement. When I sat down to develop this tooltip, I created an HTML page that has the HTML for the tooltip, and nothing else, in it. This allowed me to concentrate on the HTML and forget about all the javascript issues. Once I had the tooltip looking the way I wanted, I copied out the HTML fragment that represented the tooltip, leaving out the HTML that had the head tag, body tag, and other code I needed to make the HTML page an HTML page. I pasted this code into another HTML file, but this time the HTML file ONLY has the fragment. The other thing you’ll want to do is to dynamically create the positional DIV that you will use to hold the tooltip. This is another place where we typically had to put the content in our HTML page. Instead we will put this information in the jQuery script. While I could have included this in the fragment, doing it this way actually makes coding the tooltip easier:
As well as being able to change the class associated with an element or a set of elements on a screen, jQuery also allows you to fire events. You might want to do this, for example, if you want to simulate the clicking of a button. Of course, if you are going to fire an event, you’ll probably need some sort of event listener setup to handle that. We will address firing events first since it has the least amount of code needed. All you need to do is select the element or elements using the selectors we’ve already discussed and then call the method trigger(‘eventname’). So, to click a button, your code might look something like this: