Replies: 6 comments 9 replies
-
@tnylea I was just about to cross reference this discussion on this one here. Since you are removing voyager what are you going todo instead? I do see that Laravel 11 support is enabled which is amazing!!! :) |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
I think you guys already know my stance on Wave V3. Couldn't be more excited. Makes the devs job so much easier. I assume API will be standard out of the box again? Is this a full rebuild or an upgrade of V2? I am just curious if I will be able to upgrade from V2 is all. I see filament is going to be used. Is it possible to have the admin panel as a separate package so people can chose which panel they prefer? Personally, I prefer Voyager. However, you customize one admin panel, you can customize them all. Preferring Voyager is an opinion really. I have not tried Filament yet, is it better than Voyager? I though Dev Dojo managed Voyager now? Any particular reason Voyager was passed on? Sorry man, I am just curious. If you are considering Teams integration, I would highly recommend JetStream/Fortify unless the plan is to make it custom to Wave V3 but even then you could integrate JetStream. |
Beta Was this translation helpful? Give feedback.
-
Will we be able to upgrade from 2.2.0 along with using the newest features introduced in Wave 3? P.S. I think packaging Wave making it |
Beta Was this translation helpful? Give feedback.
-
Hello guys. Thanks for the update on v3. I am also very excited and can't wait to get my hands around a combination of Wave + filament which I adore and have used for many projects now. I don't think voyager is bad (don't get me wrong but what I can do with filament and it's full ability with Livewire 3 + AlpuneJS is amazing and I am sure this will lead to a much bigger interest of the final version from other devs being still just Filament Devs. I would.allow to second the option to upgrade Wave from one to the other version. (v2 to V3) As many of us already have some projects with Wave 2 and we can all benefit from the upgrade. One other thing I would suggest is to focus a bit more on theming the admin(allowing custom templates to be implemented). I know filament already supports theming which can be extended further allowing everyone to grab a custom/preferable admin and use it's templates.to adapt the views etc. Maybe one other thing can help too - modularity of features (like Laravel Modules or else) which would allow the community to build around some module/plugins to be proud and share/sell even depending on the amount of work etc. And lastly, but not the least - update the video gallery as to be honest this was one weak point of.Wave SAAS as I was enjoying the learning curve but from some point there weren't many more new videos. Well If.I get.some.more ideas, I will definitely share and.would.likw to take the chance to thank you for all the efforts on behalf of all the happy wave.saas community users! |
Beta Was this translation helpful? Give feedback.
-
@tnylea , would you be able to share an estimated timeline for Wave 3.0? |
Beta Was this translation helpful? Give feedback.
-
The purpose for this discussion is to highlight some of the features/improvements that will be added to Wave V3.
If there is anything specific you would like to see in the new release, be sure to post your comments/ideas below.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions