ludo | A libretro frontend written in golang | Emulator library

So basically I tweaked your code a bit and in the process got to learn about ViewGroups also. Thanks for that!

I have commented the explanations of the changes made in code you can refer to that and if any doubt please feel free to ask..

Try:

Each item in df.Neighbors is a string. When you iterate over it with for neigh in neighbors: You add each character of the neighbor to the node. For example the first node looks like

I didn't get your point in asking user for multiple actions (Select option & Click on the button) where he could get respective options just by selecting any of the option in your code. Anyway you can try below code where you get next question by clicking on the next button. (This could be the example of hardcoding :P)

A possible soultion would be to define the games before we render the options.

You should use recursion to achieve this like shown:

In case you want to set the title to the keys.

Few problems here. Currently nothing invokes renderRow method + it returns single item instead of array (row). To fix single row rendering you can:

The use of functions and operators almost always precludes the use of indexes. INSTR() is definitely in that category. LIKE with a constant pattern and no wildcards at the beginning of the pattern is an exception.

If you need to handle such scenarios, you might investigate other databases (notably Postgres) that have a wider range of indexing capabilities -- including indexes that can help for partial string matches.

You can also implement something similar in MySQL by using n-grams. However, this would require a separate data structure and a bit of complication.

You may also be able to implement this using a full text index -- but munging the data on input. For instance, you might extract adjacent three letter combinations and add them to the index, so: