Heliboard https://github.com/Helium314/HeliBoard
Fork of Openboard
This is a community for talking about and sharing links to ⌨️ you've made/found that features:
Credits:
Heliboard https://github.com/Helium314/HeliBoard
Fork of Openboard
~~ah unfortunately I had to recently take down a post here that recommended HeliBoard,~~
~~- as that project is in violation of OpenBoard's GPL-3.0 license~~
~~For some unknown reason the developers of HeliBoard decided to multi-license with Apache-2.0 and CC-BY-SA-4.0~~
~~- as I wasn't able to find any information that they received explicit consent from all members of OpenBoard about relicensing/multi-licensing~~
~~Hence I can't recommend anyone using that keyboard app until further information is disclosed~~
~~- afaik multi-licensing GPL-3.0 is only possible with other specific licenses such as AGPL-3.0~~
~~just to double-check I searched online and found this:~~
~~license-compatibility~~
~~> Likewise, CC BY-SA 4.0 explicitly permits relicensing modified versions to GNU GPL version 3, but GPL version 3 does not permit relicensing to CC BY-SA. This issue should never arise for software code; Creative Commons says its licenses are not meant for code, and says that the license to use for code is the GNU GPL. But there are other kinds of works, such as hardware designs or game art, where you might have occasion to merge material released under CC-BY-SA with material released under the GNU GPL. This can be done through CC BY-SA's explicit relicensing permission.~~
~~> Unfortunately, CC BY-SA 4.0 does not permit relicensing to future GPL versions. What you should do, when you relicense material under CC BY-SA 4.0 to the GPL, is specify yourself as a license version proxy to indicate whether future GPL versions have been authorized for that material. If someday there is a GPL version 4 and Creative Commons decides to allow relicensing from CC BY-SA to GPL version 4, you as proxy will be able to retroactively authorize use of that relicensed material under GPL version 4. (Alternatively, you can ask the authors of that material to give permission right away.)~~
Edit: I'm blind
I havent looked into FOSS keyboards much but It looks like they're licensed as GPL on the repo. The CC BY-SA is for the project icon
https://github.com/Helium314/HeliBoard/tree/main?tab=readme-ov-file#license
ah rip I didn't see that and I've made a mistake
much appreciated!
this is totally a valid suggestion!
thank you for the comment🤗
Whoo, since you're here, can I ask, does any of these (or others) have swipe-typing? And since you've used these, are they good?
Any better features than gboard? (Apart from the obvious data stealing)
Any gripes?
I just started using Heliboard yesterday. It doesn't offer its own swipe typing library. But you can give it the library file from GBoard (link on their github) and it'll use that to enable it.
For gestures/swipe-typing I do know that all 3 have that feature
unfortunately I can't provide reviews on it as I still tap to type, haven't had time to retrain unfortunately
For Florisboard's features I really like their sea of options for customizability:
For Unexpected Keyboard, the features it provided was actually unexpected:
I haven't used Thumb-Keys but I've seen good reviews about it so it's worth a shot as well 👍
Heliboard is currently the most reliable swiper.
You have to load the library for that separately, but it makes it very easy to do.
As far as features that gboard doesn't have, the main one for heliboard is that you can edit the secondary characters. That's pretty damn nice. For one, it means you can set it up to mirror the secondary layout of any keyboard you're used to, reducing any swtich caused learning curve. For another, if you want to roll your own entirely, it's super easy to do, even easier than multilingo, which is the only other editable keyboard I'm aware of.
Gripes? Honestly, only that it isn't a copy kid Swype, my preferred keyboard. It can get close, but it isn't exactly the same. It'll r be what I switch to if I ever have to give up swype.