Quick[select] is a jQuery plugin for quick selection of common options in select boxes. Quick[select] uses the browser's native select list for its overflow, meaning it will work great on all devices.
by via jQuery-Plugins.net RSS Feed
"Mr Branding" is a blog based on RSS for everything related to website branding and website design, it collects its posts from many sites in order to facilitate the updating to the latest technology.
To suggest any source, please contact me: Taha.baba@consultant.com
Quick[select] is a jQuery plugin for quick selection of common options in select boxes. Quick[select] uses the browser's native select list for its overflow, meaning it will work great on all devices.
An intro block that slides out to uncover a gallery of portfolio items.
We’ve been experimenting with some motion effects to build a simple portfolio template. The idea is to show a gallery of projects as a separate, secondary module, with the first block still partially visible – just one click away.
The post Squeezebox Portfolio Template in CSS & jQuery appeared first on jQuery Rain.
PivotTable.js is a Javascript Pivot Table library with drag’n’drop functionality built on top of jQuery/jQueryUI and originally written in CoffeeScript by Nicolas Kruchten at Datacratic.
PivotTable.js’ basic function is to turn a data set into a summary table and then optionally add a true 2-d drag’n’drop UI to allow a user to manipulate this summary table, turning it into a pivot table, very similar to the one found in older versions of Microsoft Excel with a bunch of extra developer-oriented features and some visualization effects. With optional add-ons, the summary table can be rendered various kinds of charts, turning the pivot table into a pivot chart.
The post PivotTable.js : JavaScript Pivot Table, Chart, Grid Library appeared first on jQuery Rain.
The problem with placeholders is that the feature is not supported in IE 9 and below. This is a huge pain if you use placeholders as labels.This tiny jQuery-dependent plugin which enables placeholders in browsers that do not support the technology.The plugin takes care of textareas and text-oriented inputs, including password type.
The post jQuery Placeholder Polyfill with Password Support appeared first on jQuery Rain.
The Node Package Manager (a.k.a. npm) has given web developers easy access to a lot of awesome JavaScript modules and has made our lives considerably easier when trying to find and manage dependencies for our applications. It also makes it easy for developers to create and publish their own modules, meaning that other developers can grab them with a simple npm install -g your-tool
and start using them any time they want to. It’s utopia! Right?
Err, actually …
I will never say never use the -g
option when installing an npm module, but I do have to say that we are causing problems by using it too much. There are a couple reasons that I think we should cut down on our use of global module installation, especially in the case of build, test, or linting tools such as Gulp, Karma, JSHint, and countless others. I’ll be referring primarily to Gulp throughout this article because it’s quite popular and it’s fun to say, but if you don’t like Gulp, just mentally replace it with whatever you prefer.
First of all, global modules are not listed as dependencies in your projects, even though your project depends on them, which causes extra steps for others using your application. You know that you need to use Gulp in order to get your project ready for production, so you install it globally and use it. When someone else wants to start working on, or using your wonderful open source project, they can’t just type npm install
and get going. You end up having to throw directions into your README file saying something along the lines of
To use this project, follow these steps:
git clone
the reponpm install
npm install -g gulp
gulp
to buildI see two issues with this: firstly, you are adding the extra step of installing Gulp globally and secondly, you are running gulp
directly. I see an extra step that could have been avoided (globally installing Gulp) and I see that the user is required to know that your app uses Gulp in order to build the project. This first issue is the main one I’m going to address in this article, and although the second one isn’t as big of an issue, you’ll need to update the instructions if you end up switching tools. The solution I discuss later should fix both of these issues.
The second big issue relating to installing modules globally is that you can run into conflicts due to having the wrong version of the module installed. This is illustrated by the following two examples:
gulp
to build it, but runs into errors. This is because the person who cloned your project is either running an older version or a newer version of Gulp that has some breaking differences.gulp
and you experience errors because you’ve updated Gulp since the last time you touched the project. Now you are forced to update your build process to work with the new version of Gulp before you can make any more progress on the project, instead of putting it off until a more convenient time.These are potentially very crippling issues. Like I said earlier though, I wouldn’t make a blanket statement telling you never to install something globally. There are exceptions.
By default, on some systems, installing a npm module globally requires elevated privileges. If you find yourself running commands like sudo npm install -g a-package
, you should change this. Our beginners guide to npm shows you how.
Continue reading %How to Solve the Global npm Module Dependency Problem%
Android Studio is now the official IDE for Android development. In this video we look at how to download and install it, tour the interface an look at some of the tools and features it offers.
Continue reading %Watch: A Tour of Android Studio%