Plugin Friendly SketchUp 2014

john2

Instead of we sketchup users bugging plugin makers to upgrade their plugins for v2014, is there a possibility that the guys at Google SketchUp edit the software architecture of sketchup so that older plugins are still compatible and SU 2014 users can easily work in it?

Dave R

So you're suggesting that SketchUp go back to using an older version of Ruby? That defeats the benefits of using the newer version of Ruby. If you want to stick with the old Ruby then go back to using an older version of SketchUp.

By the way, it hasn't been "Google" SketchUp for some years.

john2

@dave r said:

So you're suggesting that SketchUp go back to using an older version of Ruby? That defeats the benefits of using the newer version of Ruby. If you want to stick with the old Ruby then go back to using an older version of SketchUp.

By the way, it hasn't been "Google" SketchUp for some years.

Oops that's embarrassing. Sorry, Trimble Sketchup. And is there a fast way to convert old ruby script to a new one?

Dave R

I expect it depends upon the plugin. If plugin authors are still active and aware of it, they'll be updating their plugins. Most plugins have been updated as it is. What is the big problem with contacting the authors for those few plugins that haven't been updated already? You could just learn Ruby and do it yourself, I suppose.

john2

Im having trouble with compo spray and Didier isnt updating it.

Sent from my Micromax A110Q using Tapatalk

cotty

Maybe you can try to find a workaround with some other plugins? e.g.

tt_su

@john2 said:

Instead of we sketchup users bugging plugin makers to upgrade their plugins for v2014, is there a possibility that the guys at Google SketchUp edit the software architecture of sketchup so that older plugins are still compatible and SU 2014 users can easily work in it?

I'm afraid there is no way we can make SU2014 be 100% compatible with the previous versions. We really want to keep backwards compatibility as much as possible but this time we had to take our medicine and update Ruby.

Ruby 1.8 has reached end of life and is no longer maintained. It also imposed several limitations and issues, particular related to Unicode for handling international characters and security permissions. Since Ruby is a third party product we are somewhat bound by their development.

In this case it was a damned if we do, damned if we don't - and weighing in all pro's and cons the pros for upgrading outweighted the cons. It was the only way we could ensure we have a platform for plugins that we could maintain properly.

Dave R

@john2 said:

Im having trouble with compo spray and Didier isnt updating it.

Sent from my Micromax A110Q using Tapatalk

I expect Didier is busy with other things that are higher priority. Maybe if you offered to pay him for his effort he would be able to make some time for it.

aarondietzen

Alas... that is the life of a plugin developer... You have to roll with the changes of the host program. I will say, though that SketchUp did an excellent job of alerting us to the upcoming changes and gave developers plenty of time to make changes before 2014 was released. Not all software companies give their API users that much time to get compliant before releases!