A few GH improvement ideas

Hi,

I thought I'd share some gh improvement suggestions I've gathered over the past few weeks:

1. Shortcuts

- Alt+Drag = copy component

- Ctrl+Tab = switch between open definitions

- Right-Clicking on selection = editing multiple components, e.g., edit the values of multiple sliders at once

2. Components

- The F(x) components seem redundant. Wouldn't it be simpler to have just the Exp (Variable Expression) and put three predefined instances on the tab instead of having three different components?

The same goes with the merge02, merge03 and merge multiple. It's a pain when you're already using m.03 and decide to add one input - you can't, you have to replug everything back into a m.multiple.

3. GUI

- I know that the tabs show only the most common components to save screen space. I work with a large resolution screen, so I have plenty of space for that. Could there be a toggle to show all the icons on the tab?

- The Markov widget is great, but ... I hardly use it since it's located in the far southwest corner of the canvas. A good place for the widget would be at the top of the search tooltip menu which appears when you double-click on the canvas.

4. Other

- I'd like tha bake function to allow grouping objects according to data tree structure (nested groups)

Cheers,

Replies to This Discussion

Permalink Reply by Damien Alomar on August 31, 2010 at 7:26am

1. Those sound good, but I don't understand how right clicking would work.

2. I see what your saying there. With the function components, having function input is something that some people like (it makes the formula more visible). However, even for functions with 1 or 2 variables I almost always use the F(n) component.

3. I think the icons should just expand to whatever space is available. That way if whether you've got a big screen or a small screen, you can make the most of it.

I agree about the Markov widget being useful, but far away. I really like the idea of it popping up where your mouse is. Underneath the search bar would be cool, but maybe it could pop up when you middle click or something.

4. Interesting idea. That sounds like a good addition to ModeTools

Permalink Reply by greg bethel on August 31, 2010 at 10:45am

1. I like the Alt+drag copy suggestion.

2. It is somewhat redundant, but saves time on the occasions you know you'll only need one (or two, three) variable. I like the F(x) components because they allow plugging a panel with the expression into them. It's easier to edit the expression in a panel than dive down into the expression editor - plus the expression is always visible. Is it possible for the Exp component to have an F input?

Thanks for all the great improvements so far!

Permalink Reply by Jacek Jaskólski on August 31, 2010 at 2:02pm

Hi guys, thanks for the replies.

@Damien
1. Let's say you've got a bunch of sliders with different ranges, values, etc.
I'd like to have the possibility to select them, right-click and change their upper limit, for example, in one go. Similarily, I would select multiple various components, right-click and change the data matching in all of them.

3. -Or we could have the possiblity to choose which icons to show on the tab.
I think 'middle button menu' and 'underneath the search bar' locations are both much better for the Markov chains than the periphery of the corner. BTW if there was a middle button menu, I'd like to have a custom "VIP" section there as well - I'd keep the most frequently used components and user objects for quick access.

@Greg
2. I forgot about the F input in my scenario. I totally agree that it's a handy feature and I use it a lot.
Nevertheless, there's still no need to have 4 different components which do a similar thing. Instead, GH could have only the F(n) component (with the "F input") and the tab would host 4 of its instances with a predefined nr of inputs (much like user-objects).

---
And there's one more:
5. User objects are great, so how about "User object sets"? E.g., IntegerSlider+ListItem or CustomPreview+ColourSwatch or Surface+Sliders+DivideDomain+SurfaceMorph, Galapagos+1000sliders :) etc.

Permalink Reply by David Rutten on September 1, 2010 at 11:08am

1a. Done, available in next release.
1b. Done, available in next release.
1c. I have no idea how to implement this in a predictable manner.

2. Yes, I agree. Eventually the obsolete Fx and Merge components will disappear entirely, but probably not before I redo the Variable Parameter UI.

3a. Done, available in next release.
3b. Yup, Markov should be repositionable just like Compass. I won't get around to this soon though. It's quite a lot of work and not a lot of gain considering some of the other things I could be adding.

4. Baking needs to be seriously rethought as well. I think the current baking features are very inadequate.

--
David Rutten
david@mcneel.com
Poprad, Slovakia

Permalink Reply by Jacek Jaskólski on September 1, 2010 at 1:34pm

Great!
Thanks David.
What about nr 5, is it a reasonable request? Would it be hard to implement?
Maybe it'll make sense to introduce a feature like this with the return of the cluster...
Anyway, thank you again for the incredible job you're doing developing the software.
Cheers,
JJ

Permalink Reply by David Rutten on September 1, 2010 at 2:00pm

Hi Jacek,

it's not at all difficult, but there are some issues that need looking into. For example, a single object would have an Icon override, but if the UserObject contains multiple components, where does the icon go? Should I place a Group around the objects and assign the icon to the group?

--
David Rutten
david@mcneel.com
Poprad, Slovakia

Permalink Reply by WT4 on September 1, 2010 at 2:15pm