0% found this document useful (0 votes)
50 views

Task Lista

The document describes the steps to create a basic task management application in Laravel including: 1. Generating a migration to create a "tasks" table with id, name, and timestamps columns. 2. Generating a Task model. 3. Defining routes for displaying all tasks, adding a new task, and deleting a task. 4. Creating a layout blade template and view for displaying and adding tasks that extends the layout.

Uploaded by

Jeftic Ivan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
50 views

Task Lista

The document describes the steps to create a basic task management application in Laravel including: 1. Generating a migration to create a "tasks" table with id, name, and timestamps columns. 2. Generating a Task model. 3. Defining routes for displaying all tasks, adding a new task, and deleting a task. 4. Creating a layout blade template and view for displaying and adding tasks that extends the layout.

Uploaded by

Jeftic Ivan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 8

MIGRACIJA KA BAZI

php artisan
make:migration
create_tasks_table
--create=tasks

- da se napravi migracija ka bazi

--
Schema::create('tasks', function (Blueprint $table) {

$table->increments('id');

$table->string('name');

$table->timestamps();

});

Schema::drop('tasks');
--

php artisan migrate

- da napravi u bazi kolone u tabeli id, name, timestamps (at, to)

MODEL

app\task

php artisan make:model Task

napomena: ako hocemo i model i migraciju automatski da napravimo onda

php artisan make:model Task -m

ROUTE

app/http/web.php

- listu svih ruta:

php artisan route:list

/**

* Display All Tasks

*/ get -> je da se prikaze nesto

Route::get('/', function () {

return view('tasks');
});

/**

* Add A New Task (dodavanje novog taska u bazu -> cuvanje u bazu)

*/

Route::post('/task', function (Request $request) {

//

});

/**

* Delete An Existing Task (delete -> )

*/

Route::delete('/task/{id}', function ($id) {

//

});

VIEWS

resources/views
- pa folder layouts, pa app.blade.php

// resources/views/layouts/app.blade.php

<!DOCTYPE html>

<html lang="en">

<head>

<title>Laravel Quickstart - Basic</title>

<!-- CSS And JavaScript -->

</head>

<body>

<div class="container">

<nav class="navbar navbar-default">

<!-- Navbar Contents -->

</nav>

</div>
@yield('content')

</body>

</html>

napomena: @yield('content')portion of the layout. This is a special Blade directive that specifies
where all child pages that extend the layout can inject their own content. Next, let's define
the child view that will use this layout and provide its primary content.

Defining The Child View

// resources/views/tasks.blade.php

@extends('layouts.app')

@section('content')

<!-- Bootstrap Boilerplate... -->

<div class="panel-body">

<!-- Display Validation Errors -->

@include('common.errors')
<!-- New Task Form -->

<form action="/task" method="POST" class="form-horizontal">

{{ csrf_field() }}

<!-- Task Name -->

<div class="form-group">

<label for="task" class="col-sm-3 control-label">Task</label>

<div class="col-sm-6">

<input type="text" name="name" id="task-name" class="form-control">

</div>

</div>

<!-- Add Task Button -->

<div class="form-group">

<div class="col-sm-offset-3 col-sm-6">

<button type="submit" class="btn btn-default">

<i class="fa fa-plus"></i> Add Task


</button>

</div>

</div>

</form>

</div>

<!-- TODO: Current Tasks -->

@endsection

+ Before moving on, let's talk about this template a bit. First, the @extends directive informs
Blade that we are using the layout we defined at resources/views/layouts/app.blade.php. All of the
content between @section('content') and @endsection will be injected into the location of
the @yield('content') directive within the app.blade.php layout.
The @include('common.errors') directive will load the template located

at resources/views/common/errors.blade.php. We haven't defined this template, but we will soon!

You might also like