https://www.recoilweb.com/wp-content/uploads/2024/03/RECP-202405-SKILLS-ICT28851.jpg
Ask anyone who carries an IFAK and a gun every day what they use more often — the IFAK always wins. What other skills do you need? Find out.Recoil
Just another WordPress site
https://www.recoilweb.com/wp-content/uploads/2024/03/RECP-202405-SKILLS-ICT28851.jpg
Ask anyone who carries an IFAK and a gun every day what they use more often — the IFAK always wins. What other skills do you need? Find out.Recoil
https://media.townhall.com/cdn/hodl/ba/images/up/2023/10/gun-pistol-handgun-weapon-firearm-5947350-150×150.jpg
https://laracoding.com/wp-content/uploads/2024/02/upload-image-spatie-media-library1.png
The Spatie Media Library simplifies the process of handling media files, such as images, in Laravel. It provides features for storage, manipulation, and retrieval of media files. One of the strengths of the package is that you can easily associate uploaded files with your Eloquent Models.
In this guide, you will learn how to integrate the Media Library package into an application. We’ll use it to associate uploaded images with an Eloquent Model, specifically the Product
model.
We’ll cover all the required steps like the package installation process, model setup, defining a migration, creating the controller, views and routes to show products, show a product form with upload and storing new products.
Let’s get started!
Begin by creating a new Laravel project using Composer by running:
composer create-project --prefer-dist laravel/laravel product-media-demo
Next, install the Spatie Media Library package via Composer. Run the following command in your terminal:
composer require "spatie/laravel-medialibrary:^11.0.0"
After this has finished, we need to run following command to publish a migration the media library requires to work properly:
php artisan vendor:publish --provider="Spatie\MediaLibrary\MediaLibraryServiceProvider" --tag="medialibrary-migrations"
What this publishing does is it creates a file like, for example database/migrations/2024_02_26_203939_create_media_table.php
. This migration serves to define a table ‘media’ with all the columns predefined as they are required by media library.
Afterwards we need to execute this migration by running:
The Spatie Media Library has now been successfully installed.
Now, let’s create a “Product” model along with its migration by running:
php artisan make:model Product -m
Open the generated migration file (database/migrations/YYYY_MM_DD_create_products_table.php
) and add additional columns that could be encountered in a real-world product application, such as “name,” “description,” “price,” and “image”:
<?php
use Illuminate\Database\Migrations\Migration;
use Illuminate\Database\Schema\Blueprint;
use Illuminate\Support\Facades\Schema;
return new class extends Migration
{
public function up()
{
Schema::create('products', function (Blueprint $table) {
$table->id();
$table->string('name');
$table->text('description')->nullable();
$table->decimal('price', 8, 2);
$table->string('image')->nullable(); // Added for image path
$table->timestamps();
});
}
public function down()
{
Schema::dropIfExists('products');
}
};
Now, run the migration to create the products
table in the database:
Open the “Product” model (app\Models\Product.php
) and configure it to use the Spatie Media Library trait and implement the HasMedia interface.
<?php
namespace App\Models;
use Illuminate\Database\Eloquent\Model;
use Spatie\MediaLibrary\HasMedia;
use Spatie\MediaLibrary\InteractsWithMedia;
class Product extends Model implements HasMedia
{
use InteractsWithMedia;
protected $fillable = ['name', 'description', 'price', 'image'];
}
Defining our Model this way allows us to associate media, like an uploaded image, with each instance of a Product
. We’ll see exactly how this is used, when we add our controller code in step 9.
Generate a controller named “ProductController” by running the following Artisan command:
php artisan make:controller ProductController
Now open the generated “ProductController” (app\Http\Controllers\ProductController.php
) and implement the methods below to list an index page with products, show a create product form and finally storing a new product along with its uploaded image:
<?php
namespace App\Http\Controllers;
use App\Models\Product;
use Illuminate\Http\Request;
class ProductController extends Controller
{
// Display a list of created products along with their images
public function index()
{
$products = Product::latest()->paginate(10);
return view('products.index', compact('products'));
}
// Display the form to create a new product
public function create()
{
return view('products.create');
}
// Store a new product along with its uploaded image file
public function store(Request $request)
{
$request->validate([
// Sets a max image upload file size of 2048 kilobytes or 2MB, adjust as needed:
'image' => 'required|image|max:2048',
// Validate that other fields contain proper values too:
'name' => 'required|string|max:255',
'description' => 'nullable|string|max:255',
'price' => 'required|numeric|min:0|max:999999.99',
]);
// First create the product in the database using the Eloquent model
$product = Product::create($request->validated());
// Then associate the uploaded image file with the product
$product->addMediaFromRequest('image')->toMediaCollection('product-images');
// Send the user back to the product list page
return redirect(route('products.index'))->with('success', 'Product created successfully.');
}
}
In this step we’ll create a view that contains the form to add a new product along with an uploaded image.
I made sure the blade code offers a nicely layouted form that shows error messages for missing or invalid values. This way we can guarantee the user is prompted to always upload an actual image file and fill the required fields name
and price
.
Create a file at resources/views/products/create.blade.php
and add the following code:
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Excel Import</title>
<!-- Bootstrap CSS -->
<link href="https://cdn.jsdelivr.net/npm/bootstrap@5.3.0/dist/css/bootstrap.min.css" rel="stylesheet">
</head>
<body>
<div class="container mt-5">
<h1 class="my-4">Create Product</h1>
<form action="" method="POST" enctype="multipart/form-data">
@csrf
<div class="mb-3">
<label for="name" class="form-label">Name</label>
@error('name')
<div class="text-danger">
<small></small>
</div>
@enderror
<input type="text" class="form-control" id="name" name="name">
</div>
<div class="mb-3">
<label for="description" class="form-label">Description</label>
@error('description')
<div class="text-danger">
<small></small>
</div>
@enderror
<textarea class="form-control" id="description" name="description"></textarea>
</div>
<div class="mb-3">
<label for="price" class="form-label">Price</label>
@error('price')
<div class="text-danger">
<small></small>
</div>
@enderror
<input type="number" step="0.01" class="form-control" id="price" name="price">
</div>
<div class="mb-3">
<label for="image" class="form-label">Product Image</label>
@error('image')
<div class="text-danger">
<small></small>
</div>
@enderror
<input type="file" class="form-control" id="image" name="image">
</div>
<button type="submit" class="btn btn-primary">Create Product</button>
</form>
</div>
</body>
</html>
In this step we’ll create a view that allows us to show all products. We will use Spatie Media Library to render a thumbnail of the uploaded product image.
Create a file at resources/views/products/index.blade.php
and add the following code:
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Excel Import</title>
<!-- Bootstrap CSS -->
<link href="https://cdn.jsdelivr.net/npm/bootstrap@5.3.0/dist/css/bootstrap.min.css" rel="stylesheet">
</head>
<body>
<div class="container mt-5">
<!-- Display success message if it was set-->
@if(session('success'))
<div class="alert alert-success"></div>
@endif
<h1 class="my-4">Product Listing</h1>
<table class="table">
<thead>
<tr>
<th colspan="3"></th>
<th class="text-end">
<a href="" class="btn btn-primary">Create Product</a>
</th>
</tr>
<tr>
<th>Name</th>
<th>Description</th>
<th>Price</th>
<th>Image</th>
</tr>
</thead>
<tbody>
@foreach($products as $product)
<tr>
<td></td>
<td></td>
<td></td>
<!-- Fetch a thumbnail image based on the product's associated media -->
<td><img src="" alt="Product Image" width="140px"></td>
</tr>
@endforeach
</tbody>
</table>
</div>
</body>
</html>
Finally, before we can test the application, we need to define the routes to list products, show the create form, and store a product.
Open routes/web.php
and add:
<?php
use Illuminate\Support\Facades\Route;
use App\Http\Controllers\ProductController;
Route::get('/products', [ProductController::class, 'index'])->name('products.index');
Route::get('/products/create', [ProductController::class, 'create'])->name('products.create');
Route::post('/products', [ProductController::class, 'store'])->name('products.store');
You can now test the application by running the development server:
Now you can navigate to http://127.0.0.1:8000/products
in your browser to view the product listing. Proceed to http://127.0.0.1:8000/products/create
to access the create product form.
Select an image to upload and fill in the other product details and submit the form. Verify that the product and its associated image are successfully stored in the database.
After storing the form your database contents should look somewhat like this:
Now if you continue and upload a few more you’ll see it nicely displays all the thumbnail images on the product page:
That’s it! You’ve successfully built your first application that uses Spatie Media Library to manage its uploaded media files.
In this tutorial, we’ve explored how to upload images using the Spatie Media Library package in a Laravel application. By following the steps outlined above, you can easily handle image uploads and storage in your Laravel projects.
Using third party packages like this can greatly speed up your development process. Before you use a package in your production application, check that the package is well maintained, supports your Laravel version, is properly documented and does not have lots of unresolved issues posted on their git page.
Spatie is a well-known company that has been developing and maintaining numerous packages for years and provides them for free as open source. The Media Library is one of their most widely used packages and is likely to meet most quality requirements.
I hope this helped you get started in using this handy third party package. Let me know in the comments what you’re using it for, how it went and what issues you may have had with it.
Happy Coding!
References
Laravel News Links
https://laracoding.com/wp-content/uploads/2024/02/upload-image-spatie-media-library1.png
The Spatie Media Library simplifies the process of handling media files, such as images, in Laravel. It provides features for storage, manipulation, and retrieval of media files. One of the strengths of the package is that you can easily associate uploaded files with your Eloquent Models.
In this guide, you will learn how to integrate the Media Library package into an application. We’ll use it to associate uploaded images with an Eloquent Model, specifically the Product
model.
We’ll cover all the required steps like the package installation process, model setup, defining a migration, creating the controller, views and routes to show products, show a product form with upload and storing new products.
Let’s get started!
Begin by creating a new Laravel project using Composer by running:
composer create-project --prefer-dist laravel/laravel product-media-demo
Next, install the Spatie Media Library package via Composer. Run the following command in your terminal:
composer require "spatie/laravel-medialibrary:^11.0.0"
After this has finished, we need to run following command to publish a migration the media library requires to work properly:
php artisan vendor:publish --provider="Spatie\MediaLibrary\MediaLibraryServiceProvider" --tag="medialibrary-migrations"
What this publishing does is it creates a file like, for example database/migrations/2024_02_26_203939_create_media_table.php
. This migration serves to define a table ‘media’ with all the columns predefined as they are required by media library.
Afterwards we need to execute this migration by running:
The Spatie Media Library has now been successfully installed.
Now, let’s create a “Product” model along with its migration by running:
php artisan make:model Product -m
Open the generated migration file (database/migrations/YYYY_MM_DD_create_products_table.php
) and add additional columns that could be encountered in a real-world product application, such as “name,” “description,” “price,” and “image”:
<?php
use Illuminate\Database\Migrations\Migration;
use Illuminate\Database\Schema\Blueprint;
use Illuminate\Support\Facades\Schema;
return new class extends Migration
{
public function up()
{
Schema::create('products', function (Blueprint $table) {
$table->id();
$table->string('name');
$table->text('description')->nullable();
$table->decimal('price', 8, 2);
$table->string('image')->nullable(); // Added for image path
$table->timestamps();
});
}
public function down()
{
Schema::dropIfExists('products');
}
};
Now, run the migration to create the products
table in the database:
Open the “Product” model (app\Models\Product.php
) and configure it to use the Spatie Media Library trait and implement the HasMedia interface.
<?php
namespace App\Models;
use Illuminate\Database\Eloquent\Model;
use Spatie\MediaLibrary\HasMedia;
use Spatie\MediaLibrary\InteractsWithMedia;
class Product extends Model implements HasMedia
{
use InteractsWithMedia;
protected $fillable = ['name', 'description', 'price', 'image'];
}
Defining our Model this way allows us to associate media, like an uploaded image, with each instance of a Product
. We’ll see exactly how this is used, when we add our controller code in step 9.
Generate a controller named “ProductController” by running the following Artisan command:
php artisan make:controller ProductController
Now open the generated “ProductController” (app\Http\Controllers\ProductController.php
) and implement the methods below to list an index page with products, show a create product form and finally storing a new product along with its uploaded image:
<?php
namespace App\Http\Controllers;
use App\Models\Product;
use Illuminate\Http\Request;
class ProductController extends Controller
{
// Display a list of created products along with their images
public function index()
{
$products = Product::latest()->paginate(10);
return view('products.index', compact('products'));
}
// Display the form to create a new product
public function create()
{
return view('products.create');
}
// Store a new product along with its uploaded image file
public function store(Request $request)
{
$request->validate([
// Sets a max image upload file size of 2048 kilobytes or 2MB, adjust as needed:
'image' => 'required|image|max:2048',
// Validate that other fields contain proper values too:
'name' => 'required|string|max:255',
'description' => 'nullable|string|max:255',
'price' => 'required|numeric|min:0|max:999999.99',
]);
// First create the product in the database using the Eloquent model
$product = Product::create($request->validated());
// Then associate the uploaded image file with the product
$product->addMediaFromRequest('image')->toMediaCollection('product-images');
// Send the user back to the product list page
return redirect(route('products.index'))->with('success', 'Product created successfully.');
}
}
In this step we’ll create a view that contains the form to add a new product along with an uploaded image.
I made sure the blade code offers a nicely layouted form that shows error messages for missing or invalid values. This way we can guarantee the user is prompted to always upload an actual image file and fill the required fields name
and price
.
Create a file at resources/views/products/create.blade.php
and add the following code:
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Excel Import</title>
<!-- Bootstrap CSS -->
<link href="https://cdn.jsdelivr.net/npm/bootstrap@5.3.0/dist/css/bootstrap.min.css" rel="stylesheet">
</head>
<body>
<div class="container mt-5">
<h1 class="my-4">Create Product</h1>
<form action="" method="POST" enctype="multipart/form-data">
@csrf
<div class="mb-3">
<label for="name" class="form-label">Name</label>
@error('name')
<div class="text-danger">
<small></small>
</div>
@enderror
<input type="text" class="form-control" id="name" name="name">
</div>
<div class="mb-3">
<label for="description" class="form-label">Description</label>
@error('description')
<div class="text-danger">
<small></small>
</div>
@enderror
<textarea class="form-control" id="description" name="description"></textarea>
</div>
<div class="mb-3">
<label for="price" class="form-label">Price</label>
@error('price')
<div class="text-danger">
<small></small>
</div>
@enderror
<input type="number" step="0.01" class="form-control" id="price" name="price">
</div>
<div class="mb-3">
<label for="image" class="form-label">Product Image</label>
@error('image')
<div class="text-danger">
<small></small>
</div>
@enderror
<input type="file" class="form-control" id="image" name="image">
</div>
<button type="submit" class="btn btn-primary">Create Product</button>
</form>
</div>
</body>
</html>
In this step we’ll create a view that allows us to show all products. We will use Spatie Media Library to render a thumbnail of the uploaded product image.
Create a file at resources/views/products/index.blade.php
and add the following code:
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Excel Import</title>
<!-- Bootstrap CSS -->
<link href="https://cdn.jsdelivr.net/npm/bootstrap@5.3.0/dist/css/bootstrap.min.css" rel="stylesheet">
</head>
<body>
<div class="container mt-5">
<!-- Display success message if it was set-->
@if(session('success'))
<div class="alert alert-success"></div>
@endif
<h1 class="my-4">Product Listing</h1>
<table class="table">
<thead>
<tr>
<th colspan="3"></th>
<th class="text-end">
<a href="" class="btn btn-primary">Create Product</a>
</th>
</tr>
<tr>
<th>Name</th>
<th>Description</th>
<th>Price</th>
<th>Image</th>
</tr>
</thead>
<tbody>
@foreach($products as $product)
<tr>
<td></td>
<td></td>
<td></td>
<!-- Fetch a thumbnail image based on the product's associated media -->
<td><img src="" alt="Product Image" width="140px"></td>
</tr>
@endforeach
</tbody>
</table>
</div>
</body>
</html>
Finally, before we can test the application, we need to define the routes to list products, show the create form, and store a product.
Open routes/web.php
and add:
<?php
use Illuminate\Support\Facades\Route;
use App\Http\Controllers\ProductController;
Route::get('/products', [ProductController::class, 'index'])->name('products.index');
Route::get('/products/create', [ProductController::class, 'create'])->name('products.create');
Route::post('/products', [ProductController::class, 'store'])->name('products.store');
You can now test the application by running the development server:
Now you can navigate to http://127.0.0.1:8000/products
in your browser to view the product listing. Proceed to http://127.0.0.1:8000/products/create
to access the create product form.
Select an image to upload and fill in the other product details and submit the form. Verify that the product and its associated image are successfully stored in the database.
After storing the form your database contents should look somewhat like this:
Now if you continue and upload a few more you’ll see it nicely displays all the thumbnail images on the product page:
That’s it! You’ve successfully built your first application that uses Spatie Media Library to manage its uploaded media files.
In this tutorial, we’ve explored how to upload images using the Spatie Media Library package in a Laravel application. By following the steps outlined above, you can easily handle image uploads and storage in your Laravel projects.
Using third party packages like this can greatly speed up your development process. Before you use a package in your production application, check that the package is well maintained, supports your Laravel version, is properly documented and does not have lots of unresolved issues posted on their git page.
Spatie is a well-known company that has been developing and maintaining numerous packages for years and provides them for free as open source. The Media Library is one of their most widely used packages and is likely to meet most quality requirements.
I hope this helped you get started in using this handy third party package. Let me know in the comments what you’re using it for, how it went and what issues you may have had with it.
Happy Coding!
References
Laravel News Links
https://theawesomer.com/photos/2024/03/ludicrous_speed_switch_t.jpg
| Buy
Level up your transportation with the Spaceballs-inspired Ludicrous Speed Panel from Concord Aerospace. Turn its dial to increase your speed from Light to Ridiculous to Ludicrous, then go to Plaid. The Apollo-era control panel has a working main switch hidden under a “GO” cover, and its knob can be equipped with a potentiometer for controlling devices.
The Awesomer
https://repository-images.githubusercontent.com/735853054/5a90530f-a552-4b85-8eb9-85bd918bc981
'connections' => [ ... 'sns-sqs' => [ 'driver' => 'sns-sqs', 'key' => env('AWS_ACCESS_KEY_ID'), 'secret' => env('AWS_SECRET_ACCESS_KEY'), 'region' => env('AWS_DEFAULT_REGION', 'us-east-1'), 'prefix' => env('SQS_PREFIX', 'https://sqs.us-east-1.amazonaws.com/your-account-id'), 'queue' => env('SQS_QUEUE', 'default'), 'suffix' => env('SQS_SUFFIX'), 'after_commit' => false, 'endpoint' => env('AWS_ENDPOINT'), 'sns_topic_arn' => env('SNS_TOPIC_ARN', 'arn:aws:sns:us-east-1:your-account-id:topic'), ], ]
Laravel News Links
https://cdn.arstechnica.net/wp-content/uploads/2024/02/Screenshot-2024-02-26-160712-760×380.png
I remember Dark Forces, or Star Wars: Doom, as a slog. Running a demo of the 1995 game on a Gateway system with an Intel 486DX at 33 MHz, I trudged through seemingly endless gray hallways. I shot at a steady trickle of Stormtroopers with one their own (intentionally) semi-accurate blaster rifles. After a while, I would ask myself a pertinent, era-specific question: Why was I playing this low-energy nostalgia trip instead of actual Doom?
Dark Forces moved first-person shooters forward in a number of ways. It could lean on Star Wars for familiar sounds and enemies and tech, and a plot with a bit more complexity than "They’re demons, they gotta go." It let the player look up and down, jump, and crouch, which were big steps for the time. And its level design went beyond "find the blue key for the blue door," with some clever environmental puzzles and challenges.
Not that key cards don’t show up. This game is from 1995, so there are key cards, there are hidden wall-doors, and there are auto-spawning enemies. It’s not like the Dark Forces designers could entirely ignore Doom. Nobody could.
Having played through some enjoyable hours of Dark Forces Remaster, I’ve come around quite a bit on this Doom-era game’s worthiness. In 2024, I can joyfully rip through research facilities, foundries, sewers, and space stations at a breakneck clip, stuffing bad guys full of laser blasts from every angle and distance. The grenades (err, thermal detonators) actually feel viable and fun to use. The levels, and the game as a whole, are higher resolution and easier to appreciate at this faster, more frenetic pace.
Nightdive Studios continues its streak of providing spiffed-up but eminently faithful remasters of classic titles with Dark Forces Remastered. The studio’s leaders told Ars last year that their goal was games that "play the way you remember them playing. Not the way they actually did on your 486 [computer], but in an evocative manner." For me, Dark Forces Remastered feels far, far better than I remember, and so I’ve gotten a chance to absorb a lot more of the world it’s trying to evoke.
A quick primer on Dark Forces: You are mercenary Kyle Katarn, working for the Rebellion around the time of Episode IV (the first Death Star one), helping the rebels investigate and halt the development of Dark Troopers. Dark Troopers are essentially Stormtroopers with big shoulder pauldrons and the ability to deflect blaster fire. You can use all kinds of found weapons, including blasters, land mines, and rocket launchers. But you will not become a Jedi, because that happens in the next game.
Due either to thematic or technical restrictions of the time, you’re not typically fighting huge arenas of baddies. You are meant to sneak through hallways and turn corners, popping a few at a time. Unless you’re me, that is, liberated by playing at 4K at 120 frames per second (and, sometimes, cheat codes), wantonly wrecking dudes who didn’t get the memo about my arrival.
The little voice stings—"Stop!" "You’re not authorized!"—were a delight, if often cut short by the quick dispatching of their speaker. For the first few levels, I felt like the Rebellion could have destroyed five Death Stars in just two movies if they had a few more Kyles like me. But Dark Forces does ramp up as you go on.
All the same cheat codes from the original game work—Nightdive even gives you places to type them in and then activate them in menus—and I had to lean on a couple level skips and resupplies to get through the first seven levels. The objectives get far twistier and "What did flipping that switch do?" as you roll on. Some of the battery-powered devices, like infrared goggles and gas masks, are all but essential at times, and the long levels with their repeating wall textures can have you wasting them. It’s never quite unfair, but you realize how tough this must have been at a far lower frame rate and walking speed. And without such easy access to online walk-throughs, of course.
There are new lighting effects, much nicer menus and options, gamepad support (including rumble), and polished cutscenes, in addition to the gameplay that now tilts a bit more toward Motörhead than Rush in speed and feel. But, really, what sells Dark Forces Remastered is the game beneath the upgrades. If you have any interest in hopping on Jabba the Hutt’s barge again, this is the way to do it.
Listing image by Nightdive/LucasFilm
Ars Technica – All content
https://picperf.io/https://laravelnews.s3.amazonaws.com/featured-images/future-ide-featured-vscode.jpg
We’ve created a collection of essential plugins for Visual Studio Code that will supercharge your coding experience. I’ve gathered my favorite extensions to make you a more productive PHP developer and even threw in my favorite theme for VS Code.
Let’s dive in!
The Laravel Blade formatter is an opinionated Blade file formatter for VS Code. This extension uses the shufo/blade-formatter NPM package that you can use to format Blade template files programmatically.
Another alternative is the shufo/prettier-plugin-blade if you’d rather use the Prettier formatter instead. VS Code has a Prettier plugin that you can use to incorporate this workflow on save. The VSCode section of the readme has setup instructions if you want to go this route.
Codeium is a free AI Code Completion and Chat tool comparable to GitHub copilot. It offers autocomplete and is available for several editors, including Visual Studio Code. It supports 70+ programming languages, including JavaScript, TypeScript, PHP, and more. You can also use the IDE-integrated chat to avoid leaving VS Code to ask questions or explain things.
You can grab this plugin for VS Code on the Visual Studio Code Marketplace.
The Monokai Pro theme is my favorite theme for Visual Studio code. While you can freely evaluate it (with occasional popups), it requires a paid license for €12.5 ($13.53 USD at the time of writing), which is well worth the effort that went into designing these themes.
Monokai Pro includes six theme variations (Octagon is my favorite), has stylish file icons, contains various configuration options, and should fit almost any style you prefer in a dark theme.
You can grab a license on the Monokai Pro website, and the extension is available on the Visual Studio Marketplace.
The PHP Intelephense extension gives you code intelligence for PHP in Visual Studio Code. If you are a newcomer to PHP or Laravel or a seasoned PHP developer jumping into VS Code for the first time, I recommend installing this extension. It includes code intelligence, symbol searching, go-to definition, documentation help, and a host of other features.
Intelephense offers a premium license that you can grab on intelephense.com that unlocks features like code renaming, code folding, "find all" implementations, "go to type definitions," and more.
Better PHPUnit is a test runner for Visual Studio Code that supports running tests from your editor in the embedded terminal. This extension also supports Running Pest Tests, which gives you one test runner to support any PHP testing workflow.
You can install this extension within VS Code or grab it from the Visual Studio Marketplace.
The Tailwind CSS IntelliSense extension gives you intelligent Tailwind CSS tooling for VS Code. This extension makes you more productive with Tailwind by providing advanced features such as autocomplete, syntax highlighting, and linting. You can also quickly see the complete CSS for a Tailwind class name by hovering over it:
You can find this extension by searching for “Tailwind CSS IntelliSense” or getting it directly from the Visual Studio Marketplace.
That’s a wrap on our essential plugins for VS Code users. I hope you’ve found something useful to improve your VS Code development! We can’t share every single extension, so let us know your favorite VS Code extension or theme!
The post Six Essential Plugins for Visual Studio Code appeared first on Laravel News.
Join the Laravel Newsletter to get all the latest Laravel articles like this directly in your inbox.
Laravel News
https://www.ammoland.com/wp-content/uploads/2024/02/LM_147_OHIO_TN-500×282.jpg
We always hear the gun-grabbers say, “More gun restrictions will reduce crime.” We remind them that the exact opposite is true. The truth is when more good people are prevented from defending themselves due to restrictive and unconstitutional gun laws; it puts them in a vulnerable position.
Not only are good people put in a vulnerable position because they can’t defend themselves and their families, but criminals are also given the upper hand. Bad guys who want to do harm are emboldened by the fact that their potential victims can no longer defend themselves. This is why gun-free zones are the most popular spot for violent attacks.
The study focused on firearms-related crimes from June 2021 to June 2023. This included the year before and after the constitutional carry law went into effect. As it turns out, Cleveland, Akron, Columbus, Parma, Canton, and Toledo became much safer when residents were not restricted from protecting themselves in public with guns. This study corresponds with the Kleck / Gertz: Armed Resistance to Crime study that showed us there are up to 2.5m defensive gun uses (DGU) per year in America. It also reminds us that just because there are guns in the hands of good people and crime is stopped, as a result, it does not mean bad guys are getting killed. Because of the extensive work John Lott and others have done in this area, we now know that in approximately 95% of DGUs, a trigger is never pulled; Just the mere presence of a good gun is enough to stop a bad guy.
Six of Ohio’s eight largest cities saw less gun crime after the state’s “constitutional carry” law took effect, according to a study published today by the Center for Justice Research, a partnership between the office of AG Yost and @bgsu.
Details: https://t.co/6gYnmJOdfe pic.twitter.com/OGCEgYPF2L— Ohio Attorney General Dave Yost (@OhioAG) January 3, 2024
Despite this study and many others like it, groups like Mom’s Demand Action, Everytown for Gun Safety, and the Gifford’s group continue to spread, anti-gun propaganda in support of more gun restrictions. It would seem they are much more interested in gun control for political purposes than actually saving lives.
About Dan Wos, Author – Good Gun Bad Guy
Dan Wos is available for Press Commentary. For more information contact PR HERE
Dan Wos is a nationally recognized 2nd Amendment advocate, Host of The Loaded Mic and Author of the “GOOD GUN BAD GUY” book series. He speaks at events, is a contributing writer for many publications, and can be found on radio stations across the country. Dan has been a guest on Newsmax, the Sean Hannity Show, Real America’s Voice, and several others. Speaking on behalf of gun-rights, Dan exposes the strategies of the anti-gun crowd and explains their mission to disarm law-abiding American gun-owners.
AmmoLand Shooting Sports News
https://www.gearpatrol.com/wp-content/uploads/sites/2/2020/08/FD-PRND-Gear-Patrol-Lead-Full-jpg.webp
For starters, the US government says so.
If your car has an automatic transmission, the different positions you can shift into follow a specific pattern: P-R-N-D, usually followed by either a couple of lower gear options or the chance to shift it into a manual control mode. In case you’ve never driven (or, somehow, only driven cars with manual transmissions, in which place, god bless you), those four letters stand for Park, Reverse, Neutral and Drive — or, in layman’s terms, Stopped, Backwards, Free-Rolling and Forwards.
You’ve probably shifted from Park to Drive a hundred thousand times, and from Drive to Reverse nearly as many. But in all those times, have you ever stopped to wonder: Gee, why is it that every car’s shifter seems to go from Reverse to Neutral to Drive?
Well, there’s actually a very good reason: the United States government says so.
Editor’s Note: This story is part of “Further Details,” a series dedicated to ubiquitous but overlooked elements hidden on your favorite products.
When the automatic transmission was young, carmakers would often set up their own shifters however they damn well felt like it. One common layout, found in General Motors and Chrysler models, among others, placed Reverse at the far end of the shifter, past Neutral, Drive and the lower gears. In one sense, it made sense; after all, you want Reverse to be easy to find, so why not put it at the very end of the shifter?
The problem that arose, however, was one of user error: people attempting to shift into a low forward gear would wind up overshooting into Reverse without realizing it, or vice versa. Given the mass of, say, a ’59 Eldorado, traveling suddenly in the wrong direction could result in very unpleasant consequences for any persons, animals or objects that happened to be in the way.
It took none other than noted safety advocate Ralph Nader to help bring the problems with this arrangement to light. In the second chapter of his seminal book Unsafe at Any Speed, Nader raised five ripped-from-the-headlines examples of death, injury and destruction caused by the poor design of this P-N-D-L-R shift arrangement.
“It takes no science and little foresight to accurately condemn a particularly dangerous transmission shift pattern — the P N D L R quadrant common to Cadillacs, Buicks, Oldsmobiles, Pontiacs, Studebakers and Ramblers over the past ten years,” he wrote. “The driver is forced to look at the shift lever for confirmation of the gear in use. The driver has to lift the lever to go into reverse. Should he not lift it enough, the car will remain in forward low while the driver is looking backwards and expecting the car to move in that direction.”
Sticking neutral between forward and reverse, Nader said, was a commonly-accepted trait of mechanical design in things like mechanical tools. But the design of the Hydra-matic transmission used in these models made it cheaper to put reverse next to the forward cogs, according to an automotive transmission engineer Nader cited; while that obstacle was gone by 1956, GM reportedly stood by it — using the rather circular reasoning that, in effect, there were already too many cars on the road using the P-N-D-L-R setup to stop using it now.
As with encouraging the adoption of safety belts, Nader’s outspoken advocacy wound up getting results. While America’s domestic carmakers all came around to the superior design of putting neutral between Reverse and Drive by 1966, by 1971, it had become part of federal law in the form of U.S. Department of Transportation Standard No. 102: “Location of transmission shift positions on passenger cars. A neutral position shall be located between forward drive and reverse drive positions.”
The recent return of pushbutton transmission selectors and the arrival of electronic gearshifts means that carmakers have a tad more flexibility than they once did, in terms of control layouts. Honda and Lincoln’s pushbutton shifters arranges its choices vertically; GMC’s stretches them out horizontally; Mercedes-Benz, BMW, Hyundai and Ford, among others, make Park a separate button to seek out. But the heart of the rule remains in effect: if you want to shift from Drive to Reverse or vice versa, you have to make a stop in Neutral.
Now, some exotic cars with single-clutch and dual-clutch automated manual transmissions, like Ferrari, Lamborghini and McLaren, arrange things even more differently — but that seems to be because they do without a “Park” or, in some cases, even a “Drive.” (Ferraris, for example, only offer buttons for reverse and manual modes; neutral is obtained by pulling both paddle shifters at once, and Park occurs automatically when the car is turned off.) But again, the spirit of the law remains in play: it’s very hard to accidentally shift into Reverse when you mean to go forward.
Gear Patrol