Re: [Pharo-users] AST Inspector
What is it drawn with? On Mon, Jun 29, 2015 at 6:53 PM, Mark Rizun mri...@gmail.com wrote: Need a bit of anti-aliasing for the round shapes :) Right :) I wonder how it will look with a long method: they usually have rather flat ASTs that would result in a wide diagram. Yes it will be pretty huge. However, 1) there is an option to scale the tree (nodes) 2) most of the methods should not be very long ;) Still the problem remains. I built it rather for fun and my possible future work, than for wide usage. But I think it may be nice for some people to one-click and see the tree, and play with it. About GT inspector: yes I've seen the ast view in inspecotr, and it's amazing how many things we can do with it.
Re: [Pharo-users] AST Inspector
Need a bit of anti-aliasing for the round shapes :) Right :) I wonder how it will look with a long method: they usually have rather flat ASTs that would result in a wide diagram. Yes it will be pretty huge. However, 1) there is an option to scale the tree (nodes) 2) most of the methods should not be very long ;) Still the problem remains. I built it rather for fun and my possible future work, than for wide usage. But I think it may be nice for some people to one-click and see the tree, and play with it. About GT inspector: yes I've seen the ast view in inspecotr, and it's amazing how many things we can do with it.
Re: [Pharo-users] AST Inspector
Simple morphic. 2015-06-29 20:01 GMT+03:00 Peter Uhnák i.uh...@gmail.com: What is it drawn with? On Mon, Jun 29, 2015 at 6:53 PM, Mark Rizun mri...@gmail.com wrote: Need a bit of anti-aliasing for the round shapes :) Right :) I wonder how it will look with a long method: they usually have rather flat ASTs that would result in a wide diagram. Yes it will be pretty huge. However, 1) there is an option to scale the tree (nodes) 2) most of the methods should not be very long ;) Still the problem remains. I built it rather for fun and my possible future work, than for wide usage. But I think it may be nice for some people to one-click and see the tree, and play with it. About GT inspector: yes I've seen the ast view in inspecotr, and it's amazing how many things we can do with it.
Re: [Pharo-users] AST Inspector
Hi, If you already seen the GT view, perhaps this means that you were missing something. Is it only the visual representation, or do you miss something else? Also, you can embed your view directly in GT. Cheers, Doru On Mon, Jun 29, 2015 at 6:53 PM, Mark Rizun mri...@gmail.com wrote: Need a bit of anti-aliasing for the round shapes :) Right :) I wonder how it will look with a long method: they usually have rather flat ASTs that would result in a wide diagram. Yes it will be pretty huge. However, 1) there is an option to scale the tree (nodes) 2) most of the methods should not be very long ;) Still the problem remains. I built it rather for fun and my possible future work, than for wide usage. But I think it may be nice for some people to one-click and see the tree, and play with it. About GT inspector: yes I've seen the ast view in inspecotr, and it's amazing how many things we can do with it. -- www.tudorgirba.com Every thing has its own flow
Re: [Pharo-users] AST Inspector
If you already seen the GT view, perhaps this means that you were missing something. Is it only the visual representation, or do you miss something else? For the most part the missing part is the visual representation of the tree. However I did this little inspector because in the future I (maybe) will implement a tool for code rewriting like Rewrite Tool, but only the rule creation process will be done by manipulating visual representation of the ASTs. Also, you can embed your view directly in GT. That's cool and I know - seen it at Pharo Days :)
Re: [Pharo-users] AST Inspector
That's a nice project. A visual rule creation tool would be so cool! Doru On Mon, Jun 29, 2015 at 7:21 PM, Mark Rizun mri...@gmail.com wrote: If you already seen the GT view, perhaps this means that you were missing something. Is it only the visual representation, or do you miss something else? For the most part the missing part is the visual representation of the tree. However I did this little inspector because in the future I (maybe) will implement a tool for code rewriting like Rewrite Tool, but only the rule creation process will be done by manipulating visual representation of the ASTs. Also, you can embed your view directly in GT. That's cool and I know - seen it at Pharo Days :) -- www.tudorgirba.com Every thing has its own flow
