keyboardkit / keyboardkit Goto Github PK

While working on the 2.0 release, some parts of the major rewrite didn't get tested. They should be tested before the 2.1 release.

AutocompleteToolbarLabel currently always left-aligns its text. It should have an additional centered label with the same size as the view, that is only visible when scrolling is not needed.

Hello,

Whenever I try to run project in my device. It throws below error

Could not find module 'KeyboardKit' for target 'arm64-apple-ios'; found: x86_64-apple-ios-simulator, x86_64

Can you help me with this error please ?

Thanks

Native keyboards switch from numeric/symbol keyboard to the alpha one when space is tapped. KeyboardKit should do that as well, or at least provide a configuration to do so.

KeyboardKit has a .switchKeyboard action that switches to the next system keyboard. However, it should also have a .toggleKeyboardMode action, so that buttons on the keyboard can toggle the keyboard state.

In the native keyboard, this is used by:

• shift
• shift lock
• numeric toggle button
• symbol toggle button

The demo keyboard's emoji button should look more like the native one.

How do you actually do this?

"Enable full access in the Info.plist, if your keyboard needs it"

The native iOS keyboard has swipe support for its buttons, which means that you can have two actions on the same button. This should be added to KeyboardKit as well.

The backspace action should have a press/repeat behavior, so that a user can press and hold to repeat that input until the user releases it.

Besides button rows and collection views, KeyboardKit should have a toolbar item type. The demo keyboard should use one of these items as well, to show how they're implemented.

The button shadow that is being used in the demo keyboard doesn't look like the system shadow. It should.

If you are typing and the cursor stands after the last character, the timer-based text position adjustment makes the context change and the suggested current word changes.

I recently came across KeyboardKit repo and I had a quick question regarding building the keyboards.

Basically, I want to make a keyboard that just changes the label and output of the spacebar but the main problem is I don’t have a ton of experience with Swift. I’ve followed all of your instructions for installation and everything seems to be okay, but in your examples you have files such as AlphabeticKeyboard.swift and DemoKeyboard.swift, but I’m not quite sure where these files would go in my Xcode project. I currently have a blank project with a custom keyboard extension and a default KeyboardViewController.swift file.

I know it’s not your job to teach me Swift or anything but I was wondering if you could point me in the right direction. If I could get one of your example keyboards running then I could start to play around with it myself and figure it out but getting off the ground has proved tricky.

Any information you can give will be greatly appreciated.

At present autocomplete is a view that you can add labels etc to. It would be nice to have the option to have a scroll view that you can add an overflow of results.

KeyboardKit should support dark mode, if it requires more dark mode support than it already has.

The documentation of the various classes and extensions are not great and should be improved.

I cloned this project , when I ran it ,after I tap the textview , just a system keyboard showed up, I didn't see the keyboard with the layout in the gif demo .

I forgot to add the correct permissions when creating the new demo project. The demo keyboard therefore crashes when saving photos to the photo library.

I think it'd be better if the demo keyboard has one button to switch to emoji keyboard and one to switch to a custom one, since the keyboard now uses different button types.

The native autocomplete toolbar behavior is to display three autocomplete suggestions and distribute them evenly within the toolbar. If their text is too long, the labels become scrollable.

However, some users have expressed their need to display more content. They therefore need the toolbar to be able to give its views as much space as they need, and that the entire toolbar should become scrollable instead.

I have therefore added enableScrolling() and disableScrolling() to AutocompleteToolbar in KeyboardKit 2.6.1.

Hi!
Are there any solutions for long tap like this?

When tapping keyboard buttons, the standard animation is too slow compared to the native one. It feels like typing under water.

Hi @danielsaidi,

How are you?

I believe it's missing NSPhotoLibraryAddUsageDescription in info.plist in DemoKeyboard.

Keyboard[25674:404407] [access] This app has crashed because it 
attempted to access privacy-sensitive data without a usage description.  
The app's Info.plist must contain an NSPhotoLibraryAddUsageDescription 
key with a string value explaining to the user how the app uses this data.
(lldb) 

Regards,

Thiago

Hi again,

Please, how can i create a Top Actions like this image below? I try to change this function:

 static func bottomActions(leftmost: KeyboardAction, for viewController: KeyboardViewController) -> KeyboardActionRow {
        let actions: [KeyboardAction] = [unathenticatedAction(for: viewController), leftmost, switchAction(for: viewController), .space, imageAction(for: viewController),  .newLine]
        let isEmoji: Bool = viewController.keyboardType == .emojis
        let isImage: Bool = viewController.keyboardType == .images
        let isUnathenticated: Bool = viewController.keyboardType == .custom("unathenticated")
        let includeImageActions: Bool = !isEmoji && !isImage && !isUnathenticated
        return includeImageActions ? actions : actions.withoutImageActions
    }

But no success :(

Also how can i add textfield inside a custom keyboard and label to it?

Sorry for my beginners doubts.

Some examples:

Thank you so much for the help

Hello,

Can we use this release custom ios keyboard?

Can you please point to some examples to autocomplete models, both for offline dictionary and online dictionary
also if there is a way to use google services.

thanks,

AutocompleteBugFixTimer solves the iOS text change bug by forcing the cursor to move. However, moving the cursor also causes any presented text field callouts to disappear.

I wanted to solve this by adding knowledge of the last detected current word to this timer, and avoid moving the cursor if the current word hasn't changed, but this does not work, since the cursor must be moved to update this information.

I can't find a way around this. I will release the autocomplete feature with this limitation, but would love to find a way to solve this problem in a better way.

In KK 2.0, I will replace much of the earlier logic with stack views. This brings devs a lot of flexibility, but I'd like to add apis that make it easier to configure them for e.g. center display.

https://github.com/danielsaidi/KeyboardKit/blob/ac0d9d1dcf066bb2f0d875313f7385102de6c094/Sources/KeyboardKit/Actions/KeyboardAction.swift#L122

Currently, moveCursorForward is mistakenly set to adjusting text position by -1. Changing it to 1 should fix the bug.

Hi,

Thank you for the great work, I'm just wondering if we can adjust the height of keyboard button in order to align the style to the build-in system keyboard.

Thanks

In KK 2.0, I base the keyboard on constraints instead of manual developer commands. However, there are a bunch of constraint warnings in the demo project, that I'd like to fix.

Just like the native iOS autocomplete toolbar. Scrolling text should fade out horizontally.

Hi Daniel!
How to use another language in this keyboard?

Thanks!

textDidChange(_ textInput: UITextInput?) isn't called when the user types and modifies the textDocumentProxy text. It gets called when you change the cursor position, however.

This function is critical to get autocomplete to work. Since the keyboard detects no text change, the autocomplete request isn't triggered and the old suggestions are still displayed even when the user writes or deletes text.

You can recreate this bug by selecting any word in the demo app. The demo autocomplete provider will change its suggestion to match the current word. Now type some text into the proxy - the old suggestions will not be replaced. Now change the cursor position - the app will now display new suggestions to match the new current word.

What is even more serious, is that even if you set a scheduled timer to trigger every second and call the autocomplete request, the currentWord will remain unchanged.

KeyboardKit should support Swift Package Manager.

The standard behaviour of double tap on "Space" button is to close the sentence. At the moment this could be implemented by handling "space" taps and measuring time between them. But it would be great if library contains a special action type for that event that would allow to specify which particular character has to be sent to proxy on space double tap.

Hi,
I was trying to implement the RepeatingGestureRecognizer for backspace - however it leads me weird results. Either the timer doesn't get invalidated or timer doesn't execute. So if you can share working code would be great help
Thanks

KeyboardKit should have autocomplete support, so that the keyboard can request auto complete suggestions from a autocomplete suggestion provider.

Hello,

KeyboardKit supports dark mode but I couldn't find the "switch".
I want to enable/disable dark mode

Thank you

The current tap gesture recognizer adds a lag to the keyboard buttons, which is notable when you try to type fast. Eliminate this to make the keyboard as responsive as the system keyboard.

Just like the native iOS autocomplete toolbar, AutocompleteToolbar should have separator lines between the suggestions.

Hi,

Becuase there is no space between two Chinese words, so the wordDelimiters won't work in my project.

https://github.com/danielsaidi/KeyboardKit/blob/151c47301b273e9bf5499cc9ec7dba101e4fe9f0/Sources/KeyboardKit/Extensions/UITextDocumentProxy%2BCurrentWord.swift#L74

The autocompleteSuggestions would consider all these characters as one word.

I think the correct way in typing Chinese could be:

• When user start typing, the autocomplete start to match the suggestions.
• When user tap to select a suggestion, the autocomplete stop, this match is finished.
• When user start to type another word, the autocomplete restart to match for the new characters.

The autocomplete should use only the new typing chracters to match the suggestions.

Like this picture below, the autocomplete should only match the new characters hao, and leave the old words.

I'm not familiar with both programming and English, hope you not be confused, very thankful for this great work.

Thank you

Add support for Xcode 11 and dark mode.

Hi, apologies for the repeat message: Is there a way to switch keyboards (yours to standard), programmatically?

Thanks

The keyboard switcher, backspace button, enter button etc. have icons that should be added to the library, as embedded images.

For iOS 12.4, i had added var window: UIWindow? in AppDelegate class to fix the black screen problem.

However, after looking at keyboard settings, i cannot find the keyboard.

But it works well for iOS 13. What is the minimum requirements for KeyboardKit? I will be looking at supporting older devices.

I am also downloading iOS 11.0 to see if it works there as well

Hi @danielsaidi , first of all. Congratulations for your excellent Framework to create Custom Keyboards on iOS. This is helping me a lots to accomplish a personal project.

Could you provide a demo example using Storyboard to create an entire keyboard?

My kind regards,

Thiago

This class is untested since the major 2.0 rewrite. Write unit tests for this class as well.

When switching from a native keyboard to a KeyboardKit one, the absence of audio feedback is annoying. KeyboardKit should provide a way to play audio feedback, as it does for haptics.

Today's toolbar view contains a stack view that can display toolbar items. However, the autocomplete toolbar should be able to enable scrolling, since it may want to display a large amount of items.