Hi Chipp,

> 1. I assume just showing edges is the equivalent of rendering in wireframe mode, correct?

Yeah pretty much - there is also a "faint wireframe" mode that objects can be set into which shows a dashed mode wireframe. This is the one you see when you do the Move command for example, the base object goes into faint wireframe mode. But it is also possible to set that mode onto objects by a script.

Check here for some various wireframe scripts:
http://kyticka.webzdarma.cz/3d/moi/#SetSelectedObjectToWireframe


> Is there a way to *selectively* show edges for different objects?

I think there's one for that on the above link.


> Is there a shortcut to toggle 'wireframe' vs 'shaded' mode?

Not for the entire display if you're asking about a full viewport display mode. In Moi setting a wireframe mode means setting some properties on particular objects, either setting the objects into faint wireframe mode or hiding their faces and leaving only edges showing.



> What about just showing faces?

Go to the Scene Browser Types section, and on the entry for "Faces" right click on the eye icon, that shows faces and hides every other type of object.


> 2. Is it possible to *select* objects by either clicking in the styles or objects window?

Yes, selections on a scene browser item are done by clicking on the selection indicator dot, the same place that shows the selection status. See the help topic for the scene browser for more information:
http://moi3d.com/3.0/docs/moi_command_reference11.htm#scenebrowser


> 3. How does one install the command line field in the UI?

It's already in there by default, the XYZ input box on the bottom toolbar which shows and allows you to enter x,y,z values for the current point being picked is also a mini command line entry, you can type a command name there and push Enter as an alternate way to launch a command. You can push Tab to put focus on there before typing.


> 4. Is the UI still fully configurable with HTML? For instance, would this still work? I notice it was
> created PRE version 3 and I think I remember reading somewhere that the customization features
> changed for V3.

The UI is still configurable with HTML but many of the specific things have changed, for example in V2 and before most of the controls and rounded corners and such were done by bitmap images. In v3 much of the structure of the UI has changed to instead use CSS properties for things like rounded corners. So the way the HTML is all set up is fairly different between v2 and v3 and you can't just take HTML designed to work in v2 and just directly put it into v3 and have it work. So no that old UI won't be possible to work in v3.

Hope this helps!

- Michael

Thanks Michael! Much appreciated.

One more question, I spend some time in my job tweaking CSS for websites, etc.. Is it possible to change the whole look and feel of the GUI via CSS? If so, is there a decent workflow for this (firebug for MoI?).

OK. I see now how to select objects in styles by clicking on a non-visible button to the right of the style. I get that it's not really PC anymore to have a bunch of 'toggle' button icons next to a list--> too much visual noise.

As a thought experiment in GUI design, I might try and put that same icon to the LEFT of the Styles where 2 other controls (visible and color) are. That way when a 'partial' selection is made, it would show up half-filled (as it does now on the right), thus helping the user to notice it as the OTHER buttons are toggles as well. Just an idea.

The contrarian argument, especially for CAD programs, is that users sooner or later get around to noticing the 'half-selection' mode and inquire. Certainly we aren't building an ATM (where everyone needs to be successful on the first interaction with the interface), and CAD programs can certainly demand more 'learning' from users.

Overall, I'm most pleased at the progressive disclosure of your GUI. Nice job. Clearly a lot of attention has been paid.

Hi Chipp,

> One more question, I spend some time in my job tweaking CSS for websites, etc.. Is
> it possible to change the whole look and feel of the GUI via CSS? If so, is there a
> decent workflow for this (firebug for MoI?).

Yup, pretty much the whole UI for controls like buttons and such is controlled by .css - most of it comes from moi.css which you can find in the \ui subdirectory. On the Mac right-click and choose "show package contents" and inside there got o drive_c/moi/ui

But there isn't any special tooling set up to do it, it just involves editing the file in a text editor.

- Michael

Hi Michael,

"But there isn't any special tooling set up to do it, it just involves editing the file in a text editor."

Based on the little bit of sleuthing I did with Max's interface, I suspect the workflow looks like:

Edit CSS / Save..
Launch MoI to view GUI
Quit MoI
Edit CSS / Save
Rinse and repeat...

I guess with the source code you can create a manual refresh mode where you don't need to quit MoI each time an edit is made to the CSS. Is there any way for us to check the CSS changes w/out relaunching?

Hi Chipp,

> I get that it's not really PC anymore to have a bunch of 'toggle' button icons
> next to a list--> too much visual noise.

Yeah I don't like it so much when there is a big grid of controls on each line. It tends to be nice for readability if there's often not much there other than the text itself.

But those invisible clickable areas (which are not always invisible, just in their "off" state like hidden has no eye showing, and unselected has no selection dot showing), could get a bit tricky to use if the were nested a couple deep, so I wanted to only put them on the left and right outside edges.


> As a thought experiment in GUI design, I might try and put that same icon
> to the LEFT of the Styles where 2 other controls (visible and color) are. That
> way when a 'partial' selection is made, it would show up half-filled (as it does
> now on the right), thus helping the user to notice it as the OTHER buttons are
> toggles as well. Just an idea.

It could probably work ok that way, the thing I would not like is when both visibility and selection were in their off states that would be a kind of an especially big blank area on the left side, and maybe targeting the inside click zone would be a little less natural than when they're all the way to one side.


> The contrarian argument, especially for CAD programs, is that users sooner or
> later get around to noticing the 'half-selection' mode and inquire. Certainly we aren't
> building an ATM (where everyone needs to be successful on the first interaction with
> the interface), and CAD programs can certainly demand more 'learning' from users.

MoI is largely based on this philosophy where I figure it's not so bad to require a certain level of learning to uncover more functionality over time...

The problem with trying to make every single function immediately obvious right off the bat is the amount of clutter that accumulates with everything trying to get a lot of simultaneous attention, that then brings about various unpleasant side effects of it taking longer for the "everyday" stuff because there's so much stuff to wade through. It's a big focus for MoI to try and keep the basic stuff have a fast and fluid streamlined feel to it.


Thanks, - Michael

Hi Chipp,

> I guess with the source code you can create a manual refresh mode where you don't need
> to quit MoI each time an edit is made to the CSS. Is there any way for us to check the
> CSS changes w/out relaunching?

There is a mode you can set in moi.ini to prevent file caching and make MoI reload files from disk each them they are called. See here for that:
http://moi3d.com/forum/index.php?webtag=MOI&msg=6727.2

But that mainly helps when you are developing a command where the command's UI gets reloaded and cleared out every time the command is run.

But the main UI is not really like that since it stays loaded after MoI has started up.

You might try sticking a button in the UI panel itself (like in CommandBar.htm or SidePane.htm) that has onclick="window.location.reload();" in it, I'm not entirely sure if that will work but it might.

There are also a few additions in MoI to try and make it a bit easier to build reusable controls in HTML, there's a templating system that expands a control to have additional HTML content inside of it, like for instance when the UI loader sees a <moi:CommandButton> element in the HTML, it checks for a template named CommandButton.htm and if found it fills the interior of the element with the content from that template file. That makes it easier for controls to have some interior structure of HTML to them but only need to be declared as a single element at the main document level.

- Michael