Calendar Operation

[blondie63]

Before the release of Backpack Calendar I had built my own code starting from this component:
but not the daily and weekly views!
Now I'm considering the change since Backpack Calendar is already part of my license. However, I have some questions:

1. Is localization planned?
2. Is there complete documentation? for example, what does the mapped field "all_day" mean?
3. Is it possible to set Calendar View as the default for Crud?
4. Are the month, week, day buttons customizable?
5. When will it be integrated into Backpack Demo?

Thanks

[tabacitu]

Hi there,

Happy to help:

1. Yes, it's got language files for en and pt. If you translate it to a different language, you can do that in your own project, but consider sending it over so other people get it too 😉 it's a win-win - one less file for you to maintain.
2. The add-on page is the docs page - https://backpackforlaravel.com/products/calendar-operation . We tried to have everything needed there. If something's missing, glad to add. And all_day event is an event that does not start at a specific hour and end at a different hour. It's the entire day. Like someone's birthday. Or a public holiday. Those are all-day events.
3. Yes. You can use the CalendarView without having the ListOperation present. Just point your menu item to /products/calendar.
4. Yes.
5. Our team was working on the integration in the demo. But we stopped, in order to add full support for Laravel 11 - that was urgent and took more time than we expected.

Cheers!

[blondie63]

@pxpm I've these:

PHP VERSION:

PHP 8.3.4 (cli) (built: Mar 12 2024 23:42:26) (NTS)
Copyright (c) The PHP Group
Zend Engine v4.3.4, Copyright (c) Zend Technologies
with Xdebug v3.3.1, Copyright (c) 2002-2023, by Derick Rethans
with Zend OPcache v8.3.4, Copyright (c), by Zend Technologies

LARAVEL VERSION:

10.48.4.0

BACKPACK PACKAGE VERSIONS:

backpack/basset: 1.3.0
backpack/calendar-operation: 1.0.4
backpack/crud: 6.7.1
backpack/devtools: 2.0.3
backpack/editable-columns: 3.0.8
backpack/generators: v4.0.4
backpack/language-switcher: 1.0.1
backpack/pro: 2.1.11
backpack/settings: 3.1.0
backpack/theme-coreuiv2: 1.2.3

Maybe backpack/calendar-operation: 1.0.5 is for Laravel 11 ?

[blondie63]

Running composer outdated i've this:

Direct dependencies required in composer.json:
backpack/devtools 2.0.3 3.1.0 An admin UI for generating migrations, models and CRUDs
backpack/language-switcher 1.0.1 2.0.0 Language Switcher for Backpack
doctrine/dbal 3.8.3 4.0.1 Powerful PHP database abstraction layer (DBAL) with many features for database schema introspection and management.
kitloong/laravel-migrations-generator v6.11.1 v7.0.1 Generates Laravel Migrations from an existing database
laravel-lang/common v3.1.1 6.1.1 Easily connect the necessary language packs to the application
laravel/cashier v14.14.0 v15.3.0 Laravel Cashier provides an expressive, fluent interface to Stripe's subscription billing services.
laravel/framework v10.48.4 v11.0.8 The Laravel Framework.
laravel/sanctum v3.3.3 v4.0.0 Laravel Sanctum provides a featherweight authentication system for SPAs and simple APIs.
nunomaduro/collision v7.10.0 v8.1.1 Cli error handling for console/command-line PHP applications.
phpunit/phpunit 10.5.14 11.0.7 The PHP Unit Testing framework.
stripe/stripe-php v10.21.0 v13.14.0 Stripe PHP Library

@pxpm Do you think that all this new are for Laravel 11 ? backpack/devtools 3.1.0 for example..

[pxpm]

you can use any of those packages with either L10 or L11.

We were able to make it compatible, so you can use 1.0.5 with L10 and with L11.

It's possible that our private repository didn't piked it yet.
I need to probably increase the frequency that the repository gets updated, but I didn't had much time left for those "side optimizations".

Cheers

[blondie63]

@pxpm Ok now I have downloaded 1.0.5, I would advise you to space out the three month, week, day buttons a little
Stuck together like this they are not pleasant.
What do you think about it ?

[pxpm]

If you happen to work on it, feel free to open an issue either here, or in crud repository with a screenshot of what you achieved.
If we all agree it looks better than what we currently have, we can add it to the package for everyone for sure👍
At the moment we don't have time to dedicate to such small details, but if they pop in front of our eyes and they look good, it's easier to squash them in the package.
It should probably be just one line of css or something.

Cheers

[jcastroa87]

Due to no activity, I will close this issue, but please feel free to re-open or create a new one.

Cheers.