So this is probably going to be a very use-case specific article on how you can hide and show components, or anything really, based on a property value. That's actually probably not even the best way to describe what I want to talk about. I'm pretty new to the Vue scene, so take what I say with a grain of salt and feel free to point out something I could've done better in the comments.

This isn't going to be a very long article, I'd just like to quickly touch bases with everyone about what's happening. So, for those that aren't aware, much of my time is now spent working on an API package for Laravel and Lumen, it's called Dingo API. I actually had some bigger plans for the whole "Dingo" thing but haven't had the time yet. So, people have simply begun referring to the API package as "Dingo". That may change one day.

Now, I've got several other things in the works as well, but I didn't want to leave this blog sitting here becoming stagnent. So, since I'm not too far off release a beta for Dingo API, I want to start providing some lessons on how to use it. And I'm going to do that right here, on this blog.

I'm not going to say when this will start happening though. It'll be a surprise. But I want to cover everything I can. From the basic installation right through to authorization using OAuth 2.0 and scopes. Everything.

I'll keep things updated on Twitter when I post here. I do have an RSS feed should you wish to subscribe that way.

I've recently just switched to Linux from Windows and I'm not looking back. I'm no stranger to Linux but it has taken me a little bit of time to get used to the development process. There were a few hurdles I needed to jump so I'd like to share them here for both my sake and for anyone else who is having these problems.

In the past I've always done my development on Windows. At one stage I had planned to do a series on my Windows development environment but I never got around to it. What a shame.

Don't get me wrong, I never truly hated Windows, although it did have a couple of shortcomings that annoyed me but I always worked around them. Recently though I've just become tired of it. A few days ago I was getting weird results with some unit tests. No matter what I did it just wasn't working, yet at the same time it was working fine on my CentOS server.

So, I did what any sane person would do. I begun trialling a few different Linux distributions to find one I really liked.

Those of you that are currently using Laravel in your projects will be aware that when you make a static call like Route::get() you're actually hitting a facade. In nearly every article about facades you'll see the example of what is happening in the background, in our case it's be something like $app['router']->get().

In this article I want to talk about how you can find your way around the source. For many this can be a bit troublesome as you'll go to where you think it is but you end up somewhere else entirely.

When you're developing an application (or anything for that matter) with a product that is deemed "not yet stable" or as it's more widely known, "beta", you should be expecting changes. I'm referring to the Laravel 4 beta but you could probably apply this article to just about any beta phase, ever.

Laravel 4 uses Composer to install its dependencies and other bits and pieces of the framework. That's just bloody wonderful. So all you have to do is composer update every now and again and you'll have the latest changes pulled in, right? Wrong! Dead wrong. That's so wrong that I'm having trouble comprehending the wrongness of it.

In the early days of Laravel we were blessed with modules. Modules allowed us to separate parts of our applications into more manageable pieces. This meant that modules could contain their own controllers, routes, libraries, configuration, composers, filters, etc. When Laravel 3 was released modules were revamped and renamed to bundles. A Laravel specific bundle repository was setup and developers could publish their bundles so that others could install them with Artisan. It was a great way to easily drop code in to an existing application.

With Laravel 4 hitting beta soon many are wondering what will happen to bundles and how they'll need to be changed to be of any use. There won't be any Laravel specific bundle repository for Laravel 4 since it's now making use of Composer to handle package dependencies.

Since you're reading this I'm assuming that you're aware of the upcoming Laravel 4 release. I'm also assuming you've come from some sort of Laravel background, be it version 2 or 3, although for this articles sake I'll only be referring to L3.

At the time of writing (December 2012) Laravel 4 is still under development, although it's at a point where people are beginning to use it and see how it all works. When reading this article take it with a grain of salt as things might change in the official release of Laravel 4.

The aim of this article is to give you, a current user of Laravel, an insight into what's changing in Laravel 4 that you'll need to be aware of, especially if you're thinking of upgrading. Before we crack on I'd like to point out that Laravel 3 is a great product and that you shouldn't upgrade your application just for the sake of keeping up with the Joneses. Right then, let's get started.

This article is about Laravel 3, some principles may apply to Laravel 4.

Have you ever heard of hooks? If yes then you should instantly know what an event is. But let me explain.

Definition
e•vent
noun

Something that happens or is regarded as happening; an occurrence, especially one of some importance.

The outcome, issue, or result of anything: The venture had no successful event.

Something that occurs in a certain place during a particular interval of time.

Basically an event is something that happens at a given point in time, or in our case, at a given point in our code. Laravel comes with a very easy to use and powerful event system that you can take full advantage of.

You may have seen the first method used and you may be using this method yourself. If you are I urge you to continue reading as it's not a great solution, especially if you find yourself changing a whole bunch of links because you changed the route for your login page.