To keep it as simple as possible, I use what ever is selected in the model. Unfortunately SketchUp's selection tool doesn't select materials and layers. I haven't yet decided how to expose other entities in the UI.

AttributeInspector has an API: You can type in a Ruby Console:
entity = Sketchup.active_model.materials[0] AE::AttributeInspector.select(entity)
or
entities = Sketchup.active_model.layers.to_a AE::AttributeInspector.select(entities)

It was only released in 2014, but I had worked on it around christmas

I have long been avoiding ruby syntax/methods that were changed in newer Ruby versions. So it works for both Ruby 1.8 nd 2.0, at least from SketchUp 8 to 2014. Did I miss a version setting in the SketchUcation Store?

This is a viewer for entity and model attributes. It keeps the user interface minimal and very efficient: Just like SketchUp's inspector dialogs, it lets you select one or more entities and displays their attributes. By editing the text fields, changes are immediately applied to the entities.

http://sketchucation.com/pluginstore?pln=ae_AttributeInspector

You can select multiple entities at once and add/edit attributes on all of them. Attributes that are not shared by all selected entities are displayed grayed out. If you edit grayed out values, they will be applied to the whole selection set.

Bonjour,
Il n y pas des grandes nouveautés à dire sur SketchUp et Wine parce que ça ne marche pas très différent comme ça marchait toutes les années. Peut-être tu trouves le SketchUp wiki utile.

Il est encore necessaire de changer le clé dans la registry de Windows/Wine pour forcer l'accelération graphique. Wine vien avec son propre "iexplore", basé sure Firefox (CSS3 hourrah!, mais les "action_callback" dans les plugins ruby ne marchent pas). À cause de ça, tu installes "ie8" avec winetricks.

Je n'avais jamais des problèmes avec des driveurs graphiques (soit Intel, soit AMD, soit open-source ou propriétaire), tout parfait (mais il y a aussi des reports contraires).

Tu peux aussi installer la version 2013, mais j'obtiens des erreurs dans la 2014 (ntdll error).

Tell your friend to look for the latest information about Wine (is not an emulator ). Take also a look at this link. It changes a lot, so old threads might be outdated. There is barely any effort to get it work (except disabling software rendering). It works beautifully with hardware acceleration, and Ruby runs better.

I haven't noticed any effort for the Windows/OSX version to share cross-platform technology, that would save time and money and that could ever result in another operating system support.

We could not be more excited than we are, no wishlist for 2015!

Congratulations for this big release!

There is also an approach without making changes to entities:
One could also use a repeated raytest, and let it pass through all faces whose material has an alpha value lower than a threshold, or a texture whose filename endswith "png" (however, scripters can not determine which texture pixels are transparent). Then the last face would be added to the selection.

But as far as I know Ruby's gabrage collector is able to release circular references. The object diagram (from the linked ruby-find-references) looks ok. I haven't yet understood fully understood what is happening.

So if I avoid that the proc includes a reference to the dialog, I can not easily use instance variables in the proc (without using hacks like __send__(:instance_variabe_get))?

I will look into it. Though I don't know what could cause this (the plugin does not use observers, and should not be triggered when you change a layer etc.). Can you tell me how many plugins you have and how components and layers in the model?

Thanks, I'll look into that.
As far as I could analyze my code, it should not permanently keep references of these dialogs. So I've started compiling a patched Ruby version that can reverse-lookup references of an object.

So you want to paint on the current view (ie. paint the object as you see it, rather than in unwrapped mode).
Unwrapped meshes have often an unnatural shape, and what looks like a straight line on the model is not always a straight line in the uv map. That makes working with many uv-mapping tools challenging and requires to think in "uv space".

Once I felt this would more fit the intuitive "SketchUp way". I have some experiments with how painting directly on the model would work. However it's rather a hackish solution and there are latency/precision problems and limitations of SketchUp's API.

The procedure of editing screenshots of the current view works for faces that are faced to the viewer, but not for orthogonal faces (the texture on them would be stretched and low-resolution). I'm sure your workflow is easier to implement in an semi-automated plugin.

Yes, the namespace feature is the last missing piece that doesn't work in some versions of Ruby. I've fixed it, but not yet published, because I also want to inspect a problem with garbage collection (closed AE::Console instances stay in memory).

If they are not good enough for the API, then they would have better never been added to the API by a script.

The concern that these undocumented methods are already widely used, seems to make SketchUp hesitate to make changes (or fix them and add them officially). But at the same time we don't want third-party scripts to modify the API. Wouldn't it make sense to – at least – wrap these methods properly into the DC module, so that it is clear they are not for common use? Deprecate them! Maybe keep aliases that puts "Method rotx is undocumented and deprecated. Don't use it.", but get rid of them from the API namespace.

Waiting will only make them more widely used.

He's been trimbled! Maybe more of us need to join SketchUp to "sketchucationize" Trimble?

By embedding that small snippet in our code, we avoid indeed dependencies that could be broken. But on the other side our copied code doesn't get bugfixed when the shared library or API gets bugfixes.

masterpaul asked for editing a 2d image in gimp, and unfortunately I mistyped and pressed the key right of "2".

Just export as 2d image and open it in Gimp.
Such a plugin would be just as simple as what you can do by hand.
Untested, but something like this line:

file = UI.savepanel; Sketchup.active_model.active_view.write_image(file);system("gimp #{file.inspect}")

I could not find where they sell plugins.
It's wrong to sell free plugins of other authors without permission, equally whether the plugins are free, opensource, or commercial.

Those relevant parts of ruby that you as a beginner need are not different. I'd concentrate on the common denominator (which keeps your scripts compatible no matter what Ruby version is used). The differences lay really in more advanced details.
The poignant guid is quite enjoyable!

Those (the quote) are the type of opinions that I've only heard when the media search hard for a "contra" opinion to have a nice pro&contra. I don't know any person who thinks so.

There is also a small new eurosceptics party in Germany (AfD). What if Europeans elect such alternatives or even Nationalists, that all contradict each other? Can there be an "International Union of Nationalists"?
I think this would be contraproductive. It might be true that we need to optimize the balance of subjects that are better handled by the EU or by individual states, but the way to do this (ie. to agree to increase/reduce EU involvement) can only be a common European way, and not a way of disagreement.

The JavaScript error should be supressed in version 2.1.1.

jolran, I can't reproduce it. When you open the Ruby Console+ for the first time (where it doesn't open), does something appear in the native Ruby Console?