Marv\'s Blog

Annoyed at the thing I have to get taught at University.

November 28, 2005
Leave a Comment

Aside from restructuring into semantic (X)HTML, this post appears as it does in the post I made on the Uni message board. Damn WebCT sucks.

obsolete/incorrect info in session 10 power point presentation

I am annoyed and frustrated about being taught obsolete and semantically incorrect techniques.

  1. Frames generally create accessibility, as well as usability problems; they should be avoided, and if scrolling content is needed, div tags with the overflow specified in CSS will fix that problem.
  2. Styles should be applied to tables with CSS, not (X)HTML attributes.
  3. Internet Explorer uses an invalid DOM.
  4. div and span tags aren’t so much layers as blank elements intended to be styled by the designer or end user. span tags can be made into block level elements and div tags can be made into inline elements, as can pretty much every other (X)HTML element.
  5. Since IE uses an invalid DOM, code should be written for everything else (the stuff thats standard based) first, and IE second. Or just Firefox, as IE is a big obsolete waste of time.
  6. Layers and Tables do not reduce the accesibility of web pages to visualy impaired users. It is the incompetent implementation of layers and tables that makes them inaccessible.
  7. Tables should not be used to control layout of a document. That’s a waste of code and creates accessibility problems, unless you know what you’re doing. Then it’s just a waste of code.
  8. Nested layers are good, nested tables are really, really bad.
  9. CSS permits user defined formating of any XML object.
  10. CSS can be applied to ANY (X)HTML object
  11. CSS files do not have to be stored with a .CSS extension. Web browsers couldn’t care less what it’s called as long as it is written in CSS. Preferably valid. Preferably without IE’s invalid bloat.
  12. Fixed pixel fonts should never be used. They are inaccesible, and should only ever ever be used if the design of a page requires it, in which case, alternate stylesheets should be provided. Many websites do this out of courtesy for their users. IE’s text zoom facilities suck. That is a syntacticalyl correct statement.
  13. CSS is not a dynamic language, it does not update all pages it is associated with, the changes are only reflected once the relevant pages have been refreshed in the browser.
  14. Most of Macromedia’s DHTML implementations create invalid javascript code.

Blogger Migration pt8

October 9, 2005
3 Comments

Testing an idea for easier migration from BlogSpot to WordPress.com.

Putting all these thoughts together, I am about to attempt something a bit iffy. I am going to edit my BlogSpot template so it cuts out all the miscelaneous HTML crap, and leaves the pure post code. I will then download my posts to my computer, making it easier for me to migrate- a simple highlight, copy & paste from Notepad++ straight into .

No messing about with back and forwards buttons. No waiting for page loads. No triple message boxes on each back button press. No warnings about POST data. A step in the process will be simplified. Migration from BlogSpot to WordPress.com will no longer require access to BlogSpot.

I have an idea of how I’m going to make it work, but I’m not sure if it will.


Blogger Migration pt5

September 28, 2005
Leave a Comment

Migration progress.

After those server time-out problems appeared to have gone away, I’ve managed to get all my posts up to July migrated. Still crap loads to go though.

Delays in migration progress.

The fairly large amount of posts was always going to be a problem, but I keep forgetting to adjust header values to fit with the template I’m using here. Can’t wait for the XHTML 2 all-purpose header tag. Early posts used an <h1> tag in the post below an <h3> tag in published output and later posts used a more semantic <h4>. What was an <h4> is now an <h3>.

Let’s not forget ISP screw ups and intermittent service outages.

My problem with WordPress.com’s HTML filtering system.

The little ‘security’ feature they have in place means I can’t use <dfn> tags for my potentiallyOffensive coding experiment (you’ll read more about potentiallyOffensive experiment when I get the posts migrated), and also cause problem with my class=”hidden” and class=”offscreen” coding experiments.

potentiallyOffensive.

It’s a little experiment relating to censorship, freedom of speech and freedom of choice.

class=”hidden” & class=”offscreen”.

Personally I hate seeing full stops at the end of lists and header tags- <dt> and <th> included. The reason I put them there in the first place is back when I was working for Connexions, I was experimenting with some screen reader software, and the dumb piece of crap didn’t put a pause after each header or <li> tag in the navigation list. So I had to put full stops in the <li> tags, but hide them from view. Thus class=”hidden” was born (yes I realise other people may use it, but that was when I first used it). More recently I’ve needed to have some full stops (or other text) be hidden in @media screen, projection etc, and apparent in @media print, aural, braille, embossed, and others hidden in just @media screen, print, projection, handheld etc. Thus class=”offscreen” was born (early posts in Blogspot used class=”hidden”, later ones used class=”offscreen”).

However I have noticed that the code disappeared between manual coding (I don’t like WYSIWYG editors) and publishing.


Yet more template fiddling

August 2, 2005
Leave a Comment

Nothing Major (yet again).

Added a profile photo and a little description of the blog.

I’ll be adding a new syndication feed to the list once I’ve got some problems ironed out with the company that provides the service.


Posted in Blogspot, HTML
    June 2017
    M T W T F S S
    « Apr    
     1234
    567891011
    12131415161718
    19202122232425
    2627282930  

    The Buttons

    • Get Firefox!
    • Get Thunderbird!
    • No Software Patents
    • Questionable Content
    • Wapsi Square
    • XFN Friendly

    My del.icio.us feed

    RSS Unknown Feed

    • An error has occurred; the feed is probably down. Try again later.

    RSS Unknown Feed

    • An error has occurred; the feed is probably down. Try again later.

    RSS Unknown Feed

    • An error has occurred; the feed is probably down. Try again later.

    RSS Unknown Feed

    • An error has occurred; the feed is probably down. Try again later.