- Wavebox github Patch#
- Wavebox github code#
- Wavebox github free#
- Wavebox github windows#
I'm all for performance enhancements and features, but not at the expense of the ability to read the code. But I chose WB because it was open source.
Wavebox github Patch#
We'll be pushing patch releases to Wavebox Classic until everyone's in a position to move across to Wavebox 10.Īny time line on this? I ask because, as I mentioned, I have a "just so" config on Linux. While this is a legitimate issue, I can't help but feel it's not the main one. Anything beyond that on a best effort basis I would think to be perfectly reasonable for a small team trying to make a commercially viable product. You could just say "here's the source, now you're on your own".
Wavebox github code#
Your obligations beyond providing the code are entirely what you make them. Is there really no middle ground between devoting excessive resources to tooling and support with open source and going completely opaque? It is open source after all. we've decided not to open source the new version of Wavebox, as we feel that the time we're going to spend providing build tools and build support could be better spent.
(Which is just signing in to all the services and arranging things, not as bad as a stick in the eye, but not as nice as importing a config file either.) So, unless I missed a step (which I grant is likely) anyone choosing to go forward with the black box version has to recreate their entire setup from scratch.
But WB10 installed on Windows, and it wouldn't import the v4 config from my Linux export.
Wavebox github windows#
I just had to set up Windows for the first time in a while and downloaded Wavebox because I've been using it since wMail and consider it indispensable for a work machine. Paid users just need to sign in to Wavebox 10 with their account and will have all the new features ready to go.
Paid users just need to sign in to Wavebox 10 with their account and will have all the new features ready to go. Wavebox github free#
Free users can use exactly the same features in Wavebox 10 as what they can currently. We'll be pushing patch releases to Wavebox Classic until everyone's in a position to move across to Wavebox 10. This source code, repository and existing downloads on Github will stay exactly where they are. We've already renamed the Github project to be Wavebox Classic, but that's about the only change. If this is something you're interested in, drop support an email and we'll open up an early preview when it's ready. We're working on some new developer tooling for those that want to customize and extend Wavebox 10, this will be an enhancement to the chrome extension API that we already ship with. If you want to try it out, we'd love to hear what you think! Already, we've seen that devoting this time to the main app has allowed us to bring some amazing new features into Wavebox 10, including privacy locking, broad extension support, massive performance improvements and more. It's because of this we've decided not to open source the new version of Wavebox, as we feel that the time we're going to spend providing build tools and build support could be better spent working on features that people have been asking for. In contrast building Chromium from source is much more involved, requiring a specific build environment and also taking at least 10 hours to build on a top-of-the-range MacBook Pro. It's installable and buildable with little more than 3 commands and only takes a few minutes to compile. One of the main driving factors of this has been the time it takes our small team to provide a buildable toolset that can facilitate building from Github vs the time we could be spending on new features as requested by users.įor comparison, Electron has been designed from the group up to get started quickly and easily and this is echoed in the Electron version of Wavebox. We've also taken the tough decision not to publish the rewritten version on Github. This is a huge step forward from the old version that runs on top of Electron. Here at Wavebox HQ, we've been busy rebuilding Wavebox from the ground up and rewritten it directly on top of Chromium.
0 kommentar(er)
