PHPackages team383/livewire-resource-time-grid - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. team383/livewire-resource-time-grid ActiveLibrary team383/livewire-resource-time-grid =================================== Laravel Livewire resource time grid component 2.0.5(1y ago)2442↓100%MITPHPPHP ^7.2|^8.0|^8.1|^8.2|^8.3|^8.4 Since Feb 20Pushed 1y agoCompare [ Source](https://github.com/383Project/livewire-resource-time-grid)[ Packagist](https://packagist.org/packages/team383/livewire-resource-time-grid)[ Docs](https://github.com/asantibanez/livewire-resource-time-grid)[ RSS](/packages/team383-livewire-resource-time-grid/feed)WikiDiscussions master Synced 1mo ago READMEChangelog (4)Dependencies (4)Versions (10)Used By (0) Livewire Resource Time Grid =========================== [](#livewire-resource-time-grid) This package allows you to build resource/time grid to show events in a "calendar" way. You can define resources as anything that owns an event, eg. a particular day, a user, a client, etc. Events loaded with the component will be then rendered in columns according to the resource it belongs to and the starting date of the event. This package is based on , but has significantly diverged from this in order to support Laravel 11 and Livewire 3, and also provides various improvements and additional features. Preview ------- [](#preview) [![preview](https://github.com/383Project/livewire-resource-time-grid/raw/master/preview.gif)](https://github.com/383Project/livewire-resource-time-grid/raw/master/preview.gif) Installation ------------ [](#installation) You can install the package via composer: ``` composer require team383/livewire-resource-time-grid ``` Requirements ------------ [](#requirements) This package uses `livewire/livewire` () under the hood. It also uses TailwindCSS () for base styling. Please make sure you include both of this dependencies before using this component. Usage ----- [](#usage) In order to use this component, you must create a new Livewire component that extends from `LivewireResourceTimeGrid` You can use `make:livewire` to create a new component. For example. ``` php artisan make:livewire AppointmentsGrid ``` In the `AppointmentsGrid` class, instead of extending from the base `Component` Livewire class, extend from `LivewireResourceTimeGrid`. Also, remove the `render` method. You'll have a class similar to this snippet. ``` class AppointmentsGrid extends LivewireResourceTimeGrid { // } ``` In this class, you must override the following methods ``` public function resources() { // must return a Laravel collection } public function events() { // must return a Laravel collection } ``` In `resources()` method, return a collection holding the "resources" that own the events that are going to be listed in the grid. These "resources" must be arrays with `key => value` pairs and must include an `id` and a `title`. You can add any other keys to each "resource as needed" Example ``` public function resources() { return collect([ ['id' => 'andres', 'title' => 'Andres'], ['id' => 'pamela', 'title' => 'Pamela'], ['id' => 'sara', 'title' => 'Sara'], ['id' => 'bruno', 'title' => 'Bruno'], ]); } ``` In the `events()` method, return a collection holding the events that belong to each of the "resources" returned in the `resources()` method. Events must also be keyed arrays holding at least the following keys: `id`, `title`, `starts_at`, `ends_at`, `resource_id`. Also, the following conditions are expected for each returned event: - For each event `resource_id` must match an `id` in the `resources()` returned collection. - `starts_at` must be a `Carbon\Carbon` instance - `ends_at` must be a `Carbon\Carbon` instance Example ``` public function events() { return collect([ [ 'id' => 1, 'title' => 'Breakfast', 'starts_at' => Carbon::today()->setTime(10, 0), 'ends_at' => Carbon::today()->setTime(12, 0), 'resource_id' => 'andres', ], [ 'id' => 2, 'title' => 'Lunch', 'starts_at' => Carbon::today()->setTime(13, 0), 'ends_at' => Carbon::today()->setTime(15, 0), 'resource_id' => 'pamela', ], ]); } ``` Now, we can include our component in any view. You must specify 3 parameters, `starting-hour`, `ending-hour` and `interval`. These parameters represent the times of a day the grid will render and how many divisions per hour it will display. (`interval` must be in minutes and less than `60`) Example ``` ``` You should include scripts with `@livewireResourceTimeGrid` to enable drag and drop which is turned on by default. You must include them after `@livewireScripts` ``` @livewireScripts @livewireResourceTimeGridScripts ``` This will render a grid starting from 8am til 7pm inclusive with time slots of 15 minutes. [![example](https://github.com/asantibanez/livewire-resource-time-grid/raw/master/example.png)](https://github.com/asantibanez/livewire-resource-time-grid/raw/master/example.png) By default, the component uses all the available width and height. You can constrain it to use a specific set of dimensions with a wrapper element. Advanced Usage -------------- [](#advanced-usage) ### UI customization [](#ui-customization) You can customize the behavior of the component with the following properties when rendering on a view: - `resource-column-header-view` which can be any `blade.php` view that renders information of a resource. This view will be injected with a `$resource` variable holding its data. - `event-view` which can be any `blade.php` view that will be used to render the event card. This view will be injected with a `$event` variable holding its data. - `resource-column-header-height-in-rems` and `hour-height-in-rems` can be used to customize the height of each resource view or time slot respectively. Defaults used are `4` and `8` respectively. These will be used as `rem` values. - `before-grid-view` and `after-grid-view` can be any `blade.php` views that can be rendered before or after the grid itself. These can be used to add extra features to your component using Livewire. Example ``` ``` Caution UI Customisation has not been tested with the new 383 implementation; care should be taken to reproduce the necessary parts within each view to ensure your custom views preserve required functionality. ### Interaction customization [](#interaction-customization) You can override the following methods to add interactivity to your component ``` public function hourSlotClick($resourceId, $hour, $slot) { // This event is triggered when a time slot is clicked.// // You'll get the resource id as well as the hour and minute // clicked by the user } public function onEventClick($event) { // This event will fire when an event is clicked. You will get the event that was // clicked by the user } public function onEventDropped($eventId, $resourceId, $hour, $slot) { // This event will fire when an event is dragged and dropped into another time slot // You will get the event id, the new resource id + hour + minute where it was // dragged to } ``` You can also override how events and resources are matched instead of using a `resource_id` and `id` respectively. To do this, you must override the following method ``` public function isEventForResource($event, $resource) { // Must return true or false depending if the $resource is the owner of the $event } ``` The base implementation for this method is ``` return $event['resource_id'] == $resource['id']; ``` You can customize it as you need. 👍 383's Additions --------------- [](#383s-additions) As well as bringing the code up to date, we have also added a few features which may be useful. ### Reactive properties [](#reactive-properties) In order to facilitate live updating of key layout features on the fly, we have made the following fields reactive: - `startingHour` - `endingHour` - `interval` - `hourHeightInRems` For this to work correctly, you will need to arrange a few things: - When one of these fields is changed, your app will need to dispatch a `onRefreshResourceTimeGrid` livewire event to refresh the time grid component - If you are using drag-to-scroll or drag-to-create, you will need to re-run the initialisation scripts using something like this: ``` @script // This is required to reinitialise the component when the settings are changed window.Livewire.on('onLivewireResourceTimeGridMounted', () => { initDragToScroll(); }); @endscript ``` ### Drag-to-scroll & Drag-to-create [](#drag-to-scroll--drag-to-create) We have added a feature which allows you to drag the grid to scroll it. This is particularly useful when you have a large number of resources and events, and you want to be able to scroll through them quickly. This works by scrolling the grid horizontally, or the whole page vertically if you are at the top or bottom of the grid. This is achieved by holding the right mouse button and moving the mouse, or by holding the shift key while dragging. There is also a hover-over tooltip that repeats the column header and the time slot so it's easy to see where you are when the page is scrolled. In addition you can create new items by dragging from the top of the grid to the bottom. This will create a new event in the resource you are dragging from, with the start and end times corresponding to the time slot you are dragging to. Use the middle button, or hold control while dragging, to use this feature. These features must be individually enabled like this: ``` // Render your component @livewire(\App\Livewire\MyLivewireTimeGrid::class, [ ... 'dragToScroll'=> true, 'dragToCreate' => true, ]) // You will need to load the relevant scripts after the component is initially rendered: @livewireResourceTimeGridDragToScroll @script // This is required to reinitialise the component when the settings are changed window.Livewire.on('onLivewireResourceTimeGridMounted', () => { initDragToScroll(); }); @endscript ``` ### Per-event styling [](#per-event-styling) The original version of this package required a single set of styles from a single function; this was not flexible enough for our requirements at 383 as we needed to have different colours and content for different events. Therefore you can now provide a lot more details in the event array; here is an example from our implementation: ``` public function events() { return $itemCollection->map(fn (ItineraryItem $event) => [ # These items are standard as in the original package: 'id' => $event->id, 'resource_id' => intval($event->start_at->format('Ymd')), 'title' => $event->name, 'starts_at' => $event->start_at, 'ends_at' => $event->end_at, # These are the additional properties we have added: 'header' => $event->start_at->format('H:i') . " - {$event->name}", 'header_class' => 'bg-blue-500 text-white p-1 text-xs font-bold', 'body' => $event->description, 'body_class' => 'bg-blue-100 p-1 text-xs whitespace-pre overflow', 'footer' => " ", # If this is empty, the footer won't be used, so we use a space to ensure it is rendered 'footer_class' => 'bg-blue-500 text-white p-1 text-xs font-bold', ]); return $return; } ``` By including this information in the event array, you can now style the header, body and footer of each event individually. This allows you to have different colours, fonts, sizes, etc. for each event, and to include additional information in the event card. Original Information -------------------- [](#original-information) Warning None of the following information has been explicitly updated in the 383 environment, and as such everything that follows should be considered as potentially out of date information, and may not apply. ### Testing [](#testing) ``` composer test ``` ### Todo [](#todo) - Add drag-to-resize functionality - Fully remove old implementation quirks and redundencies - Ensure package is self-sufficient and does not rely on external scripts ### Changelog [](#changelog) Please see [CHANGELOG](CHANGELOG.md) for more information what has changed recently. Contributing ------------ [](#contributing) Please see [CONTRIBUTING](CONTRIBUTING.md) for details. ### Security [](#security) If you discover any security related issues, please email instead of using the issue tracker. Credits ------- [](#credits) - [Andrés Santibáñez](https://github.com/asantibanez) - [All Contributors](../../contributors) License ------- [](#license) The MIT License (MIT). Please see [License File](LICENSE.md) for more information. ### Health Score 38 — LowBetter than 84% of packages Maintenance51 Moderate activity, may be stable Popularity17 Limited adoption so far Community12 Small or concentrated contributor base Maturity60 Established project with proven stability Bus Factor2 2 contributors hold 50%+ of commits How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~11 days Total 7 Last Release 375d ago ### Community Maintainers ![](https://www.gravatar.com/avatar/5497bae5ba869e14821b6d8e27e650d014bb5ec227235252376247bb6ca0a638?d=identicon)[Team383](/maintainers/Team383) --- Top Contributors [![asantibanez](https://avatars.githubusercontent.com/u/5126648?v=4)](https://github.com/asantibanez "asantibanez (23 commits)")[![SteJaySulli](https://avatars.githubusercontent.com/u/60765965?v=4)](https://github.com/SteJaySulli "SteJaySulli (14 commits)")[![barryvdh](https://avatars.githubusercontent.com/u/973269?v=4)](https://github.com/barryvdh "barryvdh (5 commits)")[![stojankukrika](https://avatars.githubusercontent.com/u/10199584?v=4)](https://github.com/stojankukrika "stojankukrika (2 commits)")[![edwinvdpol](https://avatars.githubusercontent.com/u/9265514?v=4)](https://github.com/edwinvdpol "edwinvdpol (2 commits)")[![fwartner](https://avatars.githubusercontent.com/u/6692500?v=4)](https://github.com/fwartner "fwartner (1 commits)")[![wilburpowery](https://avatars.githubusercontent.com/u/15817188?v=4)](https://github.com/wilburpowery "wilburpowery (1 commits)") --- Tags asantibanezlivewire-resource-time-grid383group ### Code Quality TestsPHPUnit ### Embed Badge ![Health badge](/badges/team383-livewire-resource-time-grid/health.svg) ``` [![Health](https://phpackages.com/badges/team383-livewire-resource-time-grid/health.svg)](https://phpackages.com/packages/team383-livewire-resource-time-grid) ``` ### Alternatives [asantibanez/livewire-charts Livewire Charts 896960.0k5](/packages/asantibanez-livewire-charts)[asantibanez/livewire-calendar Laravel Livewire calendar component 96883.3k1](/packages/asantibanez-livewire-calendar)[asantibanez/livewire-select Livewire dropdown select component 520138.4k2](/packages/asantibanez-livewire-select)[asantibanez/livewire-resource-time-grid Laravel Livewire resource time grid component 2308.1k](/packages/asantibanez-livewire-resource-time-grid)[asantibanez/livewire-status-board Livewire component to show models/data according to its current status 34115.4k](/packages/asantibanez-livewire-status-board) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)