Update project with Laravel 4

[pokap]

This is a big features.
I am not proposing an overhaul of tinyissue, but a passage to Laravel 4.1.

The are lot of modification like rename and move file, logic does not change.
Warning, I have not included the vendors.

If there are problems of integration or other, I remain available to update the PR.

[ryanwinchester]

Yes Laravel 4.1 support would be amazing

[woolfg]

+1

[codivist]

+1

[woolfg]

just installed the new version, did a "php composer.phar install" and everything worked fine

[woolfg]

@pokap did you base your laravel4 upgrade on the master branch as in your version some features are missing which are currently available in the current develop branch. you should also point your pull request to the develop branch.

[pokap]

@woolfg I can propose a new branch develop like "4.1", you can easily manage merges. What do you think?

[woolfg]

I would be glad to hear about mikelbring's ideas and plans. afaik he planned to switch to laravel 4 as well?

[pokap]

@woolfg I don't know the mikelbring's intentions :(

I'm involved in a project via tinyissue but my server doesn't work with laravel 3, I upgraded all code for lavarel 4 and I propose this upgrade.

If @mikelbring doesn't respond, it will be difficult to maintain, or it will go through a real fork.

[woolfg]

I hope @mikelbring will respond and shed light on the current roadmap. Afaik he wanted to develop a flexible plugin system to cope with all the issues and pull requests.

[akanevsky]

@pokap I think that it would be easier to integrate your pull request with all the other recent contributions if you based it off of the develop branch. Also, what are the two other commits that are part of this pull request? They don't seem to related to the Laravel update. Thanks.

[pokap]

@akanevsky You're right, I'll take the time to properly rebuild this PR. And update by development with new features.

[pokap]

@everyone, I create a new PR in #214.