Showing posts with label Opera. Show all posts
Showing posts with label Opera. Show all posts

Monday, 10 January 2011

Genealogy websites 2011

One returning from my Christmas break I started to think about a suitable blog with which to start the New Year. Initially I thought about a review of 2010, but then we've done that and got the T-shirt! So, how about 2011, and what will it bring? Since my main interests are genealogy and creating websites, the exciting happenings in website development, and the possible effects on our websites is an obvious. But first, I would like you to look at The Wilderness Years to do so you will need lots of memory and preferably the Google Chrome Browser, if you haven't got it, it is worthwhile downloading for this site alone. It will just about run on the latest Firefox (but not well), and I could not get it to run at all on the latest Beta version of IE9. When asked for your town, I would suggest that you enter a large city, or at least a place where Google Earth will have lots of photos.

Now that site is based on the new HTML5 coding, and I am not suggesting that it will have much effect on research sites such as Ancestry, or Findmypast, but I am certain that it will be used by people, like myself, who write their own websites. It will also be used in conjunction with another new language, CSS3, which is used to code the positioning and layout of the pages.

Will this affect the User?

Yes, it will! Already the latest browsers are starting to incorporate the functionality which they need in order to read HTML5 and CSS3. Chrome is probably the best at present but it is steadily being introduced into Firefox, Opera, IE9 and other major browsers. The figures below are taken from visitors to my own website.
1) Browsers used:
As might be expected IE is at the top of the list whilst at the bottom are the mobile phone browsers. In general, it is fair to say that non-IE users tend to be very dedicated in updating their browsers to the latest version, and IE users less so as the table below shows:

2) IE Users:
At last some three-quarters are now using IE8 but there is still over 5% using IE6 or earlier. Those users are going to have problems because only the latest browser will be able to read the new codings, and their problem is that little will be done to get the sites to display properly when using them. Even IE7 and IE8 users will not get the full benefit of the new technology, although the probability is that the sites will degrade gracefully for these users.

IE users with the XP operating system also have a big problem since it would seem that IE9 will only be available for Vista and Win7 operating systems - a change to Chrome could be their best option.

Website Generators

To generate my Pedigree web pages I use the HTML generator included in the Legacy Family Tree program. I still consider this to be the best program around for these types of web pages, but it is now getting old and tired as it is written in very basic HTML. It has received a boost with the publishing of a program from LTools which enables the conversion to CSS/HTML, but, in my view, will shortly need to be rewritten - this comment also applies to most similar programs.

The Future

This year promises to be one of the most exciting in website development for many years but for the new techniques to achieve their potential depends not only on the website developers but also relies on the users to upgrade their browsers and the software manufacturers to improve their generators - before we reinvent the wheel!!

Disclosure

The author is a volunteer beta tester for Legacy Family Tree.

© Ron Ferguson 2011

Thursday, 11 March 2010

Genealogy Website: The Nav Bars

 A web page can be considered as being built on layers, the first being the base, or blank page, usually white but it can be given a colour. For my new site I have put another, slightly smaller, background layer on top, followed by the data and images. In my case I consider the nav bars as being a new layer since the drop-downs must sit on top of any data and images. One point about images, IE6, and earlier, do not recognise the ".png" transparency. Google will find many scripts to cure this, one of which is to be found here.

To date, I have used javascript for my drop-down menus, however it is now possible to write these in CSS. Unfortunately, because to do this the latest CSS standard is used there are problems with older browsers, in particular with IE6. The image on the right is a sneak preview of a section of my new index page, and as can be seen the drop-down sits on top.

To make them display on top of images is easy, simply use the "z-index" CSS style. However for other image forms it can be quite tricky. For Flash, within the "Object" tag the line < param name="wmode" value="transparent" > needs to be included. IFrames present a different problem, and to date, despite having tested varying "solutions", I have yet to find a way of stopping the nav bars from going behind the image for IE7 and earlier. Still, I've three weeks left!

Now, the above are the easy problems, again it is IE6 which causes the real head ache, because CSS drop-down menus simply do not work! To the rescue comes Suckerfish and the Sons of Suckerfish, which for my purposes I had to modify even further.

In my first Blog in this series I mentioned that I wished to eliminate/minimise the use of javascript, and for the navigation this has largely been achieved. As you will see to get them to work in the early versions of IE, and I no longer bother writing for IE5.5 and earlier, javascript has been a necessity, this I feel is a fair compromise. If those using IE6 do not have javascript enabled the navigation will not work, but it is still possible for visitors to get round the site albeit with more difficulty. (If you are viewing this using IE6, please upgrade, especially as you can now see our headaches!)

My final point concerns testing, I use Firefox for most of my development work and test in IE8, Opera, Safari, Chrome, Sea Monkey and Bing, these I have on my PC. As I do not have a Mac. I rather hope that if it works with Safari it will be OK (not really satisfactory, but there we go!). So how do I test in earlier versions of IE? A nice free piece of kit called IE Tester enables this to be acheived.; although still in Alpha version, and not every bit works fully, it does do the job, and for me is a life saver.

© Ron Ferguson 2010