Apple Press Conference 2010 Predictions

iTablet, Iphone OS 4.0, Verizon Iphone 4G

The apple press event is mere hours away, so I thought I'd make some predictions before the event takes place. The biggest, and most important to me, is a Verizon iPhone

iTablet

• Netbook sector tablet computer
• Multi-touch interface
• $600 Price Point

iPhone OS 4.0

1. Multi-touch API for system wide gestures
2. Multi-tasking
3. Increased performance

Verizon iPhone / iPhone 4G (4th Generation, not 4G wireless network)

1. CDMA Version for Verizon's network in June 2010
2. 64GB SSD model / $300
3. Faster web rendering performance

These are my predictions, what do you think?

Crysis =Free Weapons= Server Mod

Crysis free weapons server mod, strength mod, speed mod, and invisibility extender. Type the following commands into the server console or (~) if you're hosting the game. Play around with different values, and have some fun!

The (almost) free weapons command:

g_pp_scale_price = 0.01
This sets the prices very low, but not to 0. You can set the prices to 0, but this will cause weapon sets not to load properly (because they use the prices, for some reason).

Super fast suit commands:

g_suitSpeedEnergyConsumptionMultiplayer = 0.01
This makes your suit's speed mode last MUCH longer.

g_suitSpeedMultMultiplayer = 10
This makes your suit MUCH faster

g_suitCloakEnergyDrainAdjuster = 0.05
This makes the suits invisibility mode last a lot longer

Super strong Suit Command:

cl_strengthscale = 150
Makes punching cars/tanks/trucks a whole heck of a lot of fun. Don't let any of the opposing team punch you!

Inudge.net Adobe Air App

Just made this track messing around, pretty cool application, you can share, edit and listen to anyone's music

XML file for Joomla Front-end editing

Phing build file for automatically building the Component/Plugins for Joomla front-end editing

Adjust the file paths to match your development environment (the following are on a windows XP vm running WAMP)

<?xml version="1.0" ?>
<project name="testsite" basedir="." default="main">
 <property name="package"  value="${phing.project.name}" override="true" />
 <property name="components" value="C:\wamp\www\Joomla Dev\Joomla 1.5 Source\components" override="true" />
 <property name="plg_sys" value="C:\wamp\www\Joomla Dev\Joomla 1.5 Source\plugins\system" override="true" />
 <property name="srcdir"   value="${project.basedir}" override="true" />
 <!-- Fileset for all files -->
 <fileset dir=".\components" id="compdir">
 <include name="**" />
 </fileset>
 <!-- system plugin -->
 <fileset dir=".\plugins\system\frontendeditor" id="sysplgdir">
 <include name="**" />
 </fileset>
 <!-- content plugin -->
 <fileset dir=".\plugins\content\articleeditor" id="contplgdir">
 <include name="**" />
 </fileset>
 
 
 <!-- Main Target -->
 <target name="main" description="main target">
 <copy todir="${components}">
 <fileset refid="compdir" />
 </copy>
 <copy todir="${plg_sys}">
 <fileset refid="sysplgdir" />
 <fileset refid="contplgdir" />
 </copy>
 </target>
 
 <!-- Rebuild -->
 <target name="rebuild" description="rebuilds this package">
 <delete dir="${builddir}" />
 <phingcall target="main" />
 </target>
</project>
 

Accessible Website Design

How do search engines & people with visual impairments see your website's content?

One key to creating successful, and accessible websites, is to make them readable, and usable by screen readers. The benefit to testing a website using a text browser like Lynx is that you can test a website's rendering to make sure that blind people and search engines alike can index your content. One accessiblity key that I include with all of my website designs is a main menu and skip to conent link, which can be seen in the following Lynx screenshots:

The purpose of these links, is that it allows visitors using a screen reader to quickly skip to the site's content, or navigational menus. This allows them a much easier browsing experience on your website. This is especially important if you have page style <img> tags, and have ALT content specified for them, as this allows users to quickly skip this needless information.

How do you make those links not appear to a traditional user?

The key to making the links invisible to a graphical web-browser lies in giving the link a class that allows us to style it in CSS.

<a href="#mainContent">Skip to Content</a>

Here is the link with a class applied to it

<a href="#mainContent" class="accessibility">Skip to Content</a>

And the CSS that will hide this link from browsers:

A.accessibility
{
  display: none;
  text-indent: -10000px;
}

There you have it, a more SEO friendly, accessible webpage!