• @fuelfrog 504.9 3.889 11.003 #

Bid now at: http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=190234347713

This phone served me well for about 8 months (when I upgraded to an AT&T Tilt). It saved our butts when my boss and I were on a business trip in Texas and we got lost — this little beaut not only found us, but told us how to get from where we were to where we were going (GPS navigation software not included).

Windows Mobile "Pocket PC"

First and foremost it’s a Windows Mobile Smartphone running Windows Mobile 5. It’s got a 520MHz PXA270 processor 64MB of RAM (50.45 available) and 128MB ROM (that means it’s plenty fast and has a bunch of room to install your own Windows Mobile applications).

If 128MB isn’t enough storage space for you, it’s got a full-size SD card slot in it, so you can upgrade your storage to 2GB just by popping in a card (and since it’s standard SD, they’re cheap — if you’ve only got MicroSD cards (like me) I’ll even throw in a MicroSD to Full-Size SD adaptor free!). NOTE: SDHC isn’t supported, just standard SD.

GPS Receiver

Its built-in GPS receiver has been tested to work with CoPilot, Google Maps, Windows Live Maps, and Tom Tom (software not included, but the Windows Live and Google apps are free downloads).

Cell Phone

In addition to being a killed PDA and GPS unit, this little guy is also a tri-band GSM phone, unlocked and ready to work on virtually any GSM network in the world (T-Mobile and Cingular in the USA work great with this phone). Just pop in your SIM and you’re making phone calls.

Camera

Comes equipped with a 1.3 megapixel camera.

Mobile Internet

With it’s GPRS radio and a data plan from your cell-phone provider this phone can get and send your email from an Exchange server, or over POP/SMTP. It’s not as fast as EDGE or 3G speeds, but it gets the job done quite nicely. If you’re worried about speeds, just set it up to get/send your email every 5 minutes, and set up and RSS reader (not included) to pull your RSS feeds in every couple hours.

Condition

This phone is used, it has a few minor cosmetic blemishes, but functions great and looks really stylish (I get asked if it’s an iPhone all the time).
This phone originally sold for over $500, you’re bidding on it starting at $99+shipping. It’s a killer deal because (1) it’s used, (2) being sold as-is, and (3) Windows Moble 6.1 is out (this is Windows Mobile 5).

What you get:

• The phone/PDA (including its 1320mAh battery),
• a USB cable (doubles as the charging cable),
• a MicroSD to standard SD adapter

Specifications from the Manufacturer

Specifications can be found at http://www.mio-tech.be/en/gps-navigation-device-Mio-A701-specifications.htm, detailed pictures are available there as well.

What are you waiting for?

You know you want it… and at this price you can’t afford to pass it up! BID NOW!

• it’s official: Lifetime Products is outsourcing Helpdesk to China… it’s still our company and only after hours… but… #
• @overheard “how are we going to deal with the ‘one more thing’ syndrome?” #
• @overheard “if the end user is not really a human person…” #

CSS Box Model

Let’s face it, if you’re not familiar with the CSS Box Model, you’re probably not a web developer (or, if you are a Developer, you need some remedial education). The CSS Box Model is one of the most misunderstood patterns in CSS.

According to the World Wide Web Consortium (W3C):

The CSS box model describes the rectangular boxes that are generated for elements in the document tree and laid out according to the visual formatting model. The page box is a special kind of box that is described in detail in the section on paged media.

In plain language that means the CSS box model specifies the way a web developer should place a box on a web page.

“But that’s not hard to do, you just drop a DIV on the page and you’re done, right?”

That’s the way to get you started, sure, but there are some things you need to keep in mind, each block-element:

• has an over-all width(measured differently in different web browsers, just to make your life more interesting).
• can have a border on each side (optional)
• can have padding (on each side) between the content and the border (optional)
• can have margin (on each side) between the border and the element that it sits next to (optional)

The following diagram from the W3C shows how these components relate to each other and the terminology used to refer to pieces of margin, border, and padding:

Here’s a tip for you that will save you countless hours of headache

When using DIV’s to layout a page (see diagram), don’t forget to use display:inline; to work-around MSIE’s annoying “double margin” issue. You can thank Anthony Short for this tip.

What you want: What you get in MSIE:

Another tip for content layout with floated DIVs

When you want two DIVs to sit next to each other (like above), under some circumstances you’ll end up with one of the two DIVs being forced below the other. To correct this, first make sure you’re using the display:inline; attribute (see above) to get rid of MSIE’s double-margin issue, the add overflow:hidden; to both DIVs. This will hide any content in the DIV that is too wide to fit and would mess with the layout. This is especially helpful if you’re pulling content in dynamically.

Don’t forget to break

After all is said and done, if you’re using floating DIVs for content layout if you want anything under the floated DIVs don’t forget to add clear:both; to that block-level element to tell it to fall under the floated DIVs.

You can thank me later.

I’m a fan of using ASP.NET’s web.sitemap feature, but I’m less impressed with the level of control that you have (rather, you DON’T have) over the menu controls that consume the web.sitemap datasource (http://www.BuyLifetime.com uses three menu controls that consume the same sitemap from MS Commerce Server 2007, which look 90% like what we want them to).

Wouldn’t it be nice if you could just make it into a navigation list? We all know (or should know by now) that a navigation list (whether ordered or unordered) should be just that, a hierarchical (“nested”) list of pages in your site.

To do this we can use a Repeater control and use the web.sitemap datasource as the contents.

It’s easy enough to make a one-level-deep list, and not too much more difficult to do a two-level-deep list.

   1: <asp:Repeater visible="false" runat="server" ID="siteMapAsBulletedList" DataSourceID="SiteMapDataSource1">

   2:     <HeaderTemplate><ul></HeaderTemplate>

   3:     <ItemTemplate>

   4:         <li>

   5:             <asp:HyperLink ID="HyperLink1" runat="server" NavigateUrl=‘<%# Eval("Url") %>’ Text=‘<%# Eval("Title") %>’ />

   6:             <asp:Repeater runat="server" id="SecondLevel" DataSource=‘<%# ((SiteMapNode) Container.DataItem).ChildNodes %>’>

   7:                 <HeaderTemplate><ul></HeaderTemplate>

   8:                 <ItemTemplate>

   9:                     <li><asp:HyperLink ID="HyperLink1" runat="server" NavigateUrl=‘<%# Eval("Url") %>’ Text=‘<%# Eval("Title") %>’></asp:HyperLink></li>

  10:                 </ItemTemplate>

  11:                 <FooterTemplate></ul></FooterTemplate>

  12:             </asp:Repeater>    

  13:         </li>

  14:     </ItemTemplate>

  15:     <FooterTemplate></ul></FooterTemplate>

  16: </asp:Repeater>