Posted on November 26th, 2008%
I just stumbled upon this announcement from the Baseball Mogul Online forums:
This page is to notify all Baseball Mogul Online users that we will be discontinuing the service as of December 1, 2008.
Why?
There are three main reasons:
#1 -The system is not profitable to operate for us. Even when it was at its peak of usership, it did not bring in enough money to support further growth and improvements.
#2 – We no longer have the staff needed to operate the system.
#3 – The machines and bandwidth that the system runs on were designed for a much larger load than we currently use. To economize, we will be switching services and bandwidth, and the new equipment will not support Mogul Online.
Sincerely,
Dee and Clay Dreslough
Sports Mogul Inc.
Well how about that. I’m as sorry as anyone to see a solid game go away, but there’s good news to all Baseball Mogul Online fans — there’s an alternative that is not going away, and . . .
→ Read More: Baseball Mogul Online is shutting down — but CSFBL isn’t, so why not check it out?
Posted on November 17th, 2008%
A client I’ve been working with is looking for a front-end ASP.Net developer to work on-site for them in their New York City (midtown) office.
The right candidate should be able to:
develop a complex ASP.Net solution using WebForms;
create web markup (HTML/CSS) from Photoshop mockups;
use ASP.Net Ajax, jQuery, or other client-side solutions, and know when to use what;
write efficient front-end code that is tested and works well across a wide range of browsers;
come up with user interface solutions (i.e. help define the client side of the business requirements);
be able to write code-behind and be able to read, understand, and enhance existing business logic code.
If you or someone you know has the right stuff, send me an email with your resume and I’ll pass it along.
. . .
→ Read More: Looking for a good ASP.Net front-end developer in New York City
Posted on November 14th, 2008%
As part of the rewrite of the ASP.Net Control Adapters (see the Google project at http://code.google.com/p/aspnetcontroladapters), I started working on a new Menu adapter. It’s got a long way to go — and you can help me get there!
The best way to engineer proper adapted menu markup is to visualize how the non-adapted Menu generates markup (and, in a sense, reverse-engineer it). With that, here’s what you can do to help.
Send me a copy of the markup and generated code for your non-adapted Menu controls!
In other words, here’s what I can use.
The exact markup of your Menu tag from your ASPX page.
Any codebehind that manipulates the properties of your Menu tag (i.e. changes to what you declared in your ASPX page).
Your sitemap file (if used), or any details that you can give about the site map used to generate your menu.
The HTML generated in the web page by all of the above — using default (non-CSS-adapted) markup.
The goal is to . . .
→ Read More: Want a better Menu adapter? Send me your menus!
Posted on November 12th, 2008%
A project I’ve been working on makes frequent use of the ASP.Net GridView. However, as many people know, the GridView has one glaring issue: It wraps your <EmptyDataTemplate> in an HTML table — something that I don’t want, for two reasons:
My empty data template does not consist of tabular data.
My stylesheet has a default style for tables — a style that I don’t want applied to my empty data template.
One solution is to use the CSS Friendly Adapters for ASP.Net, which potentially solves both prolems, but that will bring in potential breaking changes to my GridView controls. I don’t have time for that (yet).
The solution I came up with is to do two things:
Create a new CSS class that removes table formatting (borders, backgrounds, padding, margins, etc.). This class will be applied to the GridView only when it has no data.
Add a line of code in the OnPreRender() method for each web page or control that . . .
→ Read More: Cleaning up the GridView’s EmptyDataTemplate (damn those tables!)
Posted on November 11th, 2008%
Hope was a pragmatic young lady who knew the importance of planning ahead. On her 18th birthday, she decided to start saving for retirement. Being a college student, she didn’t have much money to save, but she wanted to start with something.
A local bank had a plan that was perfect for Hope. She would get a fairly moderate 5.1% interest rate on her savings, provided she follow one rule: she must save some money every day, even if it was as little as one cent.
Hope started off saving five cents per day. She followed this plan until her 21st birthday, when she increased her savings to ten cents per day.
By her 25th birthday, she was enjoying a few years of full-time work, and raised her daily savings to 25 cents per day.
Turning 29, with her career taking shape, she increased her daily savings to 50 cents per day, and continued to save that amount each day until her 67th birthday.
On her 67th birthday, Hope went to the bank to see how she had done. Over the years, she had saved just over $7,500 — yet never took more than 50 cents out of her pocket. In her retirement account was much more than that: over $25,000 — more than three times what she had saved.
Sure, no one can retire on $25,000, but everyone can save as little as 50 cents per day. What if Hope was more aggressive in her savings? What if she had saved $1 every day for her entire adult life in the same retirement account (with its 5.1% interest)? . . . → Read More: Hope and Change: A Story
|
|
