覆盖Laravel 4 Package视图

Question

I want to create my custom CMS and I'd like to create a user package in which I will have a controller with showProfile() function. But the problem is I'd like to easily edit this profile view. So I want to know if there is a way to create cascade view. Like if there is no file in app/views/ then vendor/vendor/package/src/views will be loaded. I hope you got this idea :)

EDIT:

I managed to make it work. I had to register new namespace for views in my ServiceProvider. I put this code to ServiceProvider:

\View::addNamespace('cmscore',array(app_path()./'views/packages/zaalbarxx/cmscore');

Where zaalbarxx/cmscore is vendor/package and cmscore is a namespace I can use later in controller like View::make('cmscore::index'). I added this code in boot() method BEFORE $this->package() so this way app/views are prioritized over package/views. Works brilliant.

Answer 1

这已经成为可能了，但是默认情况下结构是查看vendor/package-name/src/views ，但是如果在app/views/packages/package-name/中有相应的选择。

Answer 2

As stated, you should be able to load package views already.

However, you can add more view locations in the array found in app/config/view.php .

Additionally view paths can be added at run-time with the addLocation() method found in the FileViewFinder class.

Using that method that in a service provider would look like:

$app['view.finder']->addLocation('/path/to/views');

Or anywhere in your app:

App::make('view.finder')->addLocation('/path/to/views');

Also note, I answered this question on cacheing view output recently, which might help you see how extending some portions of the View package might work if you choose to go down that route.

Answer 3

You don't need to program this behavior in, if you read the laravel code you will see that this is built in...

Packages by default will first look in and app/views/packages/package-name/ (all in lowercase! even if package or author have caps! goes unnoticed on windows and then on linux you will bump your head against the wall! )

and if the customer app view doesn't exist the package views will load from the package itself inside: vendor/author/package-name/src/views