Docs as always are your friend (although they can be a little vague in places): http://docs.qtile.org/en/latest/#getting-involved
In terms of learn by doing, my personal experience was to just use qtile for a couple of months and take notes whenever something broke or didn't behave the way I wanted it to, then start looking at the relevant files for those issues. Just reading the files goes a long way. As for learning the index file/structure of the project I'd recommend a tool called pydeps. install: `pip install pydeps` then run: `pydeps /path/to/python3.x/site-packages/libqtile` (with /path/to/ replaced with wherever your distro keeps that stuff i.e. /usr/lib/) This will generate a big image file with a graph showing how all the files are connected through import statements. On Saturday, July 17, 2021 at 11:42:16 AM UTC-4 Arif wrote: > I really love the idea anf the fact that Qtile is completely based on > Python. > And the community seems pretty active and helping. > I am new to Python (although I'm familiar with OOP in PHP and also JS), > but I'd like to get myself more into Qtile, learning by doing. > I'm curious what's the "index" file of the project? I mean, where should I > start to understand how things work in Qtile? > -- You received this message because you are subscribed to the Google Groups "qtile-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qtile-dev/19d88a51-fc83-4842-bea5-a04cec9e37dfn%40googlegroups.com.
