mirror of
https://github.com/Helium314/HeliBoard.git
synced 2025-05-16 23:12:47 +00:00
update readme and todos
This commit is contained in:
parent
439330fc12
commit
4af0f2d3a1
4 changed files with 38 additions and 17 deletions
|
@ -60,13 +60,16 @@ open class KeyboardBuilder<KP : KeyboardParams>(protected val mContext: Context,
|
|||
|
||||
// todo: further plan
|
||||
// add a parser for more complex layouts, and slowly extend it with whatever is needed
|
||||
// try to make the format compatible with florisboard, or just take it if it has all we need
|
||||
// if so, then make sure additional stuff unwanted in this app (if there is some) does not cause errors
|
||||
// probably need to deal with different functional key definition style, but only if allowing numpad and similar layouts
|
||||
// initially it's just alternative key for shifted layout
|
||||
// so dvorak and azerty and colemak and others can be migrated
|
||||
// try to make the format compatible with florisboard
|
||||
// migrate symbol layouts to this style
|
||||
// better before user-defined layouts
|
||||
// should be straightforward to do
|
||||
// allow users to define their own layouts
|
||||
// simplified if possible, but json should be fine too
|
||||
// migrate keypad layouts to this style
|
||||
// will need more configurable layout definition -> another parser, or do it with compatible jsons
|
||||
// allow users to define their own layouts (maybe migrate other layouts first?)
|
||||
// need to solve the scaling issue with number row and 5 row keyboards
|
||||
// write up how things work for users, also regarding language more keys
|
||||
// readme, maybe also some "help" button in a dialog
|
||||
|
@ -98,14 +101,8 @@ open class KeyboardBuilder<KP : KeyboardParams>(protected val mContext: Context,
|
|||
// migrate emoji layouts to this style
|
||||
// emojis are defined in that string array, should be simple to handle
|
||||
// parsing could be done into a single row, which is then split as needed
|
||||
// this might help with split layout (no change in key size, but in number of rows!)
|
||||
// this might help with split layout (no change in key size, but in number of rows)
|
||||
// write another parser, it should already consider split
|
||||
// more dynamic / lazy way for loading the 10 emoji keyboards?
|
||||
// use recyclerView instead of a keyboard?
|
||||
// or recyclerView with one keyboardView per row?
|
||||
// could be possible if creating the keyboards is fast enough... but also need to check whether it's ok for memory use and stuff
|
||||
// migrate keypad layouts to this style
|
||||
// will need more configurable layout definition -> another parser
|
||||
// migrate moreKeys and moreSuggestions to this style?
|
||||
// at least they should not make use of the KeyTextsSet/Table (and of the XmlKeyboardParser?)
|
||||
// migrate other languages to this style
|
||||
|
|
|
@ -566,6 +566,17 @@ private class BaseKey(
|
|||
)
|
||||
|
||||
// todo (later): may depend on language for non-latin layouts... or should the number row always be latin?
|
||||
// best have number row layout in a file, and get layout file dependent on keyboard layout and some setting
|
||||
// setting should be sth that goes like "prioritize localized numbers"
|
||||
// idea for behavior:
|
||||
// if no extra local number row: number row like now, no number row shows numbers in moreKeys
|
||||
// for other numbers:
|
||||
// language-dependent number moreKeys (latin numbers on localized variant, and localized variant on latin numbers)
|
||||
// show whatever is selected as number row, or as morekeys if number row is off
|
||||
// but then how to simply put both latin and local number in moreKeys when number row is disabled?
|
||||
// consider that numbers may have more moreKeys...
|
||||
// idea: field [numbers] where in the next line the numbers are space-separated in order 1-9 and 0
|
||||
// would be simpler to handle than moreKeys
|
||||
private val numbers = (1..9).map { it.toString() } + "0"
|
||||
|
||||
// moreKeys for numbers, order is 1-9 and then 0
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue