Skip to main content

Writing a Windows Gadget is hard!

Windows Gadgets suck ... Microsoft has recently discontinued support for Windows Gadgets - in favour of Apps. So any Gadgets fans/freaks out there who might enjoy the challenge of writing a gadget ... like myself ... are out in the cold when it comes to sharing gadgets, or hoping for support on some Sidebar issues ...

Well, it's not like they dismantled Windows Sidebar in Windows 7 ... but it looks like there is no gadget support in Windows 8 ... which kind of sucks because gadgets filled the instinctive need of many computer users to clutter up their desktop with cool techno-looking bars and charts and dials and switches etc...


So, Microsoft, in their infinite wisdom, decided to integrate most of the popular gadget functionality into the actual OS, instead of these little unrelated boxes floating around causing havoc with system resources...

Well, disregarding everything I just wrote ... I decided to write my own gadget - it's still a work in progress, so don't laugh too hard... but I started by studying the gadget format - not too tough to master, basically a folder structure with some XML defining the main files...

Then there is the gadget syntax - specialized html tags to identify elements of the gadget .. not too bad...
Then there is the compulsory JavaScript - luckily I was already learning that... so not too bad there...

Then there is the docking functionality... let me start by telling you that all the examples on the internet have one or other subtle flaw which my SideBar doesn't like ... while debugging the docking code I suddenly "lost" my gadget and it would not appear in the SideBar anymore .. well, ok, I mistyped something - but it's still frustrating to not have anything to debug with besides the tools which come with Chrome ... Oh, and did I mention that gadgets rely on the ActiveX components built into Explorer?

That means that you can debug MOST of your gadget and Javascript code using Chrome ... but for all those Microsoft-specific things there is no actual way to DEBUG a gadget using Internet Explorer ... which is a shame because I rather enjoy playing with my TODOList gadget ... it's very simple, right now it can be docked - which shows a smaller list or undocked - which shows the same list in a larger view ...  fun times :-)
My main plan is to refine the todo list to the point where I enjoy using it - and it will be my default app, since I am a programmer and my mind is inordinately full and prone to dropping details after all these years of juggling crazy amounts of things around in short term memory - plus there are a lot of distractions all around me, since I am the only programmer IN THE COMPANY... which is kind of awesome, The Lone Coder lol!

Once the gadget has been refined to my liking, I would like to use it as a base for a gadget game I would like to write ... something like the old NES Star Force ... which is another mission on its own - but well worth the fun...

So, gadgets suck, but the joy they bring definitely makes it worth the time and effort that goes into creating one...

Comments

Popular posts from this blog

Finding a Game Engine is Hard

Well, if you're new here - congratulations on finding the most useless blog on the planet. If you're not new here, thanks for coming back to another installment of "And he just keeps moaning!", this weeks episode deals with how hard it is to select a Game Engine for your development needs. As I've mentioned in the past, there are many things to consider when developing a game: Storyboarding Specification document Game Engine Resources (art / sound / levels) Time constraints Return on Investment Since I've preached about the Specification Document all throughout my last post , I'll save you a little bit of reading by saying it's nearly the most important part of the entire process - nevermind having a compelling game - without the specification document, nothing gets built. Storyboarding is kind of like the specification document, but it allows you to draw little screens of the game as you imagine it to be, without too much detail.

A few thoughts on Game Development

For those of you who follow my blog, you'll notice that I talk about building games, but I never really release anything useful or fully playable. I'm more interested in studying the individual parts of game development, without really caring about building a game as a whole. Well, for the most part this is perfectly acceptable, as I'm not a game developer by trade, and my bread and butter comes from being a utility developer. I've defined utility developer as someone who codes a variety of things without specializing in any specific discipline. As a self-taught developer, it's been hard for me to pivot into a role where I'm classed as a game developer by trade. This is all good and well, but I still want to talk about game development as a whole - specifically how to get a game off the ground. If you've been following any blog about game development, or any programming course which walks you through the process, you've most likely heard of all the jar

XBOX ONE Game Dev is supposed to be hard.

So I recently took the plunge and joined the Xbox One Creators Program with Microsoft. It turns out that it's supposed to be incredibly hard to build these little games we see all the time, and for the most part, it is. Not only do we have to deal with the fact that the XBOX One does not use the stripped down PowerPC architecture that the Xbox360's used to run on, we now have to contend with the fact that it's basically running Windows 10. I remember the good old days when win32 and GDI (Graphics Device Interface) were sufficient to get a decent game running on a Windows PC - especially if the game wasn't too resource intensive. Then came Direct(X/3D/2D/11/12) with all its COM (Component Object Model) Glory -> which, perhaps most asinine of all -> is still being used today. Getting into the creators program costs a little bit of money, and that's mostly to keep the chancers out and cover administration fees. After that you really only need to abide by the