I don't think I know what most people typically expect. I don't know what chrome is, and I'm all for flexibility, but short of some crazy winamp skins in the late 90s, I've never noticed anything being particularly more fancy than amiga500 widgets. Win95 added something. Osx added a bit more, but a box with a label that reverse highlights when I select it is really all I'm expecting.
I rarely create guis, mostly just cli tools. Is there a good intro to basic ui theory so I bdont upset people with higher expectations in the rare event I do create one?
"Chrome" is the term for the OS provided border around the window. It offers anchoring points to resize the window; a place to click for dragging; as well as the buttons for closing, maximizing, minimizing. Without chrome, you can't do any of those things, so the window would be fixed in size and place. To get that functionality back, you have to manually code it into the app.
Fun fact: Chrome, the browser, is named ironically. Compared to other browsers at the time, Chrome had almost no chrome around the window content. That was one of the product's signature differences: its UI was so simple that there almost wasn't any UI, allowing users to focus entirely on the content. Thus, calling it Chrome was very funny.
The 2013 Chromebook Pixel followed this naming theme. The screen was so dense that you couldn't see the pixels.
I rarely create guis, mostly just cli tools. Is there a good intro to basic ui theory so I bdont upset people with higher expectations in the rare event I do create one?