![]() ![]() ![]() you should find the the GEM spec has an attribute for almost all those in the SketchupExtension object plus quite a few more. The SketchupExtension class object contains (at present,) only a handful of attributes, but if you compare them to those within a GEM spec. Right now, if you have ever used the SketchupExtension class, you should realize that it creates a Ruby object (before an extension / script is actually loaded and only loads it if the user has 'checked the box' in the Extensions page of the Preferences dialog. Myself, and I think Jim Foltz prefer something that is 'live-Ruby.' Where a ruby script, (or a module distro'd with Sketchup,) tasked with Extension management, can actually ask the plugin / extension about itself. I think they were 'leaning' toward a RDoc-like syntax. And we've discussed something similar before in other threads, Rick Wilson had an experimental approach that was implemented as embedded documentation, that would need to be parsed. Oh OK, well then debugger is the wrong term for what you want. Not, a all, I 'm meaning some sort of version control / monitor / indicator, so if I write what I think is a really simple beginners type ruby, with only SU6 on a Mac available for testing, my editor can highlight the fact I've used a Win32 only method that also needs MeshAdditions.rb + Geodesic.rb or wharever.
0 Comments
Leave a Reply. |