[OpenGL] reduce window width

[diver]

This is hrev40927, gcc4hybrid.

Current GUI:



Mockup:



Alternative mockup:




BTW, there is no OpenGL component in trac.

[humdinger]

Your mockups do look nicer. I have to wonder, however, why there even are OpenGL preferences in the image, if there isn't anything to tweak or fiddle with...

[diver]

I was wondering the same thing the other day.

[yourpalal]

One thing I think is worth mentioning is that we can't shorten the renderer name easily in the preflet. This is fetched from opengl, and it could be anything, so it isn't as simple as replacing a string in the code. We could cheat it of course, and hardcode it, but then this already not-so-useful preflet becomes even less useful.

That said, the renderer name could be changed in the source of our mesa port, which would shrink the window a bit without any extra layout work.

I like moving the logo down, and adding the stripe, which seems to be a theme in the Haiku UI nowadays ;) It's worth noting that the logo.png file used appears to have a white background (viewing it in Github, at least), so that will have to be worked around. I'm not sure if BView supports color-keyed alpha while drawing, but if it does, that would work nicely.

[anevilyak]

Replying to yourpalal:

I like moving the logo down, and adding the stripe, which seems to be a theme in the Haiku UI nowadays ;) It's worth noting that the logo.png file used appears to have a white background (viewing it in Github, at least), so that will have to be worked around. I'm not sure if BView supports color-keyed alpha while drawing, but if it does, that would work nicely.

If I understand your intent correctly, it does, c.f. ​http://www.haiku-os.org/legacy-docs/bebook/TheInterfaceKit_Drawing.html#TheInterfaceKit_Drawing_Drawing_Modes - specifically with respect to drawing mode B_OP_ALPHA and consequently the appropriate parameters for SetBlendingMode()

[yourpalal]

Replying to anevilyak:

Replying to yourpalal:

I like moving the logo down, and adding the stripe, which seems to be a theme in the Haiku UI nowadays ;) It's worth noting that the logo.png file used appears to have a white background (viewing it in Github, at least), so that will have to be worked around. I'm not sure if BView supports color-keyed alpha while drawing, but if it does, that would work nicely.

If I understand your intent correctly, it does, c.f. ​http://www.haiku-os.org/legacy-docs/bebook/TheInterfaceKit_Drawing.html#TheInterfaceKit_Drawing_Drawing_Modes - specifically with respect to drawing mode B_OP_ALPHA and consequently the appropriate parameters for SetBlendingMode()

That's not quite what I meant but it'll work. Color-keyed alpha (not sure if that is exactly the right term) is supported for instance in SDL, where you can set an alpha-key, and any pixels of that exact value will be dropped when blitting, achieving a 100% transparency effect for those pixels.

At any rate, logo.png could be edited to include an alpha-channel, or the programmer could introduce one, or could achieve a similar effect to color-key alpha by setting the white pixels to B_TRANSPARENT_MAGIC*.

Anyway, it can certainly be done, and shouldn't be too tricky either.

[axeld]

I would actually prefer to remove the application altogether. It could be a demo app instead (since it's definitely no preference application), but even then, I see little reason to include this in the image.

[yourpalal]

Replying to axeld:

I would actually prefer to remove the application altogether. It could be a demo app instead (since it's definitely no preference application), but even then, I see little reason to include this in the image.

I think you're right, actually. At the moment, we only have one gl implementation, so the data in the preflet will never change. If we ever have 3D accel, we could reintroduce the preflet, or integrate it into Screen or something. If users had the option to switch between hardware/software rendering, this info might be of some use, but right now, it might only be slightly useful to someone wanting to write an opengl app in Haiku, in which case they could query this info themselves very easily.

[kallisti5]

Things have changed a bit since this ticket was opened.. Attaching the current "3D Rendering" preference pane.

I've also cut down on a few string lengths in the OpenGL add-on

[kallisti5]

This was all completed.

[jscipione]

Added the stripe and gears in hrev43991.

Replying to yourpalal:

Replying to axeld:

I would actually prefer to remove the application altogether. It could be a demo app instead (since it's definitely no preference application), but even then, I see little reason to include this in the image.

I think you're right, actually. At the moment, we only have one gl implementation, so the data in the preflet will never change. If we ever have 3D accel, we could reintroduce the preflet, or integrate it into Screen or something. If users had the option to switch between hardware/software rendering, this info might be of some use, but right now, it might only be slightly useful to someone wanting to write an opengl app in Haiku, in which case they could query this info themselves very easily.

The application is useful despite the fact that it is purely informational. It details what your current Mesa version is and what it's capabilities are. This is useful to more than just developers. It should be taken out of Preferences though and activated from a button in AboutSystem instead.

[axeld]

Replying to jscipione:

The application is useful despite the fact that it is purely informational. It details what your current Mesa version is and what it's capabilities are. This is useful to more than just developers.

How so? Haiku releases will come with a specific known Mesa release. While I agree that it would be nice to see that version in AboutSystem, the rest is pretty much useless information, unless you are really interested in those details. I would assume that 99% of the people in almost any room are not. I'm certainly not, and I have even a good idea what OpenGL is :)

It should be taken out of Preferences though and activated from a button in AboutSystem instead.

I disagree. It should be removed from the base completely. It should be moved into an optional package -- those that are interested in running it, could then just do it.

The CPU info that sysinfo dumps is certainly useful, too, even for more people; it just has no place in the GUI. As the Mesa info isn't even machine depending but is static throughout all installations, I wouldn't even see the point if that information was interesting to more people.