Back to Normality – ish…

Phew! What a blast NaNoWriMo was! I know regular visitors here will have seen the protected posts kicking around, they’re the temporary storage for the project now formally known as Script WIP. NaNo didn’t so much provide me with a novel as 50,000+ words of basics for a script that I now want to polish up as a TV series for CBBC. There’s a ton and more of work to do on it before it’s anywhere near ready so if I’m not around as much as I could be, that’s what I’m working on.  On top of that there’s still 2 of us doing the work of 4 at work, split across 2 sites and the usual chaos that Christmas throws our way.

Christmas, in fact, is now taking up a lot of time.  And it seems to be taking up more time the more the kids grow up.  We’ve got our eldest in her Primary 7 pantomime on Wednesday, somehow having to juggle 6 of us into the 3 seats allocated – and knowing the space they’re putting on the show, this is going to be interesting as most of the other families going will be doing the same.  Last weekend we had 3 parties in 2 days, just about getting the kids tired of seeing Santa.  And if I hear “Merry Christmas, Everybody” one more time I’m going to hang the DJ.  Aaaaargh!  And all of these parties required presents!  Not content with the pile of stuff we’ve already bought, we needed an extra set of presents for each kid for each party!  Man, our local toy shops do well out of these things!  I’d love to say that we’ll be more organised next year and get some presents in advance but my better half hates having stuff clutter the house – and pre-bought presents apparently fall into the category of “clutter”.  I’m seriously considering going completely Sheriff of Nottingham next year and banning Christmas.

Several of my favourite Apps have had upgrades whilst I’ve been more offline than usual.  Tweetdeck has gone all blue and shiny and I don’t like it.  Fortunately, the CSS hacks I wrote about previously still work and I’ll be posting a complete CSS file to replace the one they’ve given us here as soon as I’ve worked out how I’d like my Tweetdeck to look.

Anyway.  Stuff and things are happening.  I’ll be back to the usual rounds of Galleries, Silent Sundays, Recpie Sheds and Reasons to be Cheerful for the forseeable – doubly so if I can get ahead of myself and write some stuff to go out automatically over Christmas.

Meanwhile, kick back, open a home brew and put on the new Arena album.  It’s very, very good.

Return to Chromedeck (@chromedeck @tweetdeck #chromedeck #tweetdeck)

One of the things I like about WordPress is that you can see what interesting search terms people have used to find your blog.  Fascinating stuff (for a certain, geeky, definition of “fascinating”).  Anyway, seems that Chromedeck comes up quite a lot and a couple of people are looking for ways to change the width of the columns.  When I first talked about Chromedeck, I said that this was something it couldn’t do.  Turns out I’m wrong.

If you’ve ever right-clicked on a page in Chrome, you may have spotted “Inspect Element” as one of the options.  I do this a lot, especially when I’m trying to work out why the stylesheet I’ve spent so long writing isn’t working properly.  Yesterday, I right-clicked on Chromedeck and discovered that it’s basically just a web page.  And because it’s a web page, there’s a stylesheet determining how it looks.

The screenshot below shows Chrome’s “Inspect Element” panel open with the right bit selected:

Chromedeck screenshotOver in the right-hand pane of “Inspect Element” is a list of the various CSS rules affecting what’s being displayed:

Inspect ElementLooking at this, you can see that it’s the file “chrome.css” that’s affecting the column width, and that it’s currently set to 324px.  If you jack this up to 500px (by clicking on the 324px in “Inspect Element” and typing in 500px), you get Chromedeck looking like this:

500px column width ChromedeckThe 2 extra columns I had have wrapped down and are off the bottom of the screen.  Not ideal, but if you’ve only got a couple of columns you should be okay.

None of the changes made inside “Inspect Element” are permanent.  The second you refresh the page, the original CSS file gets applied.  So if you want to make these column width changes more permanent (at least until the next update of Chromedeck) you need to edit the original CSS.

First thing to find out is the directory name Chromedeck will be hiding under.  Click on Chrome’s spanner icon, then “Tools”, then “Extensions” (or go to chrome://extensions/).  Find Chromedeck in the list and keep that window open while you browse your computer.

On Linux, the path to the directory containing Chrome’s extensions is:

~/.config/google-chrome/Default/Extensions

I’ll add in the Windows path shortly.

The extensions directory contains a folder for each of your extensions but none of them have very sensible names.  That’s where chrome://extensions comes in.  Each extension has an ID, and that ID is the name of the directory in the extensions directory.  Once you’ve got that, you’re almost there.  Inside the ID directory is a version number directory, inside that the css directory and inside that is chrome.css.  Finally!

The file chrome.css is a one-line monster.  But from the “Inspect Element” panel we know we’re looking for “width:324px” and that only occurs once in the file.  Find it, replace it with the column width of your choice, save it and refresh Chromedeck.  You should see your changes.

And that’s that done until Chromedeck gets updated.  You’ll know it’s been updated because you’ll be back to your default column widths, and you’ll have to go through all of this again to get your customisations back.

Of course, once you’ve made one change, it’s hard not to make more – you could change the font sizes, the background colours, really go to town on customisation.  Who knows?  Maybe Chromedeck will add in an option to use your own stylesheet in the future…

 

Enhanced by Zemanta