@linea said:
Above all else I would like to see Google buying shed loads of all the plugins out there, polishing them and incorporating them properly into the core product. No need to reinvent the wheel.
I agree with you to a certain extend. not all tools make sense to be implemented into the core SketchUp. but there are many tools that are so native to my workflow now (and surely I am not the only one) that it would make perfect sense to incorporate them.
just take 'select instances' (lets you select all copies of one component just with one click) or Chris' 'arc centerpoint finder'. these are already native tools to me. and when I work on another machine thad doesn't have these scripts, I feel utterly crippled in my workflow.
I would like to think of it as a great 'open beta area'. all the plugins are being thoroughly tested and developed by the community and the ruby master minds. once it becomes clear, that one script is extremely useful to the majority of SU users, Google could really buy the plugin from it's creator, and properly implement it. it doesn't have to be all the plugins (there are far too many)
but take as an example fredo's on surface tools, paired with joint push pull (which is sort of a ':pushpull:-on surface'). Google could buy these plugins (and fredo would at last be properly rewarded for his hard work (appart from the gratitude and worship from thousands of members)). and by properly implementing it into the SU user interface, they could create one toggle-button to swich from 'normal mode' to 'on surface mode', making all the native drawing tools work 'on surface'. thus you only had one more button added to the UI, instead o a whole new set of drawing tools...
so in some cases, the implementation of a plugin would make SketchUp a lot more powerful, while keeping it's simple and easy workflow...