Shop Forum More Submit  Join Login
About Design & Interfaces / Professional yereverluvinuncleberMale/United Kingdom Groups :icondesign-addicts: Design-Addicts
design, art, customisation
Recent Activity
Deviant for 7 Years
Needs Core Membership
Statistics 925 Deviations 7,950 Comments 127,475 Pageviews

Newest Deviations

Steampunk MediaPlayer Ywidget 1.0.14a by yereverluvinuncleber Steampunk MediaPlayer Ywidget 1.0.14a :iconyereverluvinuncleber:yereverluvinuncleber 2 5 Commando Comic Animated Cover by yereverluvinuncleber Commando Comic Animated Cover :iconyereverluvinuncleber:yereverluvinuncleber 3 0 Ye Roast Beef of Olde England by yereverluvinuncleber Ye Roast Beef of Olde England :iconyereverluvinuncleber:yereverluvinuncleber 5 6 A Dickensian Christmas by yereverluvinuncleber A Dickensian Christmas :iconyereverluvinuncleber:yereverluvinuncleber 2 19 Neil Sees Brexit by yereverluvinuncleber Neil Sees Brexit :iconyereverluvinuncleber:yereverluvinuncleber 5 11 Neil Sees Steam Engines by yereverluvinuncleber Neil Sees Steam Engines :iconyereverluvinuncleber:yereverluvinuncleber 15 10 Musical Christmas Advent Bauble Widgets by yereverluvinuncleber Musical Christmas Advent Bauble Widgets :iconyereverluvinuncleber:yereverluvinuncleber 11 25 Pheasant Casserole with a sword by yereverluvinuncleber Pheasant Casserole with a sword :iconyereverluvinuncleber:yereverluvinuncleber 3 32 Pie! by yereverluvinuncleber Pie! :iconyereverluvinuncleber:yereverluvinuncleber 3 42 Lamb from a broken oven by yereverluvinuncleber Lamb from a broken oven :iconyereverluvinuncleber:yereverluvinuncleber 3 18 Potato Cakes In The Pan by yereverluvinuncleber Potato Cakes In The Pan :iconyereverluvinuncleber:yereverluvinuncleber 3 15 Lamb In The Pan by yereverluvinuncleber Lamb In The Pan :iconyereverluvinuncleber:yereverluvinuncleber 0 36 Steampunk CPU GPU OHM Thermometer by yereverluvinuncleber Steampunk CPU GPU OHM Thermometer :iconyereverluvinuncleber:yereverluvinuncleber 3 13 XP/Win 7 run dialog themed for Mediaeval Total War by yereverluvinuncleber XP/Win 7 run dialog themed for Mediaeval Total War :iconyereverluvinuncleber:yereverluvinuncleber 2 4 Medieval Total War Themed Folder Browser Skin by yereverluvinuncleber Medieval Total War Themed Folder Browser Skin :iconyereverluvinuncleber:yereverluvinuncleber 2 0 Gammon Ham Steaming Hot by yereverluvinuncleber Gammon Ham Steaming Hot :iconyereverluvinuncleber:yereverluvinuncleber 2 25


Ommatophobia by alexandreev Ommatophobia :iconalexandreev:alexandreev 331 14 Stalin's balls of steel by rOEN911 Stalin's balls of steel :iconroen911:rOEN911 118 8 Supermarine Seafire LF.III by Daniel-Wales-Images Supermarine Seafire LF.III :icondaniel-wales-images:Daniel-Wales-Images 60 12 Ura by Small-Brown-Dog Ura :iconsmall-brown-dog:Small-Brown-Dog 246 65 The Dream by dougfreak The Dream :icondougfreak:dougfreak 61 9 Supermarine Spitfire LF.Vc by Daniel-Wales-Images Supermarine Spitfire LF.Vc :icondaniel-wales-images:Daniel-Wales-Images 72 6 Old Gold by kceg Old Gold :iconkceg:kceg 24 15 Random old Truth and Bone comic book page by adeh20 Random old Truth and Bone comic book page :iconadeh20:adeh20 23 0 Happy Holidays (City Version) from Sizer by PaulSizer Happy Holidays (City Version) from Sizer :iconpaulsizer:PaulSizer 21 9 That Was close by Small-Brown-Dog That Was close :iconsmall-brown-dog:Small-Brown-Dog 248 74 The Dark Nine by geduliss The Dark Nine :icongeduliss:geduliss 81 17 Gift by AtriellMe Gift :iconatriellme:AtriellMe 30 5 Greenhouse 2 by Roseum Greenhouse 2 :iconroseum:Roseum 184 4 Baroque by kuzy62 Baroque :iconkuzy62:kuzy62 44 12 Jandosch Cloudfloater by the-first-seer Jandosch Cloudfloater :iconthe-first-seer:the-first-seer 108 55 Remembrance Day 1918-2018 by Daniel-Skelton Remembrance Day 1918-2018 :icondaniel-skelton:Daniel-Skelton 32 11



yereverluvinuncleber's Profile Picture

Artist | Professional | Design & Interfaces
United Kingdom
My alter ego is yereverluvinunclebert. You'll find me around the web. Where you find steampunk design I won't be far away.

I focus on Steampunk Design, why do I do it?

Well, I can't bear the look and feel of current desktop computing being so locked into a 1980s 'modern' paradigm. Current GUIs deriving mostly from Microsoft's efforts have a basis in the GUIs from the late 80s and early 90s and despite the regular changes they still haven't moved on much. Do you run XP, Vista, Win 7, 8 or 10? Well, if you do, that means under the skin you are still running NT5 or 6, all basically the same fundamental o/s. The only real differentiator is the GUI that MS foists upon you. Now, a GUI is a GUI and should not be confused with the underlying operating system. You should be able to decide which style of GUI you want to run.

A GUI should be independent of the o/s or at the very least the o/s ought to be very easy to theme and to customise as you wish. This just isn't the case with any Microsoft operating system as the default 'look and feel' provided with the os is really the only thing that really sets it apart from the previous version.

You'll see a massive example of this with Metro or Material Design, the UI that comes with Windows 8 & 10. The underlying os is still good old NT6 and operates much in the same way that Win7 does. However, the whole user interface has been modified to try to get you to use live tiles on the desktop as you would on a Windows phone, to make you use 'apps' rather than programs as you would on the desktop. This schizophrenic approach to a desktop o/s is hoisted upon you as Microsoft has no decent tablet-centric o/s and instead are trying to squish Windows onto tablets - it isn't working, look at the death of windows phone and even more recently, the death of Windows on tablets. They are trying to get you to adopt a new GUI so that you conform to the business plan they have in mind for Windows. That business plan is now a failed model but you, the consumer is still suffering for it.

My aim is to help you break out of this corporate mindset and to think of desktop customisation as a natural thing to do, much in the same way that you decorate and design your home, make the desktop your place to live, to work and operate.

So, with this in mind, I set out to create a series of wallpapers, widgets and icons for an o/s interface that meets the aims and needs of a small but thoroughly dedicated group of chaps and ladies known as steampunkers.

I have set out my steampunk design skills in this way to demonstrate what I can do.

Whether or not you are a steampunker yourself, with these widgets and icons you can thoroughly steampunk your desktop.

You may use any of my images in any of your own creations but commercially only with my permission. In all cases I require a credit using my name or pseudonym - and in addition a link to my DA account or my own site.

Do me a favour and don't send me a Lllama. I don't know what these bloody Llama things are for in any case and I don't give them myself. IF anyone can enlighten me as to something concrete that I can do with them I'll be pleased to hear it.


I'm posting this in tribute to the rat that I just killed. He was 8-9" long and over a foot if you count the tail. Living outside our house under the wood pile near the porch he has been causing the dog to go mad, the cat couldn't care less. Blocked up all the holes and flooded his home so he was forced out and tried to get away. I bashed him with a stick and took him into the garden for deep burial (no honours). After digging his hole out for an hour I feel dirty and tainted but the rat died so he needs some commemoration at least - he's lived with us now for over a year, so it's a RAT Trap...

and you've been CAUGHT!
Xwidget has recently received a new lease of life through the packaging of a new version for sale through Steam.…

Xwidget has been on sale for a couple of months now and looks to be doing well. It has 55 fairly positive reviews and that is a good thing for its author as it means that it must be receiving a substantial number of new users, each of which is paying two or three pounds (£) towards the developer's coffers. The number of reviewers is always a mere fraction of the numbers downloading (1-3%) so it means there must be many more downloaders (5,000+) - meaning a good cash injection to the developer of approximately £10,000 (with Steam taking 30%). As a result of the sales generated, he has updated the engine to - although the version on the old Xwidget site is still only offering the old version for download. The recent changes are trivial for desktop developers, being related to ensuring the engine is compatible with Steam, bundling a few more 'themes', fixing a couple of bugs re: high DPI monitors and language settings. Regardless of the changes it is good to see the old engine is getting a bit of attention even if it is only the Steam version that is receiving it.

Hopefully, Tony will come round to see that there is life in the old engine yet. Over the years I have lobbied Tony very hard to get him to start fixing the bugs and enhance the IDE to make it more usable but with no luck whatsoever. Tony was previously intent on putting Xwidgets into its grave, he said as much saying he wanted to work on new things - RainWidgets being the result -  but perhaps this injection of cash will make him see that there is life in the old dog after all.

I would like to see Tony pick up the Xwidget code and address the buglist he already has, see it here:… - That buglist has been around since the middle of 2017 and the bugs have been around and identified for a lot longer than that. Tony a message for you - fix some of those bugs! If Xwidget really is NOT dead then you need to prove it! We (the community) offered help to fix those bugs but the help was rejected, so it is down to you and it is about time you fixed something, anything to prove it is still alive!

A positive side-effect is that Tony is actually present on Xwidget's Steam page responding to negative user comments. He has responded to the most negative of reviews but we still don't see Tony answering technical questions on Steam nor on the product forum. That's normal for Xwidgets.

Pleased to see that Tony is still involved. I understand that it must be very difficult to keep enthusiasm on a product that has been slowly dying for years especially when it fails to make you any money. The closure of the Xwidget gallery to non-paying users was initially a mistake that prevented possible users from seeing the potential of the software without actually paying for it, however, coupled with selling the engine on Steam, it might actually turn out to be a good decision as Xwidgets is now a fully commercial proposition and can no longer be downloaded in its full and current form for free, anywhere else. Steam may become the main download location for Xwidgets and it may receive a new lease of life in conjunction with that cash injection.

So, like Frankenstein's monster, Xwidget raises its battered head, an incomplete and unfinished piece of software and lurches back into life ready to plunge into new horrors? Hopefully not, let us hope Tony sorts out the horror stories and we'll have something akin to a usable IDE that works and is useful.

This is my favourite BREXIT song - listen to the words...

We've been living through some hard times,
We've been seeing through some dark times,
Now I know the sun will shine,
You don't understand my point of view,
How I must get away from you,
Now I know I must be free,
I always knew that it would be this way,
Everybody used to say,
Everybody seems to know,
Don't say I told you so,
Don't say I told you so,
Told you so, told you so.

I was thinking of a plan
to dye one's whiskers green
and only use so large a fan
that they could not be seen.

But I was thinking of a way
To feed oneself on batter,
And so go on from day to day
Getting a little fatter.

I heard him then, for I had just
Completed my design
To keep the Menai bridge from rust
By boiling it in wine.

These are all just ideas. Borrowed from Lewis Carrol's "Alice through the looking glass"

However, I have had an idea that is equally as mad which could mean that all those abandoned Xwidgeteers could create their widgets as Rain Widgets.

It involves taking an Xwidget and the resulting .XUL file containing XML descriptions and converting it to something resembling a Yahoo Widget .KON file. This first step would result in a functioning Yahoo widget that had no logic but could move around the desktop - that's not much I hear you say - and you'd be correct.

However, we already have conversion tools that convert from Yahoo widgets to Web widgets whose elements are derived from extracting the various .KON file descriptions to JSON descriptions to place a widget and all its components on the web. As these components would work equally well within RainWidget (which is just an embedded browser on the desktop) then we have the potential to convert Xwidget designs to RainWidgets more or less on the fly. The program logic would still need to be converted but as long as the original logic was done in javascript and not using cores then the Xwidget would be quite portable. If you are a user of Xwidget cores then where the X and Rain widgets share similar cores/measures, it would not be too complicated to convert from one to another.

For me to create a Y! Widget the process at the moment is a straightforward one, creation achieved first in Photoshop using layers, creating a .PSD file and then a .KON file via a Photoshop script that results in a Yahoo widget - that is then converted (by a new tool just written) to a more portable JSON form that can be used to create basic web/Rain widgets with some minor conversion.

The process for an existing Xwidget would be similar just exporting the widget from the Xwidget IDE, taking the resulting .XUL file and converting that to a .KON file first, then using all the existing conversion tools that should work just fine in order to create a working .JSON file. That .JSON could then be used for the positioning and layout of a new RainWidget.

All I have to do is to create a new tool to convert a Xwidget XUL to a Yahoo widget .KON file. It is do-able. Should I get cracking? Well, I need an incentive. It wouldn't help me much as I have never created any unique Xwidgets, they have all been clones of my Yahoo widgets but it really might help some that only create Xwidgets. It would really help people like Jim King who have hundreds of Xwidgets to be converted to RainWidgets but no realistic prospect of being able to do so.

Or is it just a mad idea just as mad as those I started out with? IS it mad for me to do it, just to help others or should I just wait around for Xwidgeteers to ask me to do it... I feel inclined toward the latter but I won't hold my breath whilst waiting.
Currently working on another of my creations, this time it is a steampunk media player. It runs on Windows and Mac os/x and uses each system's default media player to interact with music files. It is not really possible for one person to write the code to interact with every known file format that exists (I would be forever writing codecs) so instead I just use the in-built media player that already knows the majority of formats and interface with it via an o/s API.

Fig 01. The player in simple mode.

On Windows it is the WMP (Windows Media Player) and on os/X it is QT (QuickTime). The same logic/code is used for each and the steampunk player acts/responds the same on each platform, not quite multi-platform but dual certainly. It may well work on the Ubuntu 13.03 with the Yahoo connect TV engine but that is completely untested.

It has two modes, simple compact mode where it takes up very little screen space and allows you to resize the thing to tuck it away anywhere you like. On a small pull of the keychain it enters normal mode where it shows you all the tracks in its current list.

Fig 02. The player in simple mode showing it in operation.

I am just updating the widget's menus, fixing the help screens and adding new folder browsing functionality. The old YWE engine provides access to the standard Windows folder browsing API but it does not allow you to determine where the default folder location is, instead always starting at the computer's drive root which is a pain. I am just recreating that folder browsing functionality and adding the folder start parameter that the YWE developers forgot. I am creating a browser window that looks like an old XP classic frame but I will create a more steampunk look-and-feel for it later using photoshop.

You might think it would be more sensible to use active X to use a system-level call to bring up a folder browser window and you'd be quite correct for almost all programming languages except javascript. Javascript traditionally runs in a browser and is restricted from being able to access desktop APIs. Even with these desktop engines your javascript still code runs in a browser context, in the konfabulator engine it has embedded the webkit browser and the javascript engine that comes with it. Since NT6 (Vista) access to certain activeX APIs has been restricted/deprecated, it now seems to check the language type and so you can no longer fire up a folder browser as you'd like to. Instead you have build your own from scratch.

Note: Microsoft's own jscript which runs natively on the desktop can still access these APIs, it is just those embedded in the context of 3rd party browsers that are now forbidden to access certain Windows APIs, thanks Microsoft - we know what you are doing there...

Fig 03. Displaying the original folder browser, styled to look like XP classic, new skin yet to arrive...

Fig 03a. Displaying the new folder browser, a medieval skin

Isn't it amazing how a simple skin changes the whole? The two skins above were formally created using the same methods and form but the skin changes everything.

Fig 04. Displaying the help for the player in 'simple' mode.

Fig 05. Displaying the help for the player in 'full' mode.

Fig 06. The player on my desktop with a few other steampunk creations.

Steampunk Weather (top)
Steampunk Volume Control (top right)
Steampunk Clock Calendar (left)

Fig 07. The right click menu

The right click menu showing the RJtextEd shortcut link that allows me to edit the program project files at a simple select and click

Fig 08. The build button used to initiate the program.

For each project the build button is set to simply run the project's KON file, the file that is recognised by the engine by default to initiate the running of your program. You set this using the following menu option:

Project - configuration - run settings - run

These two simple configurations speed up the debugging/development process considerably.

part II

On the steampunk media player I have modified the folder and file listing code to allow displaying both folders and files on the same pane, previously it was was just folders or files.  A simple [i]filesystem.getDirectoryContents [/i]using the konfabulator API listing just gives you an alphabetical dump so in some way you have to sort the contents, display the folders first, then the files afterwards.

I am in the process of adding a slider to allow scrolling up/down which only appears when there is more than one screen of files/folders. Also allowing the manual selection of files using the up/down keys as well as scrolling pages using the mouse scroll wheel. It indentifies known file types as they are displayed and allows you to interact with the folders alone as this is a folder selector.

Why am I doing this? Not quite sure, it started out as a fix to the limitations of the engine but suddenly I am writing a full folder/file browser pop-up in javascript and starting to replicate default Windows functions. As you get stuck into something I feel the need to do it 'right' and not to alienate Windows users which means doing it roughly the same way.

It is only when you try to recreate something from the o/s yourself that you realise what a lot of code goes into a simple folder browser window...

Part III

// now allows selection of files but not to drill down into...
// now allows the up and down key selection of tracks/folders
// does not allow the selection to go above or below the list on a key up/down
// if a track is clicked upon or key'd then the default folder is chosen.
// implemented a return to open a sub-folder
// implemented the CTRL+HOME to return to the top screen and select the top track
// implemented the CTRL+END to go to the bottom screen and select the last track
// changed the selected track colour to match the rest of the window

More recently:

// selection by mouse only allowed on populated folder/tracks
// up icon click now correctly calcualtes from current tree position
// onMouse Scroll movements to select up/and down - WIP
// up icon now checks to see if the folder is a drive, if so now passes a boolean variable to cause the drives to be displayed
// added folder exclusion list to prevent the Windows folder from being browsed - ERROR!
// the readfolderslist now shows drives
// added a drive icon for drives only
// changed text alert for folders that contain no audio files
// changed the tooltip texts to be more relevant and informative
// changed the play button to a select button
// added ting and page turn sounds to navigation events
// added folder list refresh function to F5
// added back button code to handle the very last folder selection
// remove back icon when showing drives only
// when a folder has no files but still has sub-folders within, it requests to turn recursive searching on and do a rescan.

Part IV

I've added a help screen for the folder manager

A working version is now out:…

// fixed a bug with some CDs that have no track information causing no track title to trim()
// up to drive e: when the tooltip should say drive root, added code to handle the up icon mouse enter root identification
// added help screen and menu item
// added roll over highlight of the buttons
// added tooltip change to reflect file or folder selection
// created file background with file plaque changed according to type
// fixed the file/folder browser type as called from the various places.
// there is no selected file by default any more
// no file selection does nothing as it should
// double click a file in file mode must play it
// the 2nd and 3rd folders selected should not replicate the first if the folder selected is the same
// right click select fourth saved folder selects the wrong one, now calls setmenu
// save the selected folder to the current prefs so that when opening the new folder selector the previous position is retained.
// back pressed twice, the up location is not set correctly

Unfortunately, there may be one or two bugs but in general it works and does not crash. It is a fairly basic file/folder explorer with no drag/drop nor filename editing on-the-fly but it allows navigation, file or folder selection, has full help and does the job it was designed to do. It also has a unique look that appeals to me.
Steampunk MediaPlayer Ywidget 1.0.14a

New version 1.0.14a of the Steampunk Media Player Konfabulator/Yahoo Widget with steampunk folder/file explorer. Windows only! Mac os/x compatibility in progress.

This version brings a steamy/Victorian file explorer into play. You can see it here:…

// 1.0.14a contains the following bug fixes and changes.

// fixed a bug with file selection causing the currentfolder to empty
// both upIcon functions use the same code to select the up folder
// the upIcon function now only selects a folder if the path is valid
// array variables moved from mediaplayer to folder.js to make folder.js more portable
// new alert for selecting files when folders should be selected
// new busyIcon for the folder.js when selecting an up or down folder
// added a .030 sec sleep to allow the new busyIcon to display

NOTE: To make it look like the playlist above, you'll need the Centurion light SF font that you can get here: at Ufonts.

This is a Steampunk media player Yahoo Konfabulator widget based on my original Steampunk XWidget. A widget that will play your music but  take up only a tiny amount of your desktop. It is a lovely piece of eye-candy as well as being useful on your desktop.

The older version 1.0.13 is here:…

I shall leave it here just for a while until the bugs are fixed in the new version. Be aware that this widget is still in beta and so there may be bugs! Please report any errors back to me.


You can control the volume level of the media player by moving the slider or pause/play the track by clicking on the play button. Next and Previous buttons will select the next track to play.

The Steampunk Media Player Yahoo Widget is a moveable widget that you can move anywhere around the desktop as you require. The widget is usable on all Windows.

These widgets work with all versions of Windows, they have also been tested on XP SP3, Vista Home, Windows 7 Ultimate 64 bit, Windows 8 and 10 and it should work on all these with no problems whatsoever.

All javascript widgets need an engine to function, in this case the widget uses the Yahoo Widget Konfabulator engine. The engine interprets the javascript and creates the widget according to the XML description and using the images you provide.

This widget works with Windows XP SP3, it has been tested on Vista, Windows 7/8  and 10.

You will,  of course, need the Yahoo widget engine for this widget to run. Link here… or the Mac version:…

On Windows the installation guide is simple, install yahoo widgets, download the widget zipfile, unzip it, double click on the media player widget and you are done!

If you prefer to run the Xwidget version then get it here:



Instructions for running Yahoo widgets on Mac OS/X, all recent versions including Sierra.

Edit the following file: which is in /Users/xxx/Library/Preferences. Look for these lines:    <key>DockOpen</key>

Change to false if it is true.

Then you should be able to start Yahoo! Widgets and the menubar item should appear. Widgets can then be started from the menubar or by double-clicking them in the usual way.


You may use any of my own images in your own creations but commercially only with my permission. In all other non-commercial cases I require a credit to the original artists using their/my name or pseudonym and a link to their/my sites. With regard to the commercial use of incorporated images from other artists, permission would need to be obtained from the original owner.
Update 3. 6th January 2018 - jump straight to the end.
Update 2. 28th September 2018

The first alpha/beta of the RainWidget engine has just been released. What is RainWidgets? - I hear you ask. Well, RainWidgets is the spiritual successor to Xwidgets - though before you rush out to try to download and install it - hold on! RainWidgets is NOT Xwidget 2.0. Firstly, there is no upgrade path from Xwidgets, second, there is no IDE and finally, there is no simple and easy way to create widgets using a few cores and some .js glue.

Rainwidgets is a pure widget engine and that's it, no IDE, no prettiness, no padding, just an engine for HTML based widgets. So, before you get upset and feel depressed and annoyed that Xwidgets has taken the wrong direction be placated by the fact I am fairly sure that RainWidgets has actually taken the correct direction. So far it has the feeling that it might just be the tool that a lot of desktop customisers and web developers have been looking for. A really rather good tool for putting HTML based widgets on the desktop.

RainWidget engine
Fig. 01 RainWidget Alpha Release with some yet-unreleased widgets.

This is exactly what Xwidgets probably should have been and what it almost became. Xwidget 1.0 was attempting to emulate Yahoo widgets, ie. a javascript engine with o/s APIs that allows web technologies to access the desktop. Xwidgets did it rather badly integrating a half-decent GUI IDE but unfortunately not extending API support to the underlying language, javascript. RainWidgets is not following this approach and instead is using the power of the latest browser engine so it can use stock technologies (with its own o/s extensions) to place HTML/CSS and javascript straight onto the desktop. This is a good approach as it lends itself to anything from simple widget creation as well as having the power to potentially put any complex web application straight on the desktop. This really could be the killer app that everyone has wanted for years...

Tony(?) and his team (I think there was once another chap that worked with him called qiancang) have become quite used to me pouring scorn on their offerings, the bugs in Xwidgets, the failure to fix them, the failing infrastructure, the lack of documentation &c &c but this time they really ought to take a pat on the back. RainWidgets as the spiritual successor to Xwidgets is really spot-on and they should be congratulated.

Some brief technical stuff that I have just guessed from just looking at the thing: Chrome is the browser core, the javascript engine is Chrome's V8, RainWidgets incorporates the vue.js framework to do some of the javascript heavy lifting. For those that have unpicked a typical widget, the RainWidget equivalent to Xwidget's widget.xul file is the widget.json (the equivalent of the .KON XML file in the yahoo widget engine). Image or text elements are typically defined there, such items as width, height, names, data sources used &c. The good thing is that nothing is set in stone. You can build a widget any way you like. In fact, you should be able to port any existing web widget and with a bit of tweaking it should just work (testing this now).

The core of a RainWidget is an HTML page where you define the location of the CSS, create any required divs and then call your javascript logic. The RainWidget team have provided a few examples of running widgets, one of them a quite complex web widget using jquery. None of them should be copied slavishly as examples of how to create widgets, instead you should consider them as examples of the engine's capability to use any style and method of widget creation.

Jquery and other web technologies are supported but are not required. If your widget is already designed to use vue.js then there might be an implication as the engine itself uses vue.js (a javascript framework that does the javascript heavy-lifting for the engine). In this case it might just require you to remove the line that initialises vue.js in your own script to avoid duplication or conflict - unknown and untested.

Element styling is achieved in CSS using an embedded .css file that is included into the HTML or as an element within the HTML itself using the style tag. Styling can even be achieved in javascript. Basically, the rule is - do it yourself, however you choose. You are not limited.

To obtain system-level information, instead of using cores as in Xwidget, RainWidget uses "Measures" (originally called DataSources in the first version). Xwidgets cores were APIs designed to be implemented at the GUI level and stored within the XML and as a result were largely inaccessible to the javascript 'glue' layer. It was often impossible to derive data from an Xwidget core in code.  Measures seem to be better designed giving the javascript direct access to the derived data.  

Only a few measures have been implemented so far: weather, datetime, shortcuts &c. We see very few operating system APIs to the filesystem or other useful operating system functions (the drive API was the first to be created) but after all, this is only an Alpha grade release so we ought to lower our expectations and await new measures in the fullness of time. The developer was originally drip-feeding new measures weekly, probably as soon as he had cut the code, so keep an eye out for new functionality.

(Battery, CPU, RAM measures added in 1.22 and 1.3)

An image or element is bound to a measure using the vue.js framework's v-bind directive. The usual events should be supported, eg. the onClick event (v-bind : onclick = "") as well as all the other usual events (untested). Some events are currently implemented differently, for example: onkeydown/onkeypress - some drag/drop functions are not working as expected, perhaps he hasn't implemented them properly yet, "doKeyDown" being some sort of a workaround for a non-working keypress - more on this soon.

The javascript engine is Chrome's V8. A good choice of javascript that comes bundled with the embedded Chrome engine that RainWidgets uses to place the HTML widgets on your desktop. Previously, Xwidget used IE and Jscript, Microsoft's own version of javascript that had some pecularities and features other javascript engines did not have. For example, easy and direct access to the operating system through ActiveX/COM and extras such as the enumerate function will no longer work. As a result, some existing widgets' javascript code will not easily migrate to RainWidgets and any widget developers will have to depend upon any new cores that Tony writes to provide this missing functionality. It was mooted previously by Tony that in Xwidget 2.0 the APIs would be made available for user-modification or that the new engine would have the capability to run custom 'cores' - now called measures. We shall have to see if that functionality ever actually materialises in RainWidgets. I feel slightly unsure as to whether this promised functionality will ever arrive in RainWidgets as it may not be in the devs' best interests to allow creation of custom cores in the new engine. It would rather detract from the developer's contribution allowing others to customise and take control of his engine. So, we'll just have to wait and see. Personally, I would love to have this functionality, given that the creation of new cores was one of Tony's previous worst failings. I personally created polyfills in Xwidget's javascript to replace missing API functionality, I'd like to do be able to do the same in RainWidgets using an 'official' method.

The set of widgets that are currently bundled with the engine are a little unimaginative graphically but they demonstrate that the engine works and they do show the rather impressive capabilities of the engine itself. I have yet to fully build or migrate any one of my steampunk widgets but work is at hand testing and creating. Watch this space!

Some other features:

When you add a new widget, instead of displaying a gallery that points to the software's main site (as did Xwidget), it does basically the same thing but takes its feed directly from a specific Deviantart gallery - which is quite a sensible choice. It also has an option to open any local widgets on the appdata/widgets folder. For me, the gallery is a little intrusive on my desktop being so large on my 15" screen that it fills the screen, it can also seem a little unresponsive, especially when attempting to install a widget. I feel it needs more feedback to the user in order to tell him what is actually going on - I would prefer a more positive install button on each widget image and a progress bar during download and installation. Note that the Xwidget dock functionality has not been carried over to the new engine, in fact the new gallery acts as both a download location and a replacement for the dock.

The widget's settings pages are a significant improvement over Xwidgets (in that they exist at all - a good copy of Yahoo widgets prefs functionality) and each settings page is automatically generated according to the contents of the widget's  .JSON file. Very useful indeed.

A negative point is that the settings screens are very large, in fact far too large and clunky being based on Microsoft's preferred 'modern'-type themes. The resulting configuration windows are significantly over-sized for a windows desktop. It would be very useful if there was a RainWidget configuration option, a simple switch to reduce the settings font sizes and resulting window size so it suits the desktop. It is great having a settings screen optimised for those tablet-style systems out there but we also need an option which also provides a useful size for desktops. At the moment the settings screens are big and quite ugly. Experience from other engines proves that the widget configuration screens need to be compact and not overly-large especially when we take into account migration of existing widgets from other systems with complex configuration and plenty of options.

Fig. 02 A typical large text, bloated RainWidget settings page compared to a similar but compact one from another engine where a lot of configuration options can be located on one page due to small font size.

The current RainWidget right-click menus are quite good, anyone familiar with Xwidgets will notice how similar they are in layout and operation. Unlike their settings counterparts they are easy on the eye taking their layout from Windows default theme. I'd recommend leaving the menus to adopt their size from the current windows theme rather than forcing a particular look-and-feel such as that encountered in the menus of the sister product RainWallpaper.

Fig. 03 The RainWidget Menus conforming to the Windows theme as set by the user...the centurion font used in this case.

The engine by itself uses no discernible CPU when running no widgets at all. The widgets themselves are quite efficient, they simply use as much or as little cpu as your program requires. If you have a simple clock widget then it will use very little in the way of cpu resource. If you have a complex widget that does a lot of animation then expect it to use a lot more cpu. We have already migrated a few of our widgets to web widgets (this being the same technology used by RainWidgets) and the different browsers (Firefox, chrome, Edge, Safari) handle animation differently, some more efficiently than others. RainWidget's embedded browser engine, Chrome should be quite efficient at handling javascript animation in our experience but it has yet to be determined how well the engine runs complex animation in code - as this is untested. When running a complex animation in a similar web widget on the Chrome browser (some while ago) the animation was a little choppy at times. We shall have to see how this operates through the engine though I suspect it will be similar. Machines with faster CPUs will have smoother animation as a lot of javascript animation may be accomplished using mathematics and/or canvas manipulation. As RainWidget is using the latest Chrome technology it should benefit from the improvements to javascript optimisation that future versions of Chrome brings (webAssembly &c) as long as the later versions of RainWidgets incorporate up-to-date versions of Chrome.

Each RainWidget exists within its own process context, this is a good feature as it means one crashing widget will not bring down the whole engine and all the other widgets with it. This is the same safe method used by the old Yahoo widgets engine but not by Xwidget. In Xwidget one nasty bug could have an adverse impact on all the running Xwidgets and made Xwidget a rather unstable product. RainWidgets is a much better designed product from the outset. This is probably more due to the way that Chrome implements each page/widget as a separate process rather than a feature of the RainWidget engine itself. Nevertheless, it is a significant improvement over the Xwidget way of doing things.

As yet, the documentation is very sparse. Do not depend upon it, the widget engine is still being built, things will change. In any case, lower your expectations regarding documentation, the documents from this particular stable have always been a bit lacking. The good thing is that the documentation you need to write your widgets is simply the standard documentation for javascript, CSS and HTML which is available everywhere on the web.

With regard to the missing IDE. If this is a product from the Xwidget stable then any existing users wishing to migrate will expect an IDE. I think those people will be quite disappointed. I don't think the developers will create an IDE at all, focussing instead all their energies on the engine itself. Why do I say this? Well, the IDE is a massive task on its own, imagine creating a completely new widget engine, then a graphical compositor and in addition developing and maintaining a decent code editor? That is huge amount of work and in any case, the engine needs a lot of time to complete, probably six months work or more. Having said that, I have seen the prototype of Tony's next generation IDE and I'll drop a picture here when I get time (see below) so it is possible that the graphical compositor may yet see the light of day - one morning perhaps - but for now, consign the idea of a fully-fledged IDE to the dustbin. Personally I don't want the dev to create an IDE, if he takes on this mammoth task he will fail us on the engine APIs and it is the engine he needs to focus on as it is nowhere near complete.

Tony's XWidget 2.0 IDE
Fig. 04 Tony's XWidget 2.0 prototype IDE that has NOT been shipped with RainWidgets

Note that the above IDE was shipped with the precursor to RainWallpaper - the prototype XDesktop which was originally designed to be a combination of RainWallpaper and RainWidgets. The two eventually split into separate tools but the XDesigner shows what the developers had in mind for their next generation IDE.

The use of the Rain... name? I know that some Rainmeter devotees will be really rather annoyed with the developer's choice of name. It does try to imply that the product is from the same stable. If it helps, the developer did moot compatibility with LUA and Rainmeter skins for Xwidget 2.0 but if that is an aim for RainWidgets I'd be surprised, given RainWidgets current direction (HTML/javascript). Product naming has never been one of the developer's strengths, the Xwidget name itself was ambiguous given that it was already claimed and in use by other similar web-related products. Remember this product is from a Chinese stable and that plagiarism is one of their cultural strengths enabling them to copy other's existing products without a moment's moral concern... It just doesn't figure in their mindset.

That's it, that's all I have to say so far. RainWidget is not a simple tool for beginners and that will put off a lot of Xwidgeteers that will be wondering where to go from here. I'd say to them, stay put and keep creating Xwidgets but if you want a future migration path seriously brush up your HTML, CSS and javascript skills as you'll need them. In any case RainWidgets is still a tool in an alpha state, ie. being heavily developed now and not for serious use. It is missing almost all the most useful APIs except the most basic so my recommendation is to leave it for a while until both you and the product matures.

A weird route I had not expected to recommend, is to migrate your Xwidgets to the Yahoo widget engine. That engine is much closer in concept to RainWidgets than Xwidgets  is now and could act as a sort of stepping stone to allow conversion of your widgets into pure javascript code ready for RainWidgets when it matures. It would be a very good learning curve for any Xwidgeteer who wants to become a Rainwidgeteer in the future being based upon the same technologies and fully documented.

To everyone else, the serious web-coders, I'd say download the alpha version and give it a go. Some proper coding will be required especially as there is no IDE and no coding environment provided at all. You just need to use the tools you are already familiar with for web development. If you are a frustrated Xwidgeteer and you need some help from another long-suffering widgeteer regarding the cross-over tools that might be required, just ask and I''ll be pleased to help or make some recommendations.

You can obtain RainWidgets here at Rainysoft:

With regard to support, the product is in alpha so don't depend upon it and don't ask the developer any questions, just leave him to get on with the coding. In any case there is currently nowhere to ask him any questions as there still is no forum. You can now submit your new widgets to the new group on DA, as it has just opened to normal members.

That's my initial review with two updates to reflect reality, if I've made any mistakes please feel free to correct me. I had only been experimenting for a few hours when I wrote the article so forgive  any typos and other technical mistakes.

Congratulations to the Xwidget team, sorry, the RainWidget team for creating such an amazing (alpha) tool! I have high hopes for this product.

January 2018 Addendum:

It is a few months later and time to note any changes to RainWidgets. Firstly, I can confirm that the developer is definitely our old friend Tony. We can tell that by the same lack of communication that always comes from the Xwidget stable. Some other hints that the developer team is the same - the new site is hosted on the exact same server as the old Xwidget site. Also, the right click menus on Tony's products and the new Rain products are identical. The RainWallpaper IDE/Xwidget 2.0 IDE are also the same. Most importantly, just as with Rainwidgets, we have just the minimum of communication but no more, sounds familiar?. I see the deviantart group is no longer being updated but there is some well-hidden but terse information to be found on the product's website:

Ver1.6.5 (2018-12-6)
- RainWidget now on Steam
- Change Settings window size
- Improve Widget Animation Performance

Ver1.6 (2018-11-8)
- Change Application style to Dark stye

Ver1.4 (2018-10-10)
- Improve the widget options window

There are no new measures (APIs) but I suppose it has only been five months so that can be forgiven but I am hoping for some new ones at some point. No engine can be taken seriously without some basic APIs so I am hoping these will eventually arrive before a full year of release is out?

filesystem itemexists
filesystem readfile
filesystem writefile
filesystem isDirectory
filesystem getDirectoryContents
filesystem move
filesystem copy
filesystem delete

filesystem choosefile
filesystem choosefolder

system wireless
system network
system volume

This list represents the absolute basic APIs required to start coding some serious widgets. Without these it makes no sense to start converting your widgets to RainWidgets as they can do very little real work. As time passes it will become clear as to whether the developer wants to create a real widget engine. In another six months if we see nothing then we'll now that Rainwidgets is going the same way as Xwidgets with bursts of activity followed by months/years of nothing at all. I am pessimistic as I have experience of being an active member of the Xwidget community.

One important promise missing was the ability to create our own APIs. It was suggested a while back that Xwidget 2.0 (RainWidgets) would receive the capability of supporting user-written APIs (data-sources/measures). That particular promise seems to have fallen by the wayside which is a great pity as it could have helped Rainwidgets make better progress.

Rainwidgets is taking some stick for purloining the 'Rain' name. As expected the Rainmeter community is not impressed with the attempt to jump on the Rainmeter bandwagon. There's not much they can do about it but it is more likely to alienate a community than draw it in. A silly decision.

The Rainwidget engine is now commercial, being available for download ONLY on steam. This makes sense as it gives the developer some income but it will restrict access and therefore usage and popularity. The cost is minimal so that should not deter serious investigators but it will deter the majority of penny-pinchers that want things for free. A previously-bought full XWidget licence does not give you access to Rainwidgets which is a great pity and rather a missed opportunity to get loyal and committed widget developers on board. A rather depressing statistic is that after five months the DeviantArt group has only twelve members which is a very small community for such a potentially impressive product. I think Tony has again rather missed the boat with his terrible marketing. First thing I would have done is to give out commercial licences to everyone that bought Xwidgets. The second thing I would do is repackage it not as a mere toy, it isn't just a widget engine but as a first class tool for putting javascript on the desktop. Building widgets is the least that it can do and I can't quite understand why Tony doesn't 'get' that.

Let's hope that the RainWidgets alpha release is just a precursor to a major beta release where Tony will be a bit more forthcoming in all respects.
I am always working on more than one program/project due to a problem with boredom and a failure to focus on a specific task, a failing of mine. I have another project on the backburner.

Some programs have a function, ie. they actually do something, most of my programs do something very 'real' they just have a distinct interface that runs against the computer-norm for visuals. This particular program is purely visual. What's the idea? Well, the concept is how to take something that is static and bring it alive for marketing/advertising reasons. When I was a boy I'd have given my eye-teeth for a living, animated comic cover. I think it shows what can be done by taking an out-of-date comic format and bringing it into the 21st century.

With this in mind I have taken an image created by a friend of mine and turned it into an animated comic cover. SmallBrownDog's superb interpretation of a typical Commando Comic cover of the 1960s - animated and given life! I have taken SBD's two-dimensional image and have extracted the layers to create an animated desktop program/widget that has action and realistic sound effects all encapsulated within a comic book cover.

The original image updated by me to give it even more animation and life. You'll see I've added searchlights and a Me109 just coming into the picture top right. SBD will forgive me as these extra elements are animated.

It is a replica of a typical Commando Comic cover available in the UK in the late 1960s. There will be sound-effects, music and action. 99% complete and ready to show it fully in action.

The animated program is here:…

Created with Photoshop, converted into an XML code using a bespoke script we have for converting Photoshop PSD files containing multiple layers into an XML description. From this we attach javascript code using RJTe to various include files and we use the powers of a javascript runtime engine to create the program that operates on the Windows/Mac desktop. All the audio created using Audacity.

This program's code was entirely edited using RJTe.

// test operation as a .widget, check it ALL works as expected
// test operation as a .widget on another machine with Win10, check it ALL works as expected
// tidy up functions and descriptions
// add machine guns on demand!
// add randomness to the two paired explosions
// f5 plays nothing, true
// add a menu link to my widgets on DeviantArt
// add a menu to facebook and other links if necessary (setmenu)
// make the ack ack explosions a little more frequent
// add Me109 animation s x 2
// add large explosion
// add fade in of the whole thing at the beginning
// add close button to the widget
// add modern metro-style volume toggle
// add price image click to make me 109s re-appear
// add menu link to DC Thompson
// add menu link to DeviantArt
// add menu link to 2nd about us page
// created 2nd about us page
// add green banner, badge and link to DC Thompson
// corrected the about us page text
// added a close button to the about us page
// added theme music
// added debug and editing options

The image below is a very low quality GIF of the first part of the animation only (no sound).

In the recent past, this sort of program was typically created using Flash, a superb tool for creating animated graphic content for the desktop and the web. The trouble is that Flash has earned a bad name for itself due to the poor security design and its ubiquity on the web. Flash is still a superb tool for creating desktop applications. However, its demise on the web has also led to its demise on the desktop which is quite ridiculous. Regardless of what I think, Flash is dying and so it is rather pointless creating programs like the above in Flash despite its superb GUI with timelines &c.

Instead of Flash, I have just used the YWE and code with a few graphics to achieve the same, not quite as easy without a timeline editor but it shows what can be done. Doing it this way the javascript code is not constrained just to the Yahoo Widget Engine but can be re-used in other engines and even on the web by adapting the code to use the appropriate APIs.

SBD's original art can be found here:…
I know he won't mind me animating his original work, he has seen earlier versions already and was thrilled with the result, hopefully he will be even happier with the new version.

Commando Comic Animated Cover
SmallBrownDog's superb interpretation of a typical Commando Comic cover of the 1960s - animated and given life!

The thumbnail preview above is ALL that Deviantart allows. The actual original is 450 x 600 px. You can see it in life size here:…

I have taken SBD's two-dimensional image and have extracted the layers to create an animated desktop program/widget that has action and realistic sound effects all encapsulated within a comic book cover.

Created with SBD's kind permission.

This widget was created I.T.S.O. (in the style of) a Commando Comic by DC Thompson. Neither I nor SBD have any association with DC Thompson and the Commando Logo was used here as an example of ‘fair-use’ in fan-art and as of course as mere-flattery.

This is the first release of this widget and it has only been tested on two of my systems so far, Windows 7 64bit ultimate and Mac OSX Sierra. We would appreciate feedback if you encounter a bug on your system.

These are javascript widgets. Running the widget in a javascript engine frees javascript from only running within the captivity of a browser, you will now be able to run these widgets on your Windows/Mac desktop as long as you have an engine installed.

You will, of course, need the Yahoo widget engine for this widget to run. Get Yahoo widget engine here. - download and install the windows SDK.

On Windows the installation guide is simple, install yahoo widgets, extract the widget from the zipfile, double click on the .widget file and you are done!

On Mac OS/X it is a tiny bit more involved:

Instructions for running Yahoo widgets on Mac OS/X, all recent versions including Sierra.

Edit the following file: which is in /Users/xxx/Library/Preferences. Look for these lines: <key>DockOpen</key>

Change to false if it is true.

Then you should be able to start Yahoo! Widgets and the menubar item should appear. Widgets can then be started from the menubar or by double-clicking them in the usual way.


Note: The zipfile provided here contains the yahoo/konfabulator widget ready to install.


The only condition for downloading and using is that you leave feedback. Please leave a message and rate the widget/icons as it is the only payment I get for creating this small desktop addition :D

You may use any of my images in your own creations but commercially only with my permission. In all cases I require a credit to the original artist using my name or pseudonym and a link to my own Deviantart page.
A Dickensian Christmas
My Christmas table in the 17th century part of my house.

You can't see the food but you could certainly smell it. 12lb rib of prime beef slowly cooked in the Rayburn, piled high with butter parsnips, double-roast potatoes and sweet potatoes too. A pile of brussels sprouts with walnuts and bacon, carrots in butter, garlic and honey, home made stuffing, pigs in blankets and devils in blankets and quarter of a gallon of thick reduced red wine gravy. Finally leeks and cauliflower in a cheese and mustard roux and dollops of horseradish sauce with Yorkshire puddings.
MErRy ChRiStMaS! from me to anyone who reads this but especially to anyone who watches me on DA, I've met some really nice characters through DA and an especial MERry ChristMAS to you in particular!
What Xwidget could have been and how it should have succeeded? Just a short rant this time.

Xwidget had the potential to be a rather nice widget IDE and widgeting environment allowing easy widget  development and putting javascript programs on the desktop. It almost achieved this by building a very decent graphical GUI where a developer could compose and animate widgets and combining this with the embedding of a javascript rendering engine into one Windows desktop tool.

However, the very poor editing environment, the lack of any documentation whatsoever and the buggy implementation of APIs, coupled with a complete lack of support/updates for many years led to its failure to be adopted as the desktop javascript rendering engine of choice.

In this rant I am just proposing an alternative path for the Xwidget engine that probably would have led to success and the widespread adoption of a tool that the world does actually need but still doesn't quite have.

The developer Tony, built a good and functional graphical IDE as well a complete widget engine, the creation of either one being an impressive task for a single developer. The problem lies in the sheer scale of his achievement, no single man could do either task properly to completion (IDE and engine) and the result was neither of the two was ever really completed. The partially completed IDE was quite good but a successful IDE has two elements, the graphical side and the coding side. In the Xwidget IDE the coding side was implemented in such a lacklustre fashion that it made serious editing more or less an impossible task, a task that might in the end, drive any potential developer to distraction. Serious developers tried it and abandoned it as being a mere child's tool. The graphical GUI was a tour-de-force however - but one component without the other made the combination rather useless.

For Tony to succeed he would really have had to focus on just one task and let any other task wither on the vine. Perhaps he should have left the second part of the project until he had sufficient time to complete.

My proposal would have been that Tony should have simply adopted the Yahoo widget engine instead of creating his own engine from scratch. The Yahoo widget engine was always the superior option. If he had done this then Tony could have created the exact same IDE but specifically for the YWE that sorely needed a graphical IDE. IF Tony had taken this approach he would have had the advantages of full existing documentation (no need rewrite documentation from scratch), he would have had a commercial quality IDE that developers would have been willing to pay for that supported a dual-platform target (Windows and Mac os/X), a huge crowd of extant developers and compatibility with a highly stable widget environment that already had tens of thousands if not hundreds of thousands of existing widgets. If Tony had then wanted to create his own engine in time then he could have done so, however, given that the YWE is so technically competent there was never really any need. The YWE still works to this day as well as it ever did (99.9% functional) on XP, Vista, Win7/8/10 and Mac os/X). The work expended on creating a functional duplicate of the YWE could have been spent on improving the IDE and creating an Android version of the widget engine.

If  this approach had been taken we would have had the Android version a year or two earlier, the IDE might have been a useful place to code and Xwidget's adoption on the desktop might have sky-rocketed instead of plummeting to the depths of nowhere.

Tony caused the failure of Xwidget by failing to identify what was the best route for his efforts. No need to re-invent the wheel, he should have just done what he does best, simply the creation of a decent graphical GUI for an existing widget engine. If he had given himself more time and less to do, he might just have succeeded.

IF he had really felt the need to duplicate the YWE (due to Yahoo's abandonment of the technology) he could have reimplemented it using the same technology he really did use to build the actual Xwidget engine in our own timeline. That would have extended the life of the engine into the 2020s and ensured a future for Xwidgets. He could have done this at his leisure as there was no driving imperative to create a new engine. The commercial grade IDE would have brought in plenty of cash for Tony and the future for javascript development on the desktop would have been assured.

Fig 4.0 The quality of widgets that only the Yahoo widget engine could put on your desktop.

The pity of it all is that none of this happened. Xwidget was always a poor man's Yahoo widgets, it pleased very few being buggy in almost all respects. None of the bugs were fixed, no documentation was written, no support given to its users, it was bundled with malware and abandoned. It had real promise but with some guidance Xwidget could have been a killer app. Unfortunately, it was not to be.
Current Project (very late) - some Christmas Baubles

I'm updating the baubles that I created three years ago to finish them off and get them 'out there'. They've just been populating my desktop and no-one else's.

Fig 1.0 - The help file for the baubles

Each plays a carol suited to a day in Advent, they fade in and out as your mouse passes over each, respectfully keeping themselves unnoticed in the background.

Fig 2.0 The desktop shown with the baubles bright and shiny (they fade to 20% opacity when idle)

I had hoped and have managed to largely finish them BEFORE advent ends...

You can get it here:…

I used RJTextEd exclusively to create this particular program along with Photoshop for the graphics. It is approximately 1,600 lines of code in 8 program files, mostly standard javascript with some XML descriptors. 155 separate images, baubles, advent calendar inserts, doors opened and closed, numbers, help files, scrolls &c.

A present for you this Christmas 2018.

In version 1.4 I am tidying up the baubles adding a few minor improvements:

o listing the current song's name in the scroll pop-up
o add an option to the preferences to toggle the display of the trackname
o remember and preserve the bauble's door open/closed state
o add an info window for updating the user when positions are successfully saved &c
o fixed a bug that occurs when restarting during the playing of a carol.

When these advent Baubles are completed, the aim then is to create a series Christmas Baubles for the twelve days of Christmas following the images as provided by the old song "On the twelfth day of Christmas my true love gave to me"...
Musical Christmas Advent Bauble Widgets
An advent or Christmas present for you!

A little late I am afraid as I had wanted to have it ready for the first day of advent. It has taken a little longer than expected as it was more complex that I imagined to iron out most of the bugs. It is still ready for Christmas!

Above is a quick screen shot of the Christmas Advent Baubles on my desktop.

Each bauble is individually moveable around your desktop, is resizable with the mouse wheel and plays a Christmas-themed tune when the inlaid door is opened to reveal a Christmas image. The baubles won't interfere with your desktop as they lay underneath all your windows and assume an opacity of 20% when idle.

The baubles being an advent calendar are dated for each day of Advent leading to Christmas. Click on each door for the gentle surprise inside.

These baubles will give your desktop a particularly Christmas theme.


Right click menus provide you with additional widget options and full help.

This is the first release of this widget and it has only been tested on three of our systems so far, Windows 7 64bit ultimate, Windows 10 32bit home and Mac OSX Sierra. We would appreciate feedback if you encounter a bug on your system.

Note: these are javascript widgets. These run in a desktop javascript engine freeing javascript from only running within the captivity of a browser, you will now be able to run any javascript widget on your Windows/Mac desktop as long as you have an engine installed.

You will, of course, need the Yahoo widget desktop javascript engine for this widget to run. Get Yahoo widget engine here.

So, on Windows the installation guide is simple, install yahoo widgets, extract the widget from the zipfile, double click on the .widget file and you are done!

On Mac OS/X it is a tiny bit more involved:
Instructions for running Yahoo widgets on Mac OS/X, all recent versions including Sierra.

Edit the following file: which is in /Users/xxx/Library/Preferences. Look for these lines: <key>DockOpen</key>

Change to false if it is true.

Then you should be able to start Yahoo! Widgets and the menubar item should appear. Widgets can then be started from the menubar or by double-clicking them in the usual way.


Note: The zipfile provided here as a download contains the yahoo/konfabulator widget ready to install.


The only condition for downloading and using is that you leave feedback. Please leave a message and rate the widget/icons as it is the only payment I get for creating this small desktop addition :D

You may use any of my images in your own creations but commercially only with my permission. In all cases I require a credit to the original artist using my name or pseudonym and a link to my own Deviantart page.
A poll was run in Britain in the wake of the Brexit vote over whether Britain is a divided society.

50% of the responders said it was, 50% said it wasn't...

That was a joke by the way.

Pheasant Casserole with a sword
Pheasant casserole, mushrooms, cabbage and ham, roasted colcannon with tom-toes and carrots honey-roasted in butter and garlic. As you'd expect tastes quite gamey.

Yes, that's a Roman Gladius in the picture, I was explaining Cicero to my youngest boy who is now taking Latin.

I knew her Father a long time ago, we both had a mutual friend who died and we lost touch. His daughter has done him proud.

Journal History


by acg3fly

I really like it. The icons are clearly the work of a professional. However, I don't see the over-arching 'theme'. They are all individ...


Add a Comment:
yereverluvinuncleber Featured By Owner Sep 24, 2018  Professional Interface Designer
Bloody Hell, I forgot.
SirIvyPink Featured By Owner Sep 24, 2018  Hobbyist General Artist

You Are Most Welcome My Friend.
Happy Birthday, My Friend.

Exzeedvelocity Featured By Owner Sep 23, 2018  Hobbyist Traditional Artist
Dude your entire gallery is awesome
yereverluvinuncleber Featured By Owner Sep 23, 2018  Professional Interface Designer
That's rather kind.
HipHopium Featured By Owner Sep 19, 2018
Thanks for the +fav;) (Wink) Nod  
tec192 Featured By Owner Sep 6, 2018  Hobbyist Artisan Crafter
Thank you very much for fave!)
yereverluvinuncleber Featured By Owner Sep 6, 2018  Professional Interface Designer
It was nice work. Feel free to submit to my groups.
tec192 Featured By Owner Sep 7, 2018  Hobbyist Artisan Crafter
yereverluvinuncleber Featured By Owner Sep 7, 2018  Professional Interface Designer
The tank designs to design-addicts.
(1 Reply)
CinnamonDevil Featured By Owner Jul 19, 2018
Thanks for the watch, I really appreciate it :)
Add a Comment: