OK... particularly fugly code... wow.
I'm about 2/3 of the way refactoring this huge beast of an application. I'm pulling SQL out of the code behind and putting it into the database layer. I'm using StringBuilder to avoid the loooooong chained together strings they used. Anything possible, I'm pushing to Oracle.
But some of the worst is the client-side code. Multiple times I've found 60 or 80 non-breakable spaces to move something to the right! Data entry forms with 6 rows of data to fill out, and when I try to fix up the UX, things blow up and I find a label that's only in there to space something out... sigh.
I've mentioned some of this before, but today's challenge is a 6-row form that's not-exactly orthogonal in it's layout. Of course I didn't really notice that until I started working on it. The reason it's not lined up both horizontally and vertically is because it's a table cell of a set width, and all 6 display rows are just non-breakable space-separated elements that wrap and make up the display ... seriously!
I missed out on classic ASP, and came in on the tail-end of .NET 1.1, but I'm pretty sure this wouldn't be advisable in either of those, and it's a total Pain in the A$$ to straighten out.
Just thought I'd share ... at least I know what I'm going to be doing all morning!