Managing extensions

Extensions/plugins are an essential way to leverage the best out of SU and tailor it to personal requirements. But the way they operate and are managed is a bit haphazard. You are never sure where they are going to appear in the drop down menus. Some have their own toolbar, others don’t. Some have their own icons but not all. Even under Preferences, if they appear there, the list seems arbitrary and is in no seeming order. That list cannot be sorted or grouped. Worst of all, there is rarely much explanation of how to use the extension. It would be good to have information imported with the extension to tell you where to find it and how to make use of it. Perhaps in the Preferences window there would be a More Info button to access this.

I have just downloaded a new extension (TIG’s Split Sausage). I was told it had installed OK. But can I find it, either under the Preferences list or anywhere in SU? One is left wondering what happened.

I realise this situation arises because there are a lot of people doing their own thing in their own sweet way. But might there not be a kind of protocol that developers are encouraged to use to get some uniformity? Maybe there is but they often ignore it?

Many simple Plugins are NOT Extensions.
So they are not listed in Preferences > Extensions.

With my ‘Split’ tools…
TIG-Split makes the combo-toolbar.
TIG-Split Donut, TIG Split Sausage and also SplitUp
Which otherwise run from typed commands in the Ruby Console…

You have picked a particularly ‘different’ kind of Plugin, since it’s part of a set and although it is at its simplest a stand-alone Console based tool, it is enhanced by its helper Split Tools…

These are over 4 years old…
The raw RB in the original post is an indication that it’s not a complex extension…

These scripts have their own pages in the SCF forums, but are also in the SCF PluginStore as RBZs…
It’s always recommended that you get the latest versions of any tools from there.

It says quite clearly in the SCF PluginStore entry -

Splits a ‘sausage’ shaped face, made with Followme etc into ‘quads’.
To get combo-Toolbar install ‘Split Tools’…
Usage: Tools || Toolbar > Split Tools… > Split Sausage

This is an additional script which is also clearly linked off in the first post.

…Now in Tools > Split Tools submenu. http://forums.sketchucation.com/viewtopic.php?p=386658#p386658

It’s More Info ‘Usage’ says:

Select ONE face and ONE edge that you want to be the ‘seed’ for the
‘quads’ vertices, typically this will be the ‘end’ edge.
Lines are then added between ‘matching’ vertices along the ‘sausage’ to
divide its face into ‘quads’…
If the ‘sausage’ has an uneven number of vertices then the last facet will
be a triangle
Type into the Ruby Console: TIG.splitsausage
OR use Tools > Split Tools… submenu item.
It is one step undoable.

So as a stand-alone you need to run it from the Ruby Console, or by insatlling the helper ‘Split Tools’ it makes a submenu in the Tools menu and a Toolbar

If you had the SketchUcation ExtensionStore³ toolset installed then the Extension and Plugin Managers give you details of non-extension scripts.
If a highlighted Plugin is hosted in the SCF PluginStore then its details are repeated off the web-page…

It also installs the RBZ directly for you with no download required…

4 Likes

A large percentage of these ‘freely shared’ plugins have instructions, it is up to end user to read them…

If you still can’t figure out how to use them, there are often full threads dedicated usage where you can ask questions…

I find this to be very disingenuous to the script writers who dedicate free time to help others achieve better workflows…

Some of the Authors have moved on from the community…

Other’s [mainly Tig] spend many hours updating older ones and I find any request to impose ‘conditions’ on these endeavours offensive…

john

3 Likes

I really wasn’t meaning to antagonise anyone. It was an observation/analysis, not a criticism. I absolutely agree that people do give freely of their time and many of us are the beneficiaries.

If the fault was mine for not reading instructions, I will happily take the blame.

1 Like