Cool! On 08.04.2013, at 13:08, Gisela Decuzzi <giseladecuzzi@gmail.com> wrote:
Hi, I'm just starting an internship for 3 months and we were talking about the scope for my time here. This is a summary of what we have discussed: The main objective it's to improve the AST and use it to implement as many improvements and refactors/transformations as we can to help the programmer. Some ideas: - distinguish the code scope (for example, when you have lot of blocks all together when you pass over with the mouse that it get special something to understand where you are)
+1. The same for the keyboard would be cool (maybe highlight brackets like it's done in some popular text editors)
- make suggestions depending on what you have selected. Example if it's a variable rename it, or find accesses (â¦)
You should take a look at Pavels work Periscope (http://smalltalkhub.com/#!/~PavelKrivanek/Periscope) which is his take on LightTable and does some of these things already.
- highlight selectors - implements some rules to help code improvement, for example if you select some part of the code and it's repeated you can do an: extract method, or extract to variable transformation. - improve the navigation between static code - review the refactoring API and evaluate a change for admitting AST nodes and avoid the use of strings...
Please let me know your thoughts about it and if you have more ideas, they are always welcome.