I’ve recently released the first version of my jQuery Cascading Dropdown plugin. You can find it on my Github page located here:
jQuery Cascading Dropdown
The plugin allows you to implement a cascading dropdown using multiple select boxes in which one select box depends on the input from one or more separate select boxes. Once one or all (depending on the configuration) required select boxes contain a value, it will trigger an event that will fire off the dependant select box so it will fetch its own list.
It’s free to use, so feel free to download it, use it, even abuse it, as long as you keep the copyright info intact.
Throughout my career as a web developer, I’ve come to realise that building a website is a lot like cooking. Everything needs to be just right, and that there is a certain balance that needs to be kept. Get it right, and you’ll be serving a Gordon Ramsay dinner - rich, elegant and enjoyed by all. Get it wrong, and you’ll be serving a fast food dinner - greasy, bloated and no good to anyone.
It’s important to think about what you actually need as it’s very easy to get lost and end up with a website that actually have more features than you actually need.
I have compiled a list of guidelines that I personally use when starting a new project.
Geta has released yet another open source EPiServer CMS module. This latest module allows EPiServer administrators, as well as anyone with access rights, to manage the cache for EPiServer sites.
- One-click cache clear- Clear EPiServer site cache with just one click.
- Selective cache entry deletion - Select and delete individual cache entries.
- Cache entry value display - View the contents of cache entries.
- Multiple server support - Manage cache for multiple servers from a single node.
I’m currently working on a small NuGet module for EPiServer CMS, and I thought it’d be cool to implement a RESTful API using the ASP.NET Web API. However, as you probably already know, you need to make certain adjustments to the Global.asax file to set up some routing so that any requests made is redirected to the appropriate controllers.
This is fine if you’re implementing Web API into your main project, but not if you’re trying to get it working in a 3rd party module. You really don’t want anyone who installs your module to have to unnecessarily edit anything on their end. It’s just bad design.
Every now and again I get into this situation where I have a list, and some JS function will retrieve more stuff via Ajax to insert into that list. This is normally fine if you stick to normal lists, but once you start using DIVs (eg. grid) and whatnot things start to get a bit more complicated. For one, you will have to make sure the item you’re appending to the list uses the same template as the existing items, for consistency.
So the question I normally get asked is, “What’s the best way to display the new list items in this kind of situation?”.
There are a couple of ways to do this, and in most cases they all output the same stuff. The only difference is the speed in which the job gets done.