RewriteEngine on
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME}\.php -f
RewriteRule ^(.*)$ $1.php

The nice thing about this is that it doesn’t affect querystrings.  With this solution, both of these URLs are effectively the same:

http://example.com/page.php?id=123

http://example.com/page?id=123

Of course, the caveat is that you don’t have “clean querystrings”, but it’s a reasonable trade-off between “clean” and configuration.

For a long time, we’ve been asking for your feedback and directing you to post them on our UserVoice page.  In theory, this was a good idea, as it allowed the community to suggest new features and vote on their priority.  This gave us a good insight into where you wanted us to take Surreal.  However, over time, we’ve come to realize that UserVoice isn’t the solution we were really looking for.

For one, you were thrown into an entirely new interface and required to register a separate username and password.  Many users simply stopped at this point, which means that if they didn’t contact us directly we never got the chance to hear their feedback.  You shouldn’t be forced to register with another site just to tell us what you think about our service.

We also felt that UserVoice’s interface doesn’t fit well with Surreal’s mantra.  Surreal is simple.  Providing feedback to us should be just as simple.  So from now on, we encourage you to send all your comments, suggestions, and all other feedback directly to us through Surreal’s Help & Support section.

We want to hear from you directly, and we want to take back that personal touch that we lost when we started sending folks elsewhere to tell us how we were doing.

In Surreal CMS version 3, we tried to solve this problem by using only the Insert/Edit Table button in the toolbar.  For other functions, the user just needed to right-click on the table to bring up a contextual menu with additional table options.  For the most part this worked, but we saw a lot of support requests from people who never even knew there was a context menu available.  In addition, the use of context menus in web applications is still a rather controversial matter.

So with the development of Surreal CMS v4 underway, we needed a better solution to this dilemma.  Here are the facts that we faced:

• Most people won’t be working with tables in the CMS
• At the same time, a lot of people still need this functionality
• The built-in TinyMCE tablecontrols feature dumps 12 buttons into the toolbar—every option is essential when working with tables, but it clutters the toolbar and intimidates novice users

Our solution was to create a SplitButton control that combined all of the necessary options into a single dropdown.  When the button is clicked, the Insert/Edit Table dialog appears.  When the arrow is clicked, you get the rest of the table options neatly organized in a TinyMCE dropdown:

The plugin is very lightweight and contains only one small JavaScript file—no CSS, images, or language packs required.  The plugin is also theme-ready and localization-ready, as it uses standard TinyMCE classes and terms.

We think that this is a very elegant solution for a very much overlooked UI problem, so for the sake of better usability in apps that use TinyMCE, we have released the code under the MIT license for all to use and share.  If you’re interested in this plugin, you can download and contribute to it on GitHub.

var isMobile = {
    Android: function() {
        return navigator.userAgent.match(/Android/i) ? true : false;
    },
    BlackBerry: function() {
        return navigator.userAgent.match(/BlackBerry/i) ? true : false;
    },
    iOS: function() {
        return navigator.userAgent.match(/iPhone|iPad|iPod/i) ? true : false;
    },
    Windows: function() {
        return navigator.userAgent.match(/IEMobile/i) ? true : false;
    },
    any: function() {
        return (isMobile.Android() || isMobile.BlackBerry() || isMobile.iOS() || isMobile.Windows());
    }
};

While this doesn’t account for all mobile platforms, it will pick up the most popular ones out there.

Examples

To check to see if the user is on any of the supported mobile devices:

if( isMobile.any() ) alert('Mobile');

To check to see if the user is on a specific mobile device:

if( isMobile.iOS() ) alert('iOS');

 ##
 ## www.domain.com --> domain.com
 ##
 RewriteEngine On
 RewriteCond %{HTTP_HOST} ^www\.(.*)$ [NC]
 RewriteRule ^(.*)$ http://%1/$1 [R=301,L]
 

 ##
 ## domain.com --> www.domain.com
 ##
 RewriteEngine On
 RewriteCond %{HTTP_HOST} !^www\.
 RewriteRule (.*) http://www.%{HTTP_HOST}/$1 [R=301,L]
 

If you plan on using these, you’ll need to make sure you have the mod_rewrite module enabled on your server.

Here are just a few:

• convert() – converts an image from one format to another
• flip() – flips an image vertically or horizontally
• rotate() – rotates an image at the specified angle
• brightness() – adjust the image’s brightness
• contrast() – adjust the image’s contrast
• grayscale() – makes the image black and white
• blur() – blurs the image at the specified level
• watermark() – creates a watermark effect using another image
• text() – adds text to the image

In addition, there are some special methods for resizing and cropping:

• resize() – resizes an image to the specified values
• resize_to_width() – resizes an image to the specified width
• resize_to_height() – resizes an image to the specified height
• resize_to_fit() – resizes an image to fit within the specified dimensions
• crop() – crops an image
• square_crop() – crops the image into a square of the given size

Download

This project is actively maintained on GitHub. Please submit all issues and contributions to the project page. Licensed under both the MIT and the GNU GPL licenses.

Download the latest version from GitHub

The goal of this plugin is to show passive notifications that can be easily dismissed with minimal distraction.  Rather than using a dialog or a distracting overlay, the notification appears on screen for a specified duration, and then fades out.  The user may also dismiss the notification simply by clicking on it.  At the present time, this plugin does not support multiple notifications.

Screenshot

If you’re interested in using this in your own projects, head on over to GitHub and download the source.

Demo & Download

This project is actively maintained on GitHub.  Please submit all issues and contributions to the project page.  Licensed under both the MIT and the GNU GPL licenses.

Demo | Download the latest version on GitHub

It can be frustrating, however, if you ever come across that need.  If you’re one of those individuals, open up a terminal window and navigate to your local Git repository.  Once there, simply run these commands, replacing [tag] with the tag name:

git tag -d [tag];
git push origin :[tag]

And if your tag has the same name as one of your branches, use this instead:

git tag -d [tag]
git push origin :refs/tags/[tag]

Of course, these steps assume that you have Git running on your local machine.

Thus, jQuery MiniColors was born.  A simple, compact color picker that complements a text or a hidden input control.

The plugin adds a trigger next to the input which is customizable via CSS.  The included icon is a modified version of the UI color picker icon included in the Fugue icon set.  (You may use it for free with attribution or create your own icon instead.)

When the trigger is clicked or when the input gains focus, the color picker appears.  Users can either type in a hex-color or select one using the control.  The control disappears when the user clicks anywhere outside of the selector or tabs out of the input.  If specified, a callback is fired whenever the color value changes.

Initializing

$("INPUT.color-picker").miniColors({
    change: function(hex, rgb) { ... }
});

Methods

Methods are called like this:

$("INPUT.color-picker").miniColors('methodName', [value]);

Available methods include:

• disabled [true|false] – disables/enables the input and the selector
• readonly [true|false] – sets the readonly state of the control
• destroy – removes the color picker and restores the input to its original state
• value [hex string] – sets the color of the color picker and updates the input value

Events

The change event is called whenever the color value changes (see example above for an implementation example). Two arguments are passed to the callback function that contain hex and RGB values of the selected color.  The context of this within the callback refers to the original input control.

Note: While using the mouse to select a color, the change event may be called frequently.  It is recommended to keep any behavior that occurs in this callback to a minimum to minimize performance issues.

Demo & Download

This project is actively maintained on GitHub.  Please submit all issues and contributions to the project page.  Licensed under both the MIT and the GNU GPL licenses.

Demo Page | Download the latest version from GitHub

The plugin works by piggy-backing your existing SELECT controls.  Since the original controls aren’t destroyed (they’re hidden), you can easily integrate this plugin into just about any existing form. The plugin degrades gracefully, as users without JavaScript will see the default SELECT controls.

Plugin Features

• Easily replace existing SELECT controls
• Supports OPTGROUPs
• Supports standard dropdown controls
• Supports multi-select controls (i.e. multiple=”multiple”)
• Supports inline controls (i.e. size=”5″)
• Fully accessible via keyboard
• Shift + click (or shift + enter) to select a range of options in multi-select controls
• Type to search when the control has focus
• Auto-height based on the size attribute (to use, omit the height property in your CSS!)
• Tested in IE7-9, Firefox 3-4, recent webkit browsers, and Opera.

Please refer to the main source file for implementation examples, a list of known issues, and the change log.

Demo & Download

This project is actively maintained on GitHub.  Please submit all issues and contributions to the project page.  Licensed under both the MIT and the GNU GPL licenses.

Demo Page | Download the latest version on GitHub