Talk:Theme development guide

Is themeing spelled wrong here??

I checked both http://m-w.com/dictionary/themeing and http://m-w.com/dictionary/theming, along with wiktionary, and came up with no word for either one. Probably should be called Theme Guide as a noun instead of as a verbal expression. (P.S. Don't forget to sign your comments). --Gregturn 18:57, 5 February 2006 (UTC)

I concur: let's move the page to theme guide. --Baylink 18:59, 5 February 2006 (UTC)

I should have read the damn page first, folks. I was worng: this isn't about *themes*. It's about *making* themes. IE, it *is* the "themeing guide". So, much as I hate to say it, we should resolve the spelling issue, and move it back. --Baylink 21:26, 6 February 2006 (UTC)

I still contend "themeing" isn't a word. I thought I understood what this article was about. Maybe we should call it "Theme development guide", or "Custom theme development" so no one confuses what this article is supposed to be about. --Gregturn 02:42, 7 February 2006 (UTC)

Themeing would be the gerund verb of Theme; the process of applying themes to something (or by extension, creating them). I'm fine with those alternatives, though, Greg. --Baylink 03:59, 7 February 2006 (UTC)

Okay, I moved the article to what I think is a good title, and also wrote an introductory paragraph, giving fair credit to the word "themeing". I scanned google, and found this word in common usage, so that should make all parties happy. To cap it off, I even corrected the original author's spelling of "theming" to "themeing" which would appear to be the proper format. :) --Gregturn 04:44, 7 February 2006 (UTC)

If you also check "Theming" with Google, you'll see that it is 4 times more common than the mis-spelling "Themeing". The concept of theme-creation as a verb hasn't made it into the dictionary yet, so there isn't a definitive choice.

Reference to paths

After seeing how many people are simply incapable of finding their butt.jpg with both processors, I begin to think that perhaps we should start changing the paths mentioned explicitly in the documentation to use a bit of abstraction. For instance, /usr/local/share/mythtv/themes all well and good to tell someone, but most distros (and almost all binary packages) use /usr/share/mythtv/themes, and believe it or not this sort of thing confuses the people who come into #MythTV-users. It might be more useful to start saying ${prefix}/share/mythtv because this drops a hint into the mind of the reader that the top of the file hierarchy for these files is not actually /, but a particular location specified by the builder which may or may not be the same on their system. --Dagmar 05:01, 10 December 2006 (CST)

MediaWiki doesn't like SVG files?

I suppose there's some way I'm unaware of to upload zipped files and assign them a special thumbnail, but at the moment I've got no clue about that (and am hesitant to use an opaque container for something like this anyway). It's kind of a bummer that the MediaWiki won't accept SVG images, since Inkscape and SVG is what I used to create these cheatsheets to begin with. Still, people using Inkscape to do their layout can still just import these images into Inkscape just fine. --Dagmar 07:46, 10 December 2006 (CST)

text & activetext

I'm about to submit a patch to provide <halign> and <valign> attributes, so just to make it explicit (before I forget or it gets misdocumented) they will both have possible values of "left", "right" and "center" --Dagmar 0501 CST, January 30th, 2007.