For my CS332A final, I decided to make an RSS feed that listed my most recently updated projects for the eFiction script including skins, modifications, and plug-in type functions such as blocks and panels. I installed it in the header of my personal site (rather than crux, which seems to hate me right now) so RSS capable browsers would automatically make it available to my users.

XML Project Feed: project.xml

I originally wanted to do both an RSS feed as well as an XML document listing all my available projects. The RSS feed came together quickly, though I did have some problems getting it to validate correctly. (I kept wanting to use 4 letter month abbreviations and it took me a while to realize it wanted only 3 letter abbreviations.) Unfortunately, I didn’t have the same luck with my project list. I guess I didn’t understand XSL as well as I thought I did, because I’m having a problem figuring out what I’m doing wrong.

If you’d like to see my project list XML document, you can find it here: full_project_list.xml

I do plan on finishing it up eventually, I really do need something to keep my projects straight. Once I finish up the rest of my finals, I’ll probably return to it just to see if I can finish before midnight.

Just thought I'd share some assorted things I've been learning in my DHTML/XML class. These more or less come from my class notes and textbook. Hopefully this makes sense, I'm tired and not feeling especially great.

Most modern browsers handle style sheets, but did you know they read your styles in a very specific way?

Here's the order that CSS styles are handled:

1.) Anything with the !important tag next to it is given top priority.

Example:

By doing this, you can also override any stylesheets the visitor is using with their browser. Just be sure to use this wisely and to not abuse it. (Also be sure to put it BEFORE the semi-colon or it may not work right.)

2.) Does the style sheet belong to the Visitor or Author?
Most browser's today allow will favor their user's settings. That means that if they're using their own style sheet, it'll get higher priority than your's.

3.) The more specific the rule is, the more important it is.

There's an actual scoring system used to determine this:

• #IDs are the most specific. (100 points)
• .classes are medium (10 points)
• HTML tags are the least specific. (1 point)

These can also add up.

For example:

• DIV = 1 point
• .login DIV = 10 + 1 = 11 points
• #header DIV = 100 + 1 = 101 points
• #header .login DIV = 100 + 10 + 1 = 110 points

That would mean that the last one would get highest priority because it's the most specific.

4.) Last rule in the style sheet

The further down the page a set of css definitions are, the more important they are. In other words, the last thing in your style.css file is actually ranked higher than things at the top.

5.) Existing or inherited attributes are the last things considered.

Existing attributes: the the bold tag normally makes something bold, italic tag makes things italic. These sort of tags already apply a style to any text you use them on.

Inherited attributes: For example, if you embed one tag inside another, the inside tag inherits the style from the outer tag.

So what happens when I get stuck on a web design? I turn it into a wallpaper. ^^;

This was a vector design that was intended to be part of my Naruto-inspired skin for Lunaescence but it is just not behaving. I end up despising each and every layout configuration I try.

I set out to create my own rendition of the Rasengan jutsu using ONLY vector graphics, no images from the franchise. Here I took those courses and I've never posted anything to show what I learned or even tried challenging myself. I also wanted something I could put in my design portfolio that wasn't overtly anime or manga themed. (hah.)

Created With: Macromedia Fireworks / Flash
Total time: 12+ hours

Naruto belongs to Masashi Kishimoto, not me!

Be sure to backup your database and files before you begin this or any other mod.

Description: This mod will put a male, female, or undisclosed icon in the author profile. I'll let you decide if undisclosed means "Not Telling" or just what. It is up to you to provide your own icons.

This mod was originally created for JanAQ as part of her requested profile mods.

I can't take full credit for this mod, I spent a lot of time trying to figure out how to get it working before I asked for help. Tammy replied and told me how to get it working.

As usual, my line numbers are approximate and only meant to put you in the general ballpark.

Requirements: eFiction 2.0

Difficulty: Easy

Modification History:
EDIT: Stopped working for some reason, so I changed the MYSQL declarations.
EDIT: Clarified my instructions for the database
EDIT: Changed my instructions so I didn't overwrite some of my other mods. If it's confusing, feel free to ask.
EDIT: Trying to fix the error Seiji found
EDIT: Tammy got it working! embarassed
EDIT: Fixed a typo from the instructions for line 389. Sorry!! embarassed
EDIT: Added the tpl tag
EDIT: 29 June 2006 -- Updated post format to match post requirements; also began an update to bring the mod up to the current version.
EDIT: 29 June 2006 -- Updated the modification to match the current release. Please let me know if you have any difficulties.

Files Involved:

• user.php
• viewuser.php
• languages/en.php
• user.tpl

Modification & Support Link: eFiction.org

Instructions:

Description: This mod adds a manditory disclaimer field to every story form. If users do not fill in the disclaimer, they'll receive an error just like if they left the summary or title blank.

This mod is as involved as my story type mod, if not a bit moreso, due to the fact that it has to be made manditory. I strongly suggest you read through my instructions before you actually attempt this modification.

For this mod, I used files from the latest release. (2.0.7, 28 Aug 2006 patch) The line numbers are all approximate and will likely change as you progress through this mod. Please consider them simply a guide to put you into the general area.

This mod is UNTESTED. In theory it should work, but I have not tested it on my own site.

Requirements: eFiction 2.0.7 (28 Aug. 2006 Patch)

Difficulty: Advanced

Mod History:

18 Sept 2006 -- Mod created as per request by fanfiction world

Files Involved:

• Database modification
• stories.php
• viewstory.php
• languages/YOUR LANGUAGE.php
• skins/YOUR SKIN/viewstory.tpl

Modification & Support Link: eFiction.org

Instructions:

Description: This is a quick and dirty version check script for eFiction 2.0. It simply shows your currently installed version of eFiction, the current version, and then the release date for the last patch along with any important notes or news relating to that patch.

Requirements: eFiction 2.0

Difficulty: Easy

Mod History:

25 Aug 2006 -- Concept for patch suggested on eFiction New Feature forums and first attempt at creating mod made.
07 Sep 2006 -- Mod correctly checks and formats returned text.

Files Involved:

• admin.php
• admin/version_check.php

NOTE: Please be sure to back up your files and database before you begin this or any other mod.

Download Link: version_check.zip

Modification & Support: eFiction.org