Frustrated with rubies

lapeno82

My turn.

progessbar.rb is pretty basic. I wrote it a few years ago to fill a gap of no progress bar at all. However, it was still insufficient in its first incarnation since when SU would freeze up due to intense processing of a Ruby script in a single, synchronous thread. Anytime the SU user interface would need repainting, too bad, because the Ruby script had the thread, and the user interface, unfortunately, does not get serviced. When SU hits this wall, the first thing to go is the SU menu bar, then the whole UI freezes, even the status bar where progressbar.rb makes it updates.

I then changed progressbar.rb to add an estimated completion time. It's my opinion that this change transformed it into more than just a "cool animated bar", and into something that was actually pretty useful, since you now know that the script will take another 5 seconds, or 20 minutes, or whatever, and you can adjust your finger-tapping-on-the-desk to some other activity as needed.

The next phase will be a dialog, similar to what Rick mentioned, that will provide a persistent external dialog that will allow you to cancel the script at any time. This will require programming changes to the invoking script, but it will be a big improvement in long running rubies that you choose to cancel.

Todd

Is this already available?

Chris Fullmer

Nope, not yet. It would be a welcome addition though!

Chris

AdamB

So I saw this thread and spend half an hour playing with building a WebDialog progress bar.

What I planned to do was have a Javascript driven animated progress bar and a simple call from Ruby to update the percentage.

The html/js is trivial but I came unstuck because the WebDialog stops when Ruby runs. Now I don't understand because I supposed that the browser would be running in separate native thread.

Somebody mentioned they'd experimented earlier with this and failed. Was this the same issue?

Adam

baz

@thomthom said:

Yea, it's frustrating when a plugin is doing heavy work and you can't tell if it has hung or not.
But mind you, close the Outliner when you run plugins that does heavy operations. That thing really slows things down. You can often see it flicker like mad.

I read somewhere that having the outliner open can be useful, when it stops flickering you know the ruby has finished.
I cant remember which ruby, but I was having constant crashes because I was trying to undo before the operation was complete - being an impatient sob. I tend to forget that I've just asked su to recalculate 10000000000:) faces and edges!
baz

ps: personally, what I really need is a simple way to organise my rubies, for example like 'bookmarks' in 'firefox', most used at the top etc.
As for frustration, compared to windows updates and getting hassled to constantly upgrade by everybody else, I for one am eternally grateful for the fantastic generorsity of the ruby wizards, even the ones who charge. Eg:Sub divide and smooth, 20 bucks, no worries.
(note to self: must donate to fredo for Freescale, wow!)

thomthom

I would strongly recommend NOT having the Outliner open for the sake of using it as a 'progressbar'. It increases the time it takes to complete the task many times. And it's prone to cause crashes.

Jackson

In XP just left-click once on the blue bar at the top of your SU window- it'll turn white until SU or the Ruby Script has finished its task. Hardly a progress bar, but it's better than nothing.

honoluludesktop

As to the original post, and as a Architect that used to program, there was little that I did that was completely with out some kind of anomalty. Bugs can be outside your ability to clean up, especially when they deal with the OS, or the programming language itself. But, because it was my program, and I knew where the problems (most of the time) were and simply avoided them. A user on the other hand would be totally frustrated, thinking that he is entitled to a perfectly running program. And he is, especially if he paid for it. Sometimes the application of a program becomes so complex, that with infrequent use, you forget how to use it. And so on, and so on, and so on.

So, regarding my use of rubies that are written by non-professional programmers: 1) I would use a ruby as a application (withing its limitations), and 2) when there is no other way to do what I am trying to accomplish. If I could write them however, I am sure my opinion would be different.

RickW

@adamb said:

So I saw this thread and spend half an hour playing with building a WebDialog progress bar.

What I planned to do was have a Javascript driven animated progress bar and a simple call from Ruby to update the percentage.

The html/js is trivial but I came unstuck because the WebDialog stops when Ruby runs. Now I don't understand because I supposed that the browser would be running in separate native thread.

Somebody mentioned they'd experimented earlier with this and failed. Was this the same issue?

Adam

Yes, same issue. Scott Lininger is aware of the problem.

RickW

@baz said:

ps: personally, what I really need is a simple way to organise my rubies, for example like 'bookmarks' in 'firefox', most used at the top etc.

Have you looked into Organizer?

baz

@unknownuser said:

Have you looked into Organizer?

Thanks Rick, tho it seems a bit complicated for my poor brain. I can see myself getting in lots of trouble trying to organise subfolders, especially considering the apparent dependency of various rubies on each other.
baz

rv1974

Here's the cry of my soul:
Ruby people please stop adding your stuff to right click menu!
The 2nd: Why not concentrate all rubies in plug-is menu? (jumping thru draw-tools-
plug-ins is extremely annoyng!

Chris Fullmer

#1 - I actually mostly agree with. I don't like rubies to clutter up my right click context menu also.

#2 - Some author feel that there plugin should be placed in the camera menu since the plugin might be directly related to the camera. Or the Draw menu, or the tools menu. Some authors just want ttheir plugin to go into the most logical menu, and in their mind, generic "plugins" is not it. I think I agree with you on this one too. I'm not a big fan of having to remember where all the rubies I've installed have put themselves.

Of course, I'm sure there are plenty of different opinions out there....

Chris

Gaieus

This is why some ruby scripters create their own menus instead. Like Chris Fullmer tools and such...

Chris Fullmer

I agree, that shows my preference. I make a single menu within the plugins and everything I've written goes in there (except I hear that there might be a bug that is creating 2 menus - which I might have a fix for). But all my scripts should also be compatible with Rick's organizer for people who want to organize them on their own.

Chris

Gaieus

I was just teasing, Chris.

RickW

@rv1974 said:

Here's the cry of my soul:
Ruby people please stop adding your stuff to right click menu!

Interesting - I took Windowizer4 out of the right-click menu, and people were requesting I put it back!

Just shows there are different preferences for different people...

charly2008

There are a lot of good and helpfull Ruby plugins.
In addition, there are many Ruby plugins that contain similar functions.
It seems to me that the Ruby plugins are being integrated into Sketchup without a system.
I'm confused about, that the Ruby plugins can be found in three different menus.
Through this it is sometimes difficult to find the Ruby plugin you need , especially if one does not use the expansions every day.
The next difficulty is, serves itself to remind which Ruby plugin for which Function. Because the titles are often not very helpful.
It would be very helpfull if the Plugins could be organized by the user according to there main Functions
for example:

Plugins folder-------->Bezier tools
Push and Pull tools
Scaling tools
Extrusion tools

I don't know if that is possible and how to do it. Please excuse my bad English

Karlheinz

Gaieus

There is actually an "Organiser" plugin that would allow you to do it (at least with "compatible" plugins). I haven't used it yet but it may still be useful.

RickW

@baz said:

@unknownuser said:

Have you looked into Organizer?

Thanks Rick, tho it seems a bit complicated for my poor brain. I can see myself getting in lots of trouble trying to organise subfolders, especially considering the apparent dependency of various rubies on each other.
baz

Two things:

Organizer can do a simple test and notify you if you move any required files, letting you know you need to put them back in the Plugins folder. Also, creating a backup of your Plugins folder prior to using Organizer can save you some headaches.
I do offer support for all my scripts, so if you have questions, just ask