Download the PHP package laratribe/native-wheel-datepicker without Composer
On this page you can find all versions of the php package laratribe/native-wheel-datepicker. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download laratribe/native-wheel-datepicker
More information about laratribe/native-wheel-datepicker
Files in laratribe/native-wheel-datepicker
Package native-wheel-datepicker
Short Description A wheel date picker EDGE component for NativePHP Mobile v4 (SwiftUI + Jetpack Compose).
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package native-wheel-datepicker
laratribe/native-wheel-datepicker
A wheel date picker EDGE component for NativePHP Mobile v4. It renders as real SwiftUI (Picker(.wheel)) on iOS and a snapping Compose wheel on Android — not a web view.
Requires NativePHP Mobile v4 and nativephp/mobile-ui.
Install
Composer require is not enough. Register the plugin, then rebuild so Kotlin/Swift are compiled in.
Rebuild the native app (ios or android):
PHP-only changes hot-reload. Native renderer changes need native:run again. Manifest/native path changes may need php artisan native:install --force.
Local path (plugin development)
Configuration
Publish the configuration file (optional, to customize defaults):
This creates config/wheel-datepicker.php. Leave theme keys null to inherit Native UI light tokens (surface, outline, primary, …). Set hex values only to override.
Usage
native:model commits when the user taps Done (compact) or when you use the footer on inline. Use plain native:model or native:model.live — .blur / .debounce are rejected outright (no silent no-op).
Value is empty ('') when value/native:model is left unbound — the wheels still visually center on today, but nothing is committed until the user confirms, so "not selected" stays distinguishable from a real date. Pass default-to-today to opt into committing today automatically instead. Theme null inherits Native UI light tokens; paste a hex or :colors to override.
Events
on-change="method"— wheel settle (optional;native:modelalready syncs).on-done="method"— Done (fires unconditionally on confirmation).on-cancel="method"— Cancel.
_change / _done / _cancel still work underneath (that's the literal
attribute name the element receives) but on-* is the documented, intended
spelling — use it in new code.
Each handler receives a string $value in the picker’s format (default Y-m-d).
Note on reverting to the initial date: If a user opens the wheel, scrolls to another year/date, and then scrolls back to the initial date (e.g.
2026),native:model/on-changetreats it as unchanged (newValue === oldValue) and will not fire. Useon-done="handleDone"whenever you need logic, validation, or state updates to run on every confirmation, even if the value is unchanged:
Year range
Defaults: config('wheel-datepicker.year_start') (1990) through current year + 20.
Min / max date
year-start/year-end only bound the year wheel. To cap the actual selectable
day — "not after today", "18 years ago or earlier", a booking window, etc. —
use min-date / max-date instead. They accept the same formats as value,
including today, and are enforced down to the day on both platforms:
If year-start/year-end are also set, they're narrowed to fit inside
min-date/max-date automatically so the year wheel can never land on a year
the day/month wheels would then clamp back out of. min-date after max-date
throws.
Timezone
min-date="today", max-date="today", and the native "Today" button all
resolve "today" from timezone (IANA name, e.g. Asia/Kolkata) instead of
PHP's UTC normalization disagreeing with whatever clock the device is set to.
Defaults to UTC on both sides if omitted:
Format
PHP date() tokens (Y-m-d) or aliases: YYYY-MM-DD, DD-MM-YYYY, MM-DD-YYYY, and / or . variants.
Only Y, m, d, and separators (- / . `) are supported — anything else (e.g. strayj,n,y`) throws immediately in PHP rather than
reaching the device and parsing incorrectly there.
Locale
locale only changes the month names shown on the drum (en, fr-FR, ja,
…). The value committed over the bridge always stays in format (default
Y-m-d), so parsing on the PHP side never has to account for locale:
Colors
Omitted keys use config('wheel-datepicker.theme'), then config/native-ui.php light tokens (surface, outline, primary, …).
Keys: bg, card, border, text, muted, muted_2, accent.
Size
Values are density-independent (dp / pt). They do not auto-grow on tablets.
visible-items is clamped to 3, 5, or 7. wheel-height defaults to row-height × visible-items.
:size="['row_height' => 52, 'visible_items' => 7]" also works. Per-attribute props override :size, which overrides config.
class="w-full" only stretches the trigger field.
JavaScript / web view
This plugin has no bridge API. Do not import it from Vue/React. Use the EDGE tag in a NativeComponent.
Tests
Pest examples live in tests/ and are meant to run inside a NativePHP Laravel app (Native::test()).
Copy-paste starting point for a host app:
License
MIT
