ibizaman
commented
8 years ago This has been and is still essentially a one-man effort project. I'm not particularly fond of applying design pattern OOP techniques everywhere though. That being said, now that the code is clearly not a proof-of-concept anymore and that redbaron's usefulness is certain, we should think about how to refactor the code.
I also noted speed issues when using redbaron to do real-time parsing in an editor. Some parts are even very slow like the bounding box related code. Parsing speed is also a concern as can be seen in https://github.com/Psycojoker/baron/issues/61.
The TODO file is a good starter point to know what the near future looks like. More issues were discussed on the chat like how to handle comments well.
Every idea on how to improve redbaron or baron is very welcomed! Do not hesitate to come on the #baron freenode IRC channel. :smiley:
What you are implementing is legendary tool to manipulate with code. But your hacking implementation is very uncomfortable to use and slowly. For instance, if you give to RedBaron file about 100 lines of logical code, it will works for more than 10 seconds. I'm suggesting you to choose style guide and more OOP approach using design patterns. Good example to start from is documentation of flask webframework.