Geeky Shit

Google App Engine is Moderately Full of Win

Google App Engine has been out for a while and still is in a testing phase. It’s an app engine (duh) that contains libraries for web development and allows you to host your applications on Google’s servers. In the future, more languages will be available, but currently, the only runtime available is Python.

It has it’s ups and downs. You can use Google’s Google Accounts system as your authentication system, which, to me, is fucking amazing. I hate making user systems and like how things can be linked like that; I only need one account for Google and all of their servers and applications, and only have one password I need to remember and one set of information I need to keep up to date.

A huge plus? Most, if not all, of the handling and configuration is done in a file called app.yml. And you know how I feel about YAML. Here’s an example of my top-secret (more on that later) application’s app.yml file.

application: active-camo
version: 1
runtime: python
api_version: 1
handlers:
- url: /
  script: index.py
#- url: /get_data
#  script: resources/get_data.py
#- url: /data
#  script: data.py

What does this mean? It supplies the application’s identifier, the version (you can have multiple versions and roll back to an older one should you need,) the runtime (right now, only Python,) and the API version (right now, only 1.)

Below are the handlers for this application. See the comments? You can do that, it’s YAML! This means that / (index with no filename) will be handled by index.py. Isn’t that great?

There are also some downsides, though. Python naturally isn’t very good at handling files, which means that, in this case, I need to keep just about every file separate. I can’t use include 'header.php'; as I normally would.

And about my top-secret project? If I told you, it wouldn’t be a secret. But it’s probably not that interesting, don’t worry about it.

People STILL Use Tables?

As I’m sure you know, I strongly oppose the use of tables for website design. I stopped using tables ages ago and assumed the rest of the web had, too. But I was dead wrong. I was on a message board and spotted a thread about a person looking for web design help. Somebody suggested he not use tables, and I agreed.

But we’re in the minority. Two or three people immediately jumped on us and told us about how wrong we were, one went so far as to say I’m just a stereotype of a wannabe developer. It’s a shame that it’s actually 2008 now and we still have people who’ve no idea what web semantics are.

Tables are made for tabular data. As in, to display data that belongs in a table. W3C has said this numerous times. But why do people still make websites using tables?

• It’s easier. Tables aren’t as difficult to use as semantics web elements.
• Big names use tables. Google, MySpace and other popular websites all sport table-based designs.

As a public message to all table-users:

Sulfuras: Another Remake

I’ve become discouraged. Sulfuras isn’t working out like I’d intended. The system itself is working quite well (and coded beautifully if I do say so) but I’ve been thinking “why?” Most guilds can just use EQdkp. So I copied Sulfuras to my backup directory and who the hell knows what I’ll be making of it.

Fixing Scrolling Issues in WicketPixie

Out of the box, Chris Pirillo’s WicketPixie theme (the one you see on this site and his) feature some nasty scrolling issues. It’s very choppy and slow, and makes some sites nearly unreadable! But, the problem isn’t foreigners, it’s CSS elements with fixed attributes.

For comparison, scroll from top-to-bottom on both my website and Chris Pirillo’s. The difference should become fairly apparent!

Naturally, WicketPixie features two fixed elements. The background and the bar along the top. This means there are two steps in solving the scrolling issues, neither of which are very hard at all.

The first is going to the Design tab and viewing the WicketPixie options. Make sure Background Image Position is set to scroll, not fixed. Pixie was quite stubborn when I was changing this and it required a few attempts before the options actually saved. Be warned that the checkbox at the bottom of the options page becomes checked mysteriously regardless of your current settings. Be sure to uncheck it if you require before saving your options.

The second is slightly harder, but still no problem. It involves editing some CSS, which cannot be edited through the standard Theme Editor, but must be edited through FTP due to it’s location in wicketpixie/css/screen.css. Find the CSS for #topbar (it’s near the top!) and comment it out. This is done by adding /* before the # in #topbar and a */ after the } at the end of that block. This is so your changes can be reverted easily.

Next, paste the following anywhere in that same CSS file.

#topbar {
	position: absolute;
	top: 0;
	float: left;
	margin: 0;
	width: 100%;
	padding: 5px 0 19px;
	background: url("../images/topbar-bg.png") repeat-x 50% 100%;
	z-index: 999;
}

And voila! Your scrolling issues should be fixed.

Update: Zavrion has uploaded the edited screen.css file. Download it and upload it to WicketPixie’s css folder to apply the CSS changes above. Download!

Free Template: Daybreak

Daybreak, the first of my free templates, was created a while ago, but not released. It’s a black- and yellow-styled template built with valid XHTML 1.0 Strict and valid CSS. Since it’s completion, it has been used by 3 developers from the Zybez community.

Daybreak is free for both personal and commercial use provided the credit in the footer remains intact. The author meta tag can be removed at will. Additionally, the sidebar can be positioned below the navigation bar instead of overlapping it by uncommenting an existing CSS rule.

Live Demo - Direct Download