@Edward Yes I agree with you. I wrote a blog which using leo-editor to analyse flutter pugin named fluro offical example.
Here is the blog, but written by Chinese. I want to share some leo-editor usage experience. https://blog.csdn.net/weixin_42553238/article/details/121447509 fluro example: https://github.com/lukepighetti/fluro/tree/main/example I think that users who using leo-editor can read source code as a literal article. They should not jump here then jump there again and again. 在2021年11月16日星期二 UTC+8 上午5:04:34<[email protected]> 写道： > You could look at Reportlab or Pillow ... > > On Monday, November 15, 2021 at 3:07:35 PM UTC-5 Edward K. Ream wrote: > >> This morning I had what I sometimes think as an Aha/Doh moment :-) The >> background: >> >> - I've often said that creativity happens only in the presence of a juicy >> problem. >> - Leo is a tool for understanding complex programs. >> >> Putting these two together: the way forward may involve studying complex >> python programs and seeing what new tools/inventions result. >> >> pylint and mypy are immensely complex programs, so studying them will >> surely call forth new tools. >> >> *Summary* >> >> Finding new ways of understanding mypy and pylint seems like a juicy >> project. But perhaps an even juicier project may appear :-) >> >> Edward >> > -- You received this message because you are subscribed to the Google Groups "leo-editor" 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/leo-editor/6317aa1b-28ef-474f-af70-45c03b798489n%40googlegroups.com.
