raysarebest / V-A-P-O-R-B-O-A-R-D

๏ผถ๏ผก๏ผฐ๏ผฏ๏ผฒ๏ผท๏ผก๏ผถ๏ผฅย  ๏ผฆ๏ผฏ๏ผฒย  ๏ฝ‰๏ผฏ๏ผณ
6 stars 0 forks source link

Feature request: ๐”‰๐”ฏ๐”ž๐”จ๐”ฑ๐”ฒ๐”ฏ #1

Open juhakivekas opened 6 years ago

juhakivekas commented 6 years ago

I know this is not exactly the most ๐”ณ๐”ž๐”ญ๐”ฌ๐”ฏ๐”ด๐”ž๐”ณ๐”ข thing out there, but I have a real need for a ๐”ฃ๐”ฏ๐”ž๐”จ๐”ฑ๐”ฒ๐”ฏ keyboard for all the soft ๐”Š๐”ฌ๐”ฑ๐”ฅ๐”ฆ๐”  stuff I produce on a daily basis. There is no license or contribution guidelines in the repository, so I hope that I could fork this and make a pull request, unless you're interested in adding a small feature to this amazing application

What I've used so far: https://yaytext.com/fraktur/

raysarebest commented 6 years ago

Hey! I didn't include a license because I sell this on the App Store for 99ยข, and I didn't know how that would work with any open-source licensing. As long as you're ok with me using your code and keeping the little bit of money this app makes every month, I'm totally ok with you submitting a PR! Of course, I'd give you a shoutout in the release notes, and a free copy if you haven't bought one already

Before I ended up getting interested in other projects, I was refactoring this code a bit so it wasn't so terrible (in its current state, I wrote the majority of this app in about 4 hours one night while I was in high school), and I was considering what the best way to add a feature like this would be. I feel like it should be a button on the keyboard somewhere so it's a fast switch, instead of in the accompanying app somewhere. Also, how would it signal to the user obviously what kind of text it's about to type (๏ฝ†๏ฝ•๏ฝŒ๏ฝŒ๏ผ๏ฝ—๏ฝ‰๏ฝ„๏ฝ”๏ฝˆ, ๐”ฃ๐”ฏ๐”ž๐”จ๐”ฑ๐”ฒ๐”ฏ, normal, etc.)? Would just changing the characters on the keys be enough, or should some other visual change? These are some things I think still need to be considered before implementing something like this.

If you can implement a good solution to this, I'd love to merge your PR! Otherwise, I've been looking for an excuse to work on something like this for a little while again, so I might get around to it in a few weeks when my plate isn't so full

juhakivekas commented 6 years ago

How about the globe key popping a drop-down menu (like when long-pressing the regular keyboard globe) that has alternatives for all vaporized keyboard, and an option to go back to the normal keyboards (like the globe button now does). This way it should be relatively simple to make a new layout, and it would make it even easier to add another one if there was ever a need for it. In the best case scenario adding a style name and some lists for the mapped letters could be enough to make a whole new layout.

The general look of the keyboard is great, I like the slightly silly colours and I think the ironic misatch of pastel colours and a gothic font, however, the shapes and sizes of the keys are slightly off the normal keyboard, which may or may not be intentional. No-one is going to write a book with the board anyway :P

raysarebest commented 6 years ago

I think I like that idea -- a long press to bring up a menu, and a tap to cycle through, like the QuickType family of keyboards. That also leaves the option to allow the user to choose which ones they wanna enable in the companion app (though they could do it with the normal keyboard settings if we added new keyboards as different targets, though I'll think more about that later).

The color scheme I got from the cover of Floral Shoppe, the quintessential vaporwave album. Tbh I think it looks terrible, but I also think the whole vaporwave aesthetic looks terrible, too :P. If you wanna keep the color scheme the same, I'm ok with that. The key layout isn't exactly the same size as normal, but I've gotten used to it and I think it'd throw off some muscle memories to change it at this point. It's just what I ended up making with Interface Builder/AutoLayout in a couple hours :P

juhakivekas commented 6 years ago

It seems like before making any changes the application would need to be migrated to a new version of Swift. I tried doing this but being unfamiliar with the code I wasn't successful at this.