26th January 2012 The compact system camera arena is a burgeoning one with many manufacturers having followed Olympus into the fray. In latter months of last year, Nikon finally took the plunge though Canon have yet to do the same. Seeing offers on Olympus E-PL1 kits with a 14-42 mm zoom lens had me tempted, particularly with a price tag of the order of £250. In fact, I even got to looking into the competition too and a shortlist emerged. This also featured the Samsung NX-11 and the Sony NEX-C3 as well as the big brother of the latter, the NEX-5N.
What eventually countered the allure of shiny objects was the question as to why I needed such an item. After all, I already possess a Pentax K10D DSLR and a Canon Powershot G11 and these have been satisfying my photographic needs for a while now. The DSLR may date from 2007 but it is still working well for me and, if it ever needed replacing, I’d be going for another Pentax with the K-5 being a strong contender. The Canon is doing what’s asked of it so the recent launching of the G1 X isn’t so tempting either.
The whole dalliance has me wondering about how photographic equipment changeovers come about. After all, it was around a decade ago with the DSLR revolution was in the offing if not in progress. Until then, film photography was predominant but it looks as if it got as far as it could from a technological point of view when I look back at what happened. The digital photography area was new and untapped so moving there offered new possibilities and purchases more easily justified. The end result is that very few film cameras are being made nowadays. Ironically, it’s film photography that now is untrammelled terrain for many and it is holding its own too in an era when digital photography predominates.
The same sort of newness that came with digital photography also applies to CSC‘s to a certain extent. From the heritage of half-frame 35 mm film photography, Olympus has fashioned a different type of digital camera: essentially a compact with interchangeable lenses. Was it the fact that I have no CSC that caused me to be tempted and has it happened to others too? Also, is that what got digital photography going in the first place?
It almost feels as if camera manufacturers have to keep bringing to market new models and new types of camera in order to stay in business. After all, Minolta had to sell its camera division to Sony when they failed to get going in the DSLR market quickly enough. The same thing might have happened to Pentax too with the marque passing to first to Hoya, and then to Ricoh after the firm lost its independence.
What doesn’t help is the lack of longevity of camera models. The coming of digital photography has exacerbated this situated with models being launched at a frenetic rate. In the days of film photography, a model could last on the market for a few years and there was once a time when a twenty year lifetime wouldn’t have looked so ridiculous though there were incremental improvements made over that time too. For instance, a Pentax K1000 wouldn’t be exactly the same at the end of its production run as it was at the start though the model number may be the same. That world is gone.
Camera types have done better with the SLR design lasting around 50 years so far. However, mirror-less camera technology is adding pressure like never before. Even compact cameras allow live TTL type viewing and Olympus dug into its film camera heritage to add an interchangeable lens mount to give us the first E-P1. The original PEN cameras were half-frame 35 mm affairs and, appropriately enough, their descendants have small sensors in the micro four thirds mould. Then, there’s Sony’s efforts with translucent mirrors that do not move like their SLR counterparts. Canon tried this in the 1980’s with film cameras but never pursued the genre. After that, there are mirror-less SLR-style cameras from Samsung and Panasonic that make you wonder if a full size equivalent is in the offing with live viewing and an electronic viewfinder. Olympus is doing a teaser advertising campaign at the moment and it has some wondering if an OM-D is in the offing.
In parallel with all this, Sony is making a good impression with their CSC’s, the NEX series. These have APS-C sized sensors like many DSLR’s and in compact bodies as well. However, the feel very much is that of a compact camera and some have complained of a like of buttons on them though the photographic quality is very good. Samsung have gone for the same sensor size in their NX-11 thought they have gone for SLR styling. That may be more suitable for some than having to find settings buried in menus.
In summary, we are in an exciting if unnerving time in camera technology at the moment. On one hand, we are seeing a great deal of miniaturisation and what formerly were still cameras can do movie making as well. The latter may not be an interest of mine and it looks like a time-consuming hobby too. A lot is in flux right now and a recent court case reminded us of the difficulties in doing original work these days with image processing in Photoshop forming the basis of a victorious copyright claim. Because the number of images that are getting created everywhere, it could be hard for some to avoid this one and that could be exacerbated if the government changes the law so that intellectual property claims can be processed in the small claims courts. That sort of thing makes film photography seem attractive and it does seem that it isn’t disappearing either, even if Kodak has its financial problems. Novelty seems to change photographic tastes and it seems that film photography is novel again. It’s a changing world and who knows where it take us. Maybe a new DSLR body might make a good purchase in case CSC’s usurp their place entirely. Photographic technology is interesting yet again.
6th December 2010 This edifice is powered by WordPress, but there are other open-source blogging options out there and a number of these appear below, along with some proprietary alternatives. Also joining the list is the software that powers Wikipedia and a smattering of open-source Content Management Systems.
Though there appears to be a myriad of web publishing options out there presently, I’ll remain open to looking at whatever comes my way. For anything to be added here, though, it will need to open source and allow self-hosting. The former criterion excludes options like ExpressionEngine or Perch even if there is a version available that is free of charge and I recognise that many like it. The latter constraint means that services like Blogger, SquareSpace, Tumblr or WordPress.com won’t be discussed here. Many may use these, but this collection is meant for the do-it-yourself inclination that is in many of us. That is never to say that I look down on users of hosted publishing solutions because what you find here once started out on WordPress.com and, even today, I still have another active site on there.
Album
Alfresco
Though there is an enterprise edition too, this is an open-source Java-powered content and document management system. The community edition is available free of charge, but the company behind this makes its money from the enterprise edition and the provision of support.
calmPress
This is a fork of WordPress that is focused on being more security and privacy orient. The TinyMCE editor is retained while Akismet is not part of the distribution, though the latter can be added from the WordPress plugins repository. Other callbacks to WordPress servers are being removed as well to furthering privacy. Version numbering indicates that these may be early days for the project, so it will be interesting to see how things proceed.
ClassicPress
The advent of the WordPress Gutenberg project also inspired this project to create its own fork, and it advertises a focus on business usage while sticking with the TinyMCE editor. Over time, it also may gain its own plugin repository, but that is for later. Existing WordPress instances can be converted using a plugin and it also it is possible to have a stand-alone new installation just like its parent project.
CMS Made Simple
ConcreteCMS
Contao
Coppermine
DokuWiki
Drupal
Nearly a decade ago, I went looking at this and was put off by the inability to bend website theming to my will and to match other parts of the outdoor activities, photography and travel website, so I left it. The opportunity to set up a stand-alone website dedicated to my late father’s history writings changed things recently, and I decided to have another go with much more success and much less irritation than the previous dalliance.
Fork
Foswiki
GetSimple
There’s no MySQL needed for this since the storage medium is XML. It could be worth a look, then.
Ghost
This blogging tool appears to be getting a lot of praise these days when WordPress is so dominant. Finding a copy to install on a server of your own needs a visit to the installation guide in the documentation, or to go to its area on GitHub. There also are free and paid hosting options too, and that is what is being proffered on the project’s home page. Though available as open-source under the more permissive MIT licence, there clearly is a need to fund the project’s future development.
Grav
ImpressPages
Hugo
There are a number of static website generators out there, but this is the only one that I actually have used to produce a website. That was a simple affair that allowed me to spend some time learning a new way of working. The result was a success, so other web presences may use this approach, and there are platforms like Tina that automate the process as well.
Jekyll
There is no database at the back of this and the content editing involves using Markdown too, so this is a different approach to publishing on the web. Because Ruby is the technology underlying the whole thing, your web host may need to support that too. Nevertheless, Stack Overflow decided to use it for their own blog, so that is an example for you to survey.
Joomla!
MediaWiki
MoinMoin
Movable Type
This was king of the blogging hill until it upset its users, but it remains very much out there, having had users like the BBC. Though there was an open-source version at one point, that no longer is the case, so this very much is a for-fee option.
Omeka
Pivot
PivotX
Piwigo
ProcessWire
Serendipity
This uses the Smarty templating engine as the backbone of its blogging capability, and very well it seems to work too. Of course, there is the need to learn a new way of doing things, but that’s always the way with unfamiliar technology. In this case, it is the templating language that really supplies the learning curve, though a day’s effort is all that’s needed to get going. With all that’s going for it, it’s a pity that the calendar widget (or nugget as these things get called in the Serendipity world) doesn’t stop when it should and lands you one month into the future! Let’s hope that they get as far as addressing that one.
SilverStripe
Subrion
Textpattern
It may not feel as slick or as swish as others, but I have made it do what I want for A Wanderer’s Miscellany. With its only Textile mark up language and the way that content is organised, it may come across as being more for technical folks, but that can be tamed too. Plugins help on that front, and I have grown to respect the flexibility. As you might have gathered, I like it.
TiddlyWiki
Tiki Wiki
Typo3
Weblery
WonderCMS
The lightweight nature of this intrigues me so much that I might have checked it out when moving some websites away from WordPress and Drupal. Hugo was chosen then, so it may be that another project will allow further investigations.
WordPress
Started out as a fork from b2 and is moving along a path from a dedicated blogging tool to a more general content management system. Though I am always concerned that some succeeding version will foist something upon me that I don’t want or need, it, so far, has avoided this state of affairs. That’s just as well, given that it turns up on nearly every website that I now run.
XODA
It might seem odd to include a document management system in here, but there’s something to be said for managing the content assets that sit behind a website too.
XWiki
16th July 2009 I was perusing a recent copy of Linux Format and encountered a feature describing a self-hosted alternative to the likes of Flickr: Gallery. From my quick look, it looks fully featured, offering themes and even shopping cart facilities for those who want to sell their wares. The screenshots on the open-source project’s website look promising but, for a fuller appraisal, I would need to spend some time trying to bend it to my will. Before anyone mentions it, I am aware that WordPress can be used for photoblogging, but this tool seems to take things a bit further. It’s the sort of thing about which I might have wondered, given the pervasiveness of content management systems these days. My own custom-built photo gallery is devoid of a slick back end, hence why Gallery caught my eye, but I’ll continue with it and may even get to adding the needful myself.
25th January 2008 It was the prospect of having Photoshop Elements going on Linux that got me thinking about working with WINE. The cause of that was Elements’ inability to edit, create and save files to a VMware shared folder. As it turned out, there was more to my WINE adventures than getting Elements working. Because I was in learning mode, those adventures turned out to be messy ones with WINE getting uninstalled and reinstalled a number of times. For the last of these, I forced matters by installing from a DEB package rather than going through Ubuntu’s normal channels. The openSUSE journey was a bit more orderly and that VM option remains if I want to go experimenting more.
Along the way, I got the Windows version of Opera going as a test. When trying out WINE in former times, I never tried installing applications into it like I do now. I don’t know if this was because I hadn’t made an important connection or that wasn’t the way that things used to be. Flushed with the success of Opera, I went further and discovered that Dreamweaver 8 and Altova’s XMLSpy 2007 Professional work without my breaking a sweat. Photoshop Elements was another story and one that I have told before. Apple’s iTunes was another thing that I tried but without success, even with a useful guide on Wine Reviews; for some reason, I’m having trouble getting the installation to complete successfully. I think that I’ll leave my tinkering at that for now but my general impression is that WINE works well these days, even if there is the odd crash or inexplicable disappearance of an application window. The latter happened with Dreamweaver and XMLSpy and I needed to log off and back on again to clear the slate for further progress.
20th October 2013 GNOME 3.10 came out last month but it took until its inclusion into the Arch and Antergos repositories for me to see it in the flesh. Apart from the risk of instability, this is the sort of thing at which rolling distributions excel. They can give you a chance to see the latest software before it is included anywhere else. For the GNOME desktop environment, it might have meant awaiting the next release of Fedora in order to glimpse what is coming. This is not always a bad thing because Ubuntu GNOME seems to be sticking with using a release behind the latest version. With many GNOME Shell extension writers not updating their extensions until Fedora has caught up with the latest release of GNOME for a stable release, this is no bad thing and it means that a version of the desktop environment has been well bedded in by the time it reaches the world of Ubuntu too. Debian takes this even further by using a stable version from a few years ago and there is an argument in favour of that from a solidity perspective.
Being in the habit of kitting out GNOME Shell with extensions, I have a special interest in seeing which ones still work or could work with a little tweaking and those which have fallen from favour. In the top panel, the major change has been to replace the sound and user menus with a single aggregate menu. The user menu in particular has been in receipt of the attentions of extension writers and their efforts either need re-work or dropping after the latest development. The GNOME project seems to have picked up an annoying habit from WordPress in that the GNOME Shell API keeps changing and breaking extensions (plugins in the case of WordPress). There is one habit from the WordPress that needs copying though and that is with documentation, especially of that API for it is hardly anywhere to be found.
GNOME Shell theme developers don’t escape and a large border appeared around the panel when I used Elementary Luna 3.4 so I turned to XGnome Enhanced (found via GNOME-Look.org) instead. The former no longer is being maintained since the developer no longer uses GNOME Shell and has not got the same itch to scratch; maybe someone else could take it over because it worked well enough until 3.8? So far, the new theme works for me so that will be an option should there a move to GNOME 3.10 on one of my PC’s at some point in the future.
Returning to the subject of extensions, I had a go at seeing how the included Applications Menu extension works now since it wasn’t the most stable of items before. That has improved and it looks very usable too so I am not awaiting the updating of the Frippery equivalent. That the GNOME Shell backstage view has not moved on that much from how it was in 3.8 could be seen as a disappointed but the workaround will do just fine. Aside from the Frippery Applications Menu, there are other extensions that I use heavily that have yet to be updated for GNOME Shell 3.10. After a spot of success ahead of a possible upgrade to Ubuntu GNOME 13.10 and GNOME Shell 3.8 (though I remain with version 13.04 for now), I decided to see I could port a number of these to the latest version of the user interface. Below, you’ll find the results of my labours so feel free to make use of these updated items if you need them before they are update on the GNOME Shell Extensions website:
Frippery Bottom Panel
Frippery Move Clock
Remove App Menu
Show Desktop
There have been more changes coming in GNOME 3.10 than GNOME Shell, which essentially is a JavaScript construction. The consolidation of application title bars in GNOME applications continues but a big exit button has appeared in the affected applications that wasn’t there before. Also there remains the possibility of applying the previously shared modifications to Nautilus (also known as Files) and a number of these usefully extend themselves to other applications such as Gedit too. Speaking of Gedit, this gains a very useful x of y numbering for the string searching functionality with x being the actual number of the occurrence of a certain piece of text in a file and y being its total number of occurrences.GNOME Tweak Tool has got an overhaul too and lost the setting that makes a folder path box appear in Nautilus instead of a location part, opening Dconf-Editor and going to org > gnome > nautilus > preferences and completing the tick box for always-use-location-entry will do the needful.
Essentially, the GNOME project is continuing along the path on which it set a few years ago. Though I would rather that GNOME Shell would be more mature, invasive changes are coming still and it leaves me wondering if or when this might stop. Maybe that was the consequence of mounting a controversial experiment when users were happy with what was there in GNOME 2. The arrival of Fedora 20 should bring with it an increase in the number of GNOME shell extensions that have been updated. So long as it remains stable Antergos is good have a look at the latest version of GNOME for now and Cinnamon fans may be pleased the Cinnamon 2.0 is another desktop option for the Arch-based distribution. An opportunity to say more about that may arrive yet once the Antergos installer stops failing at a troublesome package download; a separate VM is being set aside for a look at Cinnamon because it destabilised GNOME during a previous look.
1st October 2019 Over the weekend, I finally got to fixing a problem that has affected Ubuntu 18.04 virtual machine for quite a while. The usual checks on Guest Additions installation and vboxsf group access assignment were performed but were not causing the issue. Also, no other VM (Windows (7 & 10) and Linux Mint Debian Edition) on the same Linux Mint 19.2 machine was experiencing the same issue. The latter observation made the problem intrinsic to the Ubuntu VM itself.
Because I install the Guest Additions software from the included virtual CD, I executed the following command to open the relevant file for editing:
sudo systemctl edit --full vboxadd-service
If I had installed installed virtualbox-guest-dkms and virtualbox-guest-utils from the Ubuntu repositories instead, then this would have been the command that I needed to execute instead of the above.
sudo systemctl edit --full virtualbox-guest-utils
Whichever configuration gets opened, the line that needs attention is the one beginning with Conflicts (line 6 in the file on my system). The required edit removes systemd-timesync.service from the list following the equals sign. It is worth checking that file paths include the correct version number for the Guest Additions software that is installed in case this was not the case. The only change that was needed on my Ubuntu VM was to the Conflicts line and rebooting it got the Shared Folder automatically mounted under the /media directory as expected.
26th July 2020 While some Linux distros like Fedora install VirtualBox drivers during installation time, I prefer to install the VirtualBox Guest Additions themselves. Before doing this, it is best to remove the virtualbox-guest-additions package from Fedora to avoid conflicts. After that, execute the following command to ensure that all prerequisites for the VirtualBox Guest Additions are in place prior to mounting the VirtualBox Guest Additions ISO image and installing from there:
sudo dnf -y install gcc automake make kernel-headers dkms bzip2 libxcrypt-compat kernel-devel perl
During the installation, you may encounter a message like the following:
ValueError: File context for /opt/VBoxGuestAdditions-<VERSION>/other/mount.vboxsf already defined
This is generated by SELinux so the following commands need executing before the VirtualBox Guest Additions installation is repeated:
sudo semanage fcontext -d /opt/VBoxGuestAdditions-<VERSION>/other/mount.vboxsf
sudo restorecon /opt/VBoxGuestAdditions-<VERSION>/other/mount.vboxsf
Without doing the above step and fixing the preceding error message, I had an issue with mounting of Shared Folders whereby the mount point was set up but no folder contents were displayed. This happened even when my user account was added to the vboxsf group and it proved to be the SELinux context issue that was the cause.
16th March 2007 We have seen the beta come out, an unprecedented move for Adobe, and now we are hearing about the new professional editions of Photoshop: Photoshop CS3 for digital imaging and Photoshop CS3 Extended with tools for processing digital video. Together with Photoshop Lightroom for digital photography and Photoshop Elements for the consumer market, it seems that Photoshop is moving from a single application to becoming a big family of them. Adobe is hosting an online launch for the CS3 suite on March 27th so the appearance on the market of the new Photoshop must be very imminent. In the light of this, I think I’ll hold off on a decision to purchase either Elements 5 or its CS2 until I have tried out the latter’s successor.
Update: I’ve just perused both .Net’s and Advanced Photoshop’s initial appraisals of Photoshop CS3 and they seemed impressed so it should be worth a look then. Another tempting idea is to have a taste of Lightroom so I went and downloaded the 30-day trial version. I may well have a go with it in my own time; I’m not wanting to install it and let the 30 days run out before I get to use it in anger.
19th November 2009 For a while, the Windows computing side of my life has been spread across far too many versions of the pervasive operating systems with the list including 2000 (desktop and server), XP, 2003 Server, Vista and 7; 9x hasn’t been part of my life for what feels like an age. At home, XP has been the mainstay for my Windows computing needs with Vista Home Premium loaded on my Toshiba laptop. The latter variant came in for more use during that period of home computing “homelessness” and, despite a cacophony of complaints from some, it seemed to work well enough. Since the start of the year, 7 has also been in my sights with beta and release candidate instances in virtual machines leaving me impressed enough to go popping the final version onto both the laptop and in a VM on my main PC. Microsoft finally have got around to checking product keys over the net so that meant a licence purchase for each installation using the same downloaded 32-bit ISO image. 7 still is doing well by me so I am beginning to wonder whether having an XP VM is becoming pointless. The reason for that train of thought is that 7 is becoming the only version that I really need for anything that takes me into the world of Windows.
Work is a different matter with a recent move away from Windows 2000 to Vista heavily reducing my exposure to the venerable old stager (businesses usually take longer to migrate and any good IT manager usually delays any migration by a year anyway). 2000 is sufficiently outmoded by now that even my brother was considering a move to 7 for his work because of al the Office 2007 files that have been coming his way. He may be no technical user but the bad press gained by Vista hasn’t passed him by so a certain wariness is understandable. Saying that, my experiences with Vista haven’t been unpleasant and it always worked well on the laptop and the same also can be said for its corporate desktop counterpart. Much of the noise centered around issues of hardware and software compatibility and that certainly is apparent at work with my having some creases left to straighten.
With all of this general forward heaving, you might think that IE6 would be shuffling its mortal coil by now but a recent check on visitor statistics for this website places it at about 13% share, tantalisingly close to oblivion but still too large to ignore it completely. All in all, it is lingering like that earlier blight of web design, Netscape 4.x. If I was planning a big change to the site design, setting up a Win2K VM would be in order not to completely put off those labouring with the old curmudgeon. For smaller changes, the temptation is not to bother checking but that is questionable when XP is set to live on for a while yet. That came with IE6 and there must be users labouring with the old curmudgeon and that’s ironic with IE8 being available for SP2 since its original launch a while back. Where all this is leading me is towards the idea of waiting for IE6 share to decrease further before tackling any major site changes. After all, I can wait with the general downward trend in market share; there has to be a point when its awkwardness makes it no longer viable to support the thing. That would be a happy day.
10th August 2018 Since upgrading to Linux Mint 19, I have installed some software from Flatpack. The cause for my curiosity was that you could have the latest versions of applications like GIMP or Libreoffice without having to depend on a third-party PPA. Installation is straightforward given the support built into Linux Mint. You just need to download the relevant package from the Flatpack website and running the file through the GUI installer. Because the packages come with extras to ensure cross-compatibility, more disk space is used but there is no added system overhead beyond that from what I have seen. Updating should be as easy as running the following single command too:
flatpack update
However, I needed to do a little extra work before this was possible. The first step was to update the configuration file at ~/.local/share/flatpak/repo/config to add the following lines:
[remote "flathub"]
gpg-verify=true
gpg-verify-summary=true
url=https://flathub.org/repo/
xa.title=Flathub
Once that was completed, I ran the following commands to import the required GPG key:
wget https://flathub.org/repo/flathub.gpg
flatpak --user remote-modify --gpg-import=flathub.gpg flathub
With this complete, I was able to run the update process and update any applications as necessary. After that first run, it has been integrated in to my normal processes by adding the command to the relevant alias definition.