The Ono list Pager aims to provide standard code for the paging logic, while the transitions are customizable and extendable. That way the plugin can adapt to a particular design without you having to rewrite the basic stuff. But that’s already the advanced stuff. The Ono List Pager already has a few built-in, configurable transition types, so you’ll most likely just pick some example code from the demo page and go on with your life.

Extending the Ono List Pager

For the more adventurous types: creating your own transition shouldn’t be that hard. It is done by writing a piece of code called an animation object. You can start with a template of the animation object, or you just rewrite an existing one. I do not recommend to write your own animation object though, because the interface of those object can still change during development. In case you do write an animation object I’d like to hear it from you. maybe it can be become part of the plugin.

Open source and available on GitHub

The Ono List Pager is free and its project is available on Github, so go right ahead and make it your own.

Browser compatibility

My aim is to make the library run on all major browsers: IE7+, Firefox, Safari, Chrome and most likely Opera.

Related posts:

1. The jQuery plugin Ono List Pager reached version 1.0!
2. New release: Ono List Pager 0.5
3. Ono List Pager 0.8 is out
4. New download location for Ono List Pager

Creating something from scratch can be empowering. It also gives a sense of control, because you can determine what the specifications should be of a product. Better: you don’t only know the specifications by heart, you also know just what strings you need to pull in your code. Getting to know a product that you didn’t code from scratch seem hard to master. And it can even harder to know it’s limitations. That’s not a situation that you want to be in, when talking to a customer. And so it seems better to stay in control and build an application of your own for your own needs.

A CMS for everyone

And so in-house coded CMS systems pop-up everywhere. But why? Are the ideas of those companies about Content Management Systems so different compared to what is already on the market? Most likely not. In many cases the euphoria of having your own CMS will turn to into a slowly simmering frustration because the time needed for bug fixes and feature request doesn’t match at all with the time that’s available.

We all know that creating a product needs time. But what we tend to forget is that keeping a product “healthy” and up-to-date also costs a lot of time in the long run. And so we have a plethora of CMS systems with loose ends and incomplete functionalities. Most of the time with an unfinished “help”-function.

For years I was accustomed to do as much as you can yourself. But now that the internet is getting bigger and bigger, you see companies specializing. Some companies are focusing on only one or a few products like a CMS, while the creators of websites ask themselves: “Am I better in building a CMS or in creating websites?” In most cases it’s the latter. And so it’s better to find a product that helps you to do the job fast instead of slowing you down.

Example: a quick flash video player

Now you may think that a CMS is an obvious thing you shouldn’t build yourself because the codebase is so large. Well, lets take something that needs less lines of code: a simple Flash video player. Many companies have developed their own Flash video player. Because it’s just relatively easy to do. But again: why? Most of the time such a in-house coded player has minimal documentation, if at all. And if you find documentation it’s likely out of date. What really bugs me if you’re asked to just “Fetch that player from our previous project”. Like that’s an acceptable codebase.

I recently decided to go with the open source Flow player. I fell for the various options to customize the player. Soon I discovered all kinds of advantages you wouldn’t have with your own code: Forums, wizards and extensive documentation. I could send a designer a link to a wizard that enables him to skin the video player at a basic level. I also could pass the player to another team member without having to explain every step in the code. The documentation is online, help yourself. Let me continue with my work.

Another example: Javascript libraries

Libraries really can speed up your work. They do not only provide lots of canned functionality, but libraries like Prototype, Mootools and jQuery can also really speed up your own coding. jQuery really helped me to code faster, more stable and in less lines of code. It made coding in avascipt even more fun.

There are lots of resources out there. As a web developer you need not only to know your code languages, you also need to know when to use some existing code and know where to find it.

No related posts.