@hil I wish the iPhone 3g design could make a comeback. I liked having lock on top and then the rocker on the side. I also liked it when phones were small enough to be used with one hand.
I guess this can count as porgress, found where Megaman Legends keeps the collision hull.
Does any one actually like the volume rockers and lock button on the same side of the phone? I generally end up locking my phone when I only meant to turn the sound down at least three times every day.
@codythedragonrude I was thinking it might be possible to have a single "master" SOC to host a network file server, and run a screen, and then have serveral "slave" SOC's connect share the same storage space. Though the issue there would be how to sync the keyboard, mouse, clipboard between the different machines.
@DashEquals I kind of imagined your profile as a winking terminal pic.
@chmod777 it will probably take my stupid brain a little bit of time to comprehend that. But basically similar to the way OpenGL 2 improves over OpenGL 1 by moving buffers to the GPU, OpenGL 3 improves on OpenGL 2 by introducing batch draw calls by using VAO's (i think).
@chmod777 So basically I'd be happier to have the option of being able to not use them in a OpenGL 3.0 context, until i had a better idea of what they are, how to implement them correctly and understand the concepts of why they're there.
As opposed to now, where it's like, "these VAO lines are here in the program because otherwise it won't run without them".
But I guess I should do the due diligence thing and try to figure out at least what they are and why they're (probably) helpful.
@chmod777 With OpenGL 3, what I can gather is that a VAO is group of buffered objects (maybe). It's a probably a lot of laziness on my part for not doing my due investigate what these are and how to implement them.
My complaint is that mostly for simple applications in OpenGL, they probably won't be complex enough to benefit from the functionality that VOA's offer in favor of using OpenGL at the functionality of OpenGL 2.x.
@chmod777 It's not that I have my heart set on not using them as much as I find them confusing.
OpenGL 1.0 is an intuitive to use API where you set attributes and draw primitives to the screen.
In OpenGL 2.0 you can see how they made that more efficient by moving the vertices and texture data to the GPU and then offloading what the CPU was doing into OpenGL 1, to the GPU by defining shaders.
@chmod777 Is there anyway to use OpenGL 3+ without VOA's?
@bennydarshan GTK with C or with a different language?
@LibertyPaulM If you had $50 a month to dish out $10 to five different projects a month, which projects would you choose?
Just pushed a new patch to Calligra. This will improve the display of the toolbox in horizontal mode. https://phabricator.kde.org/D18963
@polychrome How about the Librem 5?
@codythedragonrude A misspelling of "Kernel"
Linux Geeks doing what Linux Geeks do..