Loading user information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading user information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements


Jonathan Carter LostIn​Tangent
  • New Social Networking Website

    ddewbofh wrote:
    LostInTangent wrote:People on here actually use Myspace?

    Nope, everyone here uses sitespaces instead.

    You live in the epicenter of amazing music by the way. I'm actually hoping to make it to Sweden this summer.

  • New Social Networking Website

    People on here actually use Myspace? Perplexed

  • Looking for feedback on site design

    stevo_ wrote:
    LostInTangent wrote:

    I understand accessability, without sounding like an arse, I've been doing web design for long enough.

    Long enough to know that pixel measurements don't cause problems with the important factor of the website, the text.

    At least to the degree that you can expect the design to become somewhat less 'elegant', but when you take into consideration that em fluidity is often just as in-elegant. Then I don't see the point in working in complete em.

    I never said I would work in complete em either, and in fact I don't. But your response could have been interpreted by some as saying that ems are completely useless and that isn't true at all.

    Seeing as how you've been doing web design "long enough" (not sure the exact timespan of that), you should have been able to provide a little more helpful advice than just state your frustration with ems.

  • Looking for feedback on site design

    stevo_ wrote:
    em is over used. Since when is a single design fluid to that degree?

    em inheritance is also pretty frustrating sometimes. I've actually moved away from using it more recently.

    It's not really so much an issue of fluidity as it is accessibility. Until all mainstream browsers (or for that matter client-installed browsers) fully support resizing of pixel based designs, ems are the obvious choice for allowing users to resize their font and enjoy the same browsing experience.

    Even with the advent of pixel resizing, its still considered a best practice to employ the "absolute-relative" style in which your containers are absolutely sized, using pixels for example, then its children are sized relatively using ems.

    As far as the site goes, it looks good, nice work CyberGeek. I only noticed a few things (purely code related):

    1) You're using an <img> element for your header logo, whereas I prefer image replacement, for accessibility and SEO benefits, ect.

    2) Like w3bbo mentioned, you're definitely overusing classes whereas ids are more appropriate.

    3) In your headerBox, you're marking every <a> element with the "button" class, when you could easily just target all children <a> elements inside of headerBox and save yourself the repeated class declaration.

    4) You're using the <em> tag for purely presentational purposes also. The text its wrapping certainly isn't meant to be emphasized.

    5) The gallery is using a <table>.

    6) In the post explaining how to use BBCode, you're using <br> elements to seperate the different options, when in reality, a <ul> would be better suited, since it's a list of options, and you could style the list to  look the way you want it without using breaks, which are almost never semantically correct (the exception being poems, addresses, ect.)

  • Can I use a relation to filter instead of doing a new join select query?

    You would just set them to the names of the columns that contain the name and value data.

  • Custom Control DLL Error

    I've never been able to get it to work and as far as I know you can't in ASP.NET 2.0


  • Petzold's Programmer Pointer: XAML (Rhymes with Camel)

    TommyCarlier wrote:
    Should every website be flashy and trendy and Web 2.0-y? I think not. And I think we should appreciate the fact he's using pure XML for his blog (not even XHTML).

    Who's talking about his blog? I was commenting on his home page, which is blessed with font elements and table-based design.

    Like I said before, I respect Petzold extremely, and I look forward to meeting him at Dev Connections next month, but he certainly could spend 10 minutes to clean up the code of his home page Wink

  • Show us the Code

    That guy needs to spend more time learning how to do respectable web development/design and less time challenging Microsoft.

  • Data Binding Business Objects

    JParrish wrote:
    One of the reasons I like to use business entities over a dataset is that with the dataset you are still working with the data in a tabular fashion, which to me is less intuitive than an object hierarchy.

    If you're using a strongly typed DataSet configured with relations connecting all DataTables, the intuitiveness of the data is pretty comparable to a custom business object.

    If you had two business objects: Customer and Order, you might retreive the orders for a customer using the following code:

    Orders orders = customer.Orders;

    Whereas the same functionality, using a strongly typed DataSet, might look like this:

    CustomersDataSet.OrderRow[] orderRows = customerRow.GetOrderRows();

    Both scenarios are done with the same number of lines, both can be enumerated and accessed with strongly-typed properites, and both are arguably intuitive in their own ways.

    The difference is that it took two seconds to create the strongly typed DataSet and the same coding style can be used across all instances of DataSets regardless what they represent. With DataSets, you can easily make changes to them, and send them back to your DAL which in turn easily updates the changes using a DataAdapter. With a business object, you'd have to develop that logic yourself, which seems pointless, and depending on where logic is placed, can be rather nasty (I've seen some rediculous code done by developers in this area).

    JParrish wrote:

    I also think that when properly implemented, a business entity can be more performant. For instance, a business object that represents a "customer" may have demographics, a collection of recent transactions made by the customer, etc. Using lazy load techniques the object is then optimized to pull only the necessary data for any given usage, and does so intrinsicly.

    All that business logic you just mentioned is well-suited for an actual business logic layer, not the business object itself.

    I use DataSets strictly as containers of data that are passed between layers and controls. Any events, methods, logic, ect that I need to perform is done externally to the DataSet.

    I think the biggest factor that decides which route you take is the underlying architecture your applications use. In my case, DataSets make perfect sense. I like communicating with my business logic layer and letting it retreive the data for me as opposed to calling a method directly on the business object itself, so I develop everything into the respective layers, and leave the DataSets alone, existing only for the purpose of containing the data.

  • XAML Replaces XHTML?


    Well played raymond