Install = manually copy the DLL file.
(Delete the DYLIB it is a Mac platform library not for Windows platform.)
Connect = Start the SketchUp.exe with a debug switch and port parameter as explained in the linked page. Then open your project in RubyMine.
TestUp is too complex for newbs. Again use one of the simple example extensions.
No you set up a new project as explained but point to your own projects “src” folder instead of the TestUp project’s “src” folder.
You can “see” it if it makes itself known usually via menu item commands or toolbar buttons.
The menu commands can be either menu items in the main menubar or conditional commands that appear in the right-click context menu. (How these things are done are covered in other forum topics. Use the magnifying glass icon to search [top right].)
If it does not have any LoadError(s) or SyntaxError(s) it might be usable.
This is what testing and debugging is for, to find RuntimeError(s).
A forum post is not a good place to teach program debugging.
I’m sure that there are better documents and tutorials out on the internet.
In fact, the basics of programming in any language is a prerequisite to learning how to debug.
This assumption is incorrect. SketchUp extensions are event driven code. It is the user’s actions that trigger events which an extension responds to.
The simplest user events (as already said) are clicks on UI elements like menu items or toolbar buttons.
More complex events would be importing geometry from an external file or exporting to an eternal foreign file format of some kind other than
The most complex events are reacting to the modification of model objects such as it’s various collections, most often it’s Entities collection, using observers.
Regardless, in order for an extension to do anything within SketchUp, it must be loaded into SketchUp’s Ruby process. There are two ways. Automatic, if it is a proper extension accessible to SketchUp. (Either installed into the user “Plugins” folder or loaded via a “pointer script” in the “Plugins” folder that adds a special project repository path to Ruby’s
$LOAD_PATH array and instructs SketchUp to load the project.)
The second way is a manual load from the Ruby Console command line using Ruby’s global
It is easiest to catch and fix LoadErrors and Syntax errors using a manual load from the console.
Once these are fixed, you would use the debugger to find and fix any RuntimeError.
The path is correct if you have SketchUp 2018 installed.
Did you add content roots ? per …
I am not a RubyMine user myself, so I can’t really help when it doesn’t work correctly.
I would say concentrate on learning the basics of Ruby programming first and then later more complex things like debugging.