Technology Tales

One of the nice things about eBooks is the saving that you can make on buying one instead of the dead tree edition. And if you get one from Apress, it is the full article that you get, and they keep it available so that you can download another version if you need it. You can also print the thing off if you want too, yet a laser printer producing double-sided prints is an asset if you don’t want your space invaded by a hoard of lever arch binders. Having a copious supply of inexpensive toner helps too, as does cheap paper. Otherwise, you could spend your savings on printing the thing yourself.

The ever pervasive Safari does things a little differently from the likes of Apress. Mind you, the emphasis there is on the library aspect of the operation and not eBook selling. The result is that you can only ever download chapters, so no index or overall table of contents. You still can buy all the chapters for a particular book, though some publishers don’t seem to allow this for some reason, but finding anything in there after you have had a read becomes an issue, especially when it’s the hard copy that you are using. Take yesterday, for instance, when trying to relocate the formatting parameters for the UNIX date function. Though I eventually found them in the chapters of UNIX in a Nutshell that I have downloaded and printed off, I spent rather longer looking in Learning the Korn Shell than I should have done. Even if I know that you can search in the PDF’s themselves, that is more laborious when there are a number of files to search rather than just the one. I suppose that the likes of O’Reilly prefers you to buy paper copies of its books for more extensive use, and they have a point, even if having the electronic version all in one file does make life so much easier.

Having owned a licence of ZoneAlarm Security Suite 6, I was wondering if I would get a pop-up inviting me to upgrade, free gratis as I have a subscription, to the latest version. In the middle of my Office 2007 installation activities, the notification duly turned up to prompt me to download and install the update to version 7.

The first change you will notice is in the branding, ZoneAlarm is now owned by Check Point Software Technologies, but the real reason for my interest is my hearing that Kaspersky antivirus technology is now part of the package. In addition, learning capabilities have also been added so that you don’t get annoyed by the thing asking you if it is alright for a certain application to do something or other that seems vaguely out of order, all the time. This has been part of Norton Internet Security for a while and is certainly an asset; Windows Vista’s User Access Control feature would do well to implement some of this learning, given what I have heard of its activities. And ZoneAlarm 6 was prone to nag you a lot as well, at least it did for me.

The installation went well for me, apart from the non-activation of the antivirus functionality. This took an update and a reboot to sort out, leaving me to think that it might have emanated from the changeover to British Summer Time that took place last weekend. I shall be keeping an eye out for what happens when the changeover to Winter time takes place (don’t worry, I fully plan to enjoy the intervening time; I have more than learned to enjoy each season for its delights). Having a time changeover like this knock out your antivirus software is far from ideal. Other than that, everything is working fine, especially as the firewall is staying silent as it continues to learn.

Since today was to have been the last day of my Office 2007 trial, I headed over to Amazon.co.uk at the start of the week to bag both Office Home and Student 2007 and Outlook 2007. Both arrived yesterday, so I set to ridding my system of all things Office before adding the new software. So the 2007 trial had to go, as did Office XP and any reference to Office 97; Office XP was an upgrade. From this, you might think that I am on a five-year upgrade cycle for Office, and it certainly does appear that way though Office 95 was the first version that I had on a PC; it came with my then more than acceptable Dell Dimension XPS133 (Pentium 133, 16MB RAM, 1.6GB hard drive… it all looks so historical now).

Returning to the present, the 2007 installations went well and all was well with my system. Curiously, Microsoft seems to label the components of Office Home and Student “non-commercial use”. While I accept that the licence is that way inclined, they could be a little more subtle than to go emblazoning the application title bars with the said wording. Nevertheless, I suppose that it is a minor irritation when you consider that you are allowed a three machine licence for what are the full versions of Word, Excel, PowerPoint and OneNote. It must be the presence of OpenOffice on the scene that is inducing such benevolence.

Curiously, Outlook isn’t included in Office Home and Student, hence my getting the full version of the application separately. That means that there is no nefarious wording about the purpose for which it should be used. While on the subject of Outlook, my purge of previous Office versions thankfully didn’t rid my system of the PST files that I was using with Outlook 2007’s predecessors. In fact, the new version just picked up where its predecessors had left off without any further ado. As I have been getting used to the new interface, changed from Outlook 2002 but not as dramatically as the likes of Word, Excel or PowerPoint, there is a certain amount of continuation from what has gone before in any case. The three-pane window is new to me as I never encountered Outlook 2003 and that may explain why it took a little time to find a few things. An example is that all calenders appear in the same place when I had expected the association between calenders and their PST files to be retained. Nevertheless, it is not at all a bad way to do things, but it does throw you when you first encounter it. Its RSS feed reader is a nice touch, as are the translucent pop-ups that appear when a new message arrives; that tells you the title and the sender so you can decide whether to read it without so much as having to look at it and interrupt what you are doing.

In a nutshell, all seems well with Office 2007 on my machine, and I am set up to go forward without the headache of an upgrade cycle since I have recommenced from a clean slate. Though I have heard of some problems with Office 2007 on Windows Vista, I am running Windows XP and I have had no problems so far. In fact, I plan to sit out the Vista saga for a while to see how things develop and, who knows, I might even not bother with Vista at all and go for Vienna, its replacement due in 2009/2010, since XP support is to continue for a good while yet.

At work, we still use Windows 2000 on our desktop and laptop PC’s. This may (or may not) surprise you, but the XP upgrade seems to have been thought a premature move, only for Vista to turn up later than might have been expected. Now that Microsoft is winding down support for Windows 2000, thoughts have started to turn to a Vista upgrade, but the realisation soon dawned that a move to Vista was a major one, and it now looks as if we will be on Windows 2000 for a little while yet, until 2008 at least.

I, too, have Windows 2000 lurking around at home as a testing platform, not a work copy I hasten to add, and software vendors increasingly are not supporting the operating system any more. Symantec is one of these, with the 2006 versions of its products being the last ones to support Windows 2000. Initially, I was left with the impression that Kaspersky was the same, but this does not seem to be the case. While the open-source community can continue their supply of productivity applications such as OpenOffice, the GIMP and so on, it is the security side that is of most concern as regards the future of Windows 2000. That said, its successors are not the prime targets for cracking, but shared code could mean that it falls foul of the same exploits.

I have yet to notice it with the hardware that I am using, but hardware advances may yet put paid to Windows 2000 like they did to members of the Windows 9x line, especially when you consider that the operating system dates from 1999. Then again, you may find that you don’t need the latest hardware, so this might not affect you. This is not all that unreasonable given that the pace of technological progress is less frenzied these days than it was in the nineties, when Windows 95 was more or less out of date by the turn of the millennium. Having the gold OEM version of Windows 95 as the basis for a Windows 9x upgrade treadmill meant that my move into the world of NT-based operating systems was a clean break with a full version of my new operating system and not its upgrade edition.

Nevertheless, there remains a feeling that Windows 2000 is being cut off prematurely and that it could last a while longer with a bit of support, even if there is a feel of the late nineties about the thing. After all, Windows 2000 probably still supports a lot of what people want to do and without the Big Brother tendencies of Vista too.

Last night, I sat through part of Adobe’s CS3 launch and must admit that I came away intrigued. Products from the Macromedia stable have been very much brought under the Adobe umbrella and progressed to boot. One of these that attracts my interest in Dreamweaver and Adobe is promoting its AJAX capabilities (using the Spry library), its browser compatibility checking facility and integration with Photoshop, among other things. Dreamweaver’s CSS support also gets taken forward. In addition, Dreamweaver can now integrate with Adobe Bridge and Adobe Device Central. The latter allows you to preview how your site might look on a plethora of WAP-enabled mobile phones while the latter, unless I have been missing something, seems to have become a media manager supporting all of CS3 and not just Photoshop.

Speaking of Photoshop, this now gets such new features as smart filters, I think of these as adjustment layers for things like sharpening, monochrome conversion and much more. Raw image processing now has a non-destructive element with Photoshop Lightroom being touted as a companion for the main Photoshop. Speaking of new additions to the Photoshop family, there is a new Extended edition for those working with digital imaging with a 3D aspect and this is targeted at scientists, engineers, medical professionals and others. It appears that data analysis and interpretation is becoming part of the Photoshop remit now as well.

Dreamweaver and Photoshop are the components of the suite in which I have most interest, while I also note that the Contribute editor now has blogging capabilities; it would be interesting to see how these work, especially given Word 2007’s support for blogging tools like WordPress and Blogger. Another member of note is Version Cue, adding version control to the mix and making CS3 more like a group of platforms than collections of applications.

Unsurprisingly, the changes are rung out for the rest of the suite with integration being a major theme and this very much encompasses Flash too. The sight of an image selection being copied straight into Dreamweaver was wondrous in its own way and the rendering of Photoshop files into 3D images was also something to behold. The latter was used to demonstrate the optimisations that have been added for the Mac platform, a major selling point, apparently.

I suppose that the outstanding question is this: do I buy into all of this? It’s a good question because the computer enthusiast seems to be getting something of a sidelining lately. And that seems to be the impression left by Windows Vista, it gives the appearance that Microsoft is trying to be system administrator to the world. There is no doubt but CS3 is very grown up now and centred around work flows and processes. These have always been professional tools, with the present level of sophistication and pricing* very much reflecting this. That said, enthusiasts like me have been known to use them too, at least for learning purposes. The latter point may yet cause me to get my hands on Photoshop CS3 with its powerful tools for digital imaging, while Dreamweaver is another story. Given it doesn’t fit what how I work now, this is an upgrade that I may give a miss, as impressive as it looks. For a learning experience, I might download a demo, but that would a separate matter from updating my web presence. This time next month may tell a tale…

*Pricing remains the bugbear for the U.K. market that it always has been. At the present exchange rates, we should be getting a much better deal on Adobe products than we do. For instance, Amazon.com has the Web Premium CS3 suite from Macromedia Studio 8 priced at $493.99 while it is £513.99 on Amazon.co.uk. Using the exchange rate current as I write this, £1 buying $1.96605, the U.K. price is a whopping $1010.53 in U.S. terms. To me, this looks like price gouging and Microsoft has been slated for this too. Thus, I wonder what will be said to Adobe on this one.

Having been on a web-building journey from Geocities to having a website with my own domain hosted by Fasthosts, it should come as no surprise that I have encountered a number of tools and technologies over this time and that my choices and knowledge have evolved too. I’ll muse over the technologies first before going on to the tools that I use.

Technologies

XHTML

When I started building websites, it was not after HTML 4 got released, and I devoured most if not all of Elizabeth Castro’s Peachpit Visual Quickstart guide to the language within a weekend. Having previously used fairly primitive WYSIWYG tools like Netscape Composer and Claris Home Page, it was an empowering experience and the first edition (it is now on its third) of Jennifer Niederst Robbins’ Web Design in a Nutshell took things much further, becoming something of a bible for a number of years.

When it first appeared, XHTML 1.0 wasn’t a major change from HTML 4, but its stricter more XML-compliant syntax was meant to point the way to the future and semantic markup was at its heart at least as much as it was for HTML 4. XHTML 2.0 is on the horizon and after the modular approach of XHTML 1.1 (which I have never used), it will be interesting to see how it develops. Nevertheless, there is a surprising development in that some people are musing over the idea of having an HTML 5. Let’s hope that the (X)HTML apple cart doesn’t get completely overturned after some years of relative stability. I still bear scars from the browser wars raging in the 1990’s and don’t want to see standards wars supplanting the relative peace that we have now. That said, I don’t mind peaceful progression.

CSS

Only seems to be coming into its own in the last few years and is truly a remarkable technology despite the hobbles that MSIE places on our ambitions. CSS Zen Garden has been a major source of ideas; I wouldn’t have been able to customise this blog as much as I have without them. I was an early adopter of the technology and got burnt by inconsistent browser support; Netscape 4 was the proverbial bête noir back then, fulfilling the role that MSIE plays today. In those days, it was the idea of controlling text display and element backgrounds from a single place that appealed. Since then, I have progressed to using CSS to replace table-based layouts and to control element positioning. It can do more…

JavaScript

Having had a JavaScript-powered photo gallery before my current Perl-driven one, I can say that I have definitely sampled this ever-pervasive scripting language. Being a client-side language rather than a server-side one, it does place you rather at the mercy of the browser purveyors, and it never ceases to amaze me that there is a buzz around AJAX because of this. In fact, the abundance of AJAX cross-browser function libraries is testimony to the need for browser-specific code. Despite my preferences for server-side scripting, I still find a use for JavaScript, and its main use for me these days is to dynamically control CSS elements to do such things as control the height of a page element or whether it is shown or not. Apparently, CSS may get some dynamic capabilities in the future and reduce my dependence on JavaScript. Meanwhile, Jeremy Keith’s DOM Scripting (Friends of Ed) will prove as much of an asset as it has done.

XML

These days, a lot of the raw data underlying my personal website is stored in XML. I did try to dynamically transform the display of the XML into something meaningful with CSS and XSLT when I first scaled its dizzy heights, but I soon resorted to other techniques. Browser support and the complexity of what I required were the major contributors to this. The new strategy involved two different approaches. The first was to create PHP/XHTML pages from the precursor XML offline, and this is how I generate the website’s directory pages. The other one is to process the XML as text to dynamically supply an XHTML page as the user visits it; this is the way that the photo gallery works.

Perl

This still powers all of my photo gallery. While thoughts of changing it all to PHP linger, there is a certain something about the Perl language that keeps it there. I suppose it is that PHP is entangled in the HTML while Perl encases the whole business, and I am reasonably familiar with its syntax these days, which is why it still does a lot of the data processing grunt work that I need.

PHP

PHP is everywhere these days, though it doesn’t attract quite the level of hype that used to be the case. It still appears with its sidekick MySQL in many website applications. Blogging software such as WordPress and content management systems like Drupal, Mambo and Joomla! wouldn’t exist without the pair. It appears on my website as the glue that holds my visitor directories together and is the processing engine of my WordPress blog. And if I ever get to a Drupal element to the site, by no means a foregone conclusion though I am spending a lot of time with it at this time, PHP will continue its presence in my website scripting as it powers that too.

Applications

Macromedia HomeSite

I have a liking for hand coding, so this does most of what I need. When Macromedia (itself since taken over by Adobe, of course) took over Allaire, HomeSite sadly lost its WYSIWYG capability, but the application still soldiers on even though Dreamweaver offers a lot to code cutters these days. Nevertheless, it does have certain advantages over Dreamweaver: it is a fleeter beast to start up and colour codes Perl syntax.

Macromedia Dreamweaver

There was a time when Dreamweaver was solely a tool for visual web page development, but the advent of Dreamweaver UltraDev added server-side development capabilities to the Dreamweaver family. These days, there is only one Dreamweaver version, but UltraDev’s capabilities still live on in the latest version and I would not be surprised if they were taken further in these database-driven times.

Nowadays, Dreamweaver isn’t an application where I spend a great deal of time. In former times, when my site was made up of static HTML pages, I used Dreamweaver a lot, even if its rendering capabilities were a step behind the then-current browser versions. I suppose that it didn’t fit the way in which I worked, but its template-driven workflow would have been a boon back then.

However, my move from a static site to a dynamic one, starting with my photo gallery, has meant that I haven’t used it as much since then. However, with my use of PHP/MySQL components on my site. Its server-side abilities could get the level of investigation that its PHP/MySQL capabilities allow.

Altova XMLSpy Professional

Adding MySQL databases to my web hosting costs money, not a lot, but it could be spent on other (more important?) things. Hence, I use XML as the data store for my photo gallery and XML files are pre-processed into XHTML/PHP pages for my visitor directories before uploading onto the server.

I use XMLSpy to edit and manage the XML files that I use: its ability to view XML in grid format is a killer feature as far as I am concerned and XML validation also proves very useful; particularly when it comes to ensuring that DTD’s and XML files are in step and for the correct coding of XSLT files. There are other features that I need to explore and that would also take my knowledge of the XML further to boot, not at all a bad thing.

Saxon

For processing XML into another file format such as XHTML, you need a parser and I use the free version of Saxon to do the needful, Saxonica offers commercial versions of it. There is, I believe, a parser in XMLSpy, but I don’t use it because Saxon’s command line interface fits better into my workflow. This is a Perl-driven process where XML files are read and XSLT files, one per XML file, are built before both are fed to Saxon for transforming into XHTML/PHP files. It all works smoothly and updating the XML inputs is all that is required.

AceFTP

If I were looking for an FTP client now, it would be FileZilla, but AceFTP has served me well over the last few years, and it looks as if that will continue. It does have some extra features over FileZilla: transfers between remote sites, and scheduling, for example. I have yet to use either, but they look valuable.

Hutmil

In bygone days when I had loads of static HTML files, making changes was a bit of a chore if they affected every single file. An example is changing the year on the copyright message on the page footers. Hutmil, which I found on a magazine cover-mounted disc, was a great time saver in those days. Today, I achieve this by putting this information into a single file and getting Perl or PHP to import that when building the page. The same “define once, use anywhere” approach underlies CSS as well, and scripting very usefully allows you to take that into the XHTML domain.

Apache

Apache is ubiquitous these days, and both the online and offline versions of my site are powered by it. It does require some configuration, but it is a powerful piece of kit. The introduction of 2.2.x meant a big change in the way that configuration files were modularised and while most things were contained in a single file for 2.0.x, the settings are broken up into different files in 2.2.x, and it can take a while to find things again. Without having it on my home PC, I would not be able to use Perl, PHP or MySQL. Apart from this, I especially like its virtual site capability; very useful for offline development.

WordPress

My hosting supplier offers blogs on Blogware, but that didn’t offer the level of configuration that I would have liked. It is true that this is probably true of any host of blogs. I can’t speak for Blogger, but WordPress.com does have its restrictions too. To make my hillwalking blog fit in with the appearance of my photo gallery, I went popped over to WordPress.org to download WordPress so that I could host a blog myself and have maximum control over its appearance. WordPress supports themes, so I created my own and got my blog pages looking as if they are part of my website, rather than looking like something that was bolted on. Now that I think of it, what about WordPress supporting user-created themes? I support that there is the worry of insecure PHP code but what about it?

MySQL

I am between minds on whether this is a technology or a tool. SQL certainly would be a technology standard, but I am not so clear on what MySQL would be. In any case, I have classed it as a tool, and a very useful one at that. It is the linchpin for my WordPress blogs and, if I go for a content management system like Drupal, its role would surely grow. While I do have a lot of experience with using SAS SQL and this helps me to deal with other varieties, there is still a learning curve with MySQL that gets me heading for a good book and Kofler’s The Definitive Guide to MySQL5 (Apress) seems to perform more than adequately in this endeavour.

Paint Shop Pro

As someone who hosts an online photo gallery, it won’t come as a surprise that I have had exposure to image editors. Despite various other flirtations, Paint Shop Pro has been my tool of choice over the years, but it is now set to be usurped by a member of Adobe’s Photoshop family. Paint Shop Pro does have books devoted to it, but it appears that Photoshop gets better coverage and I feel that my image processing needs to be taken up a gear, hence the potential move to Photoshop