Google Reply Window
Today I submitted a feedback form to Google. Eyep, things will definitely be changing ‘round these parts…
I’m feeling frustrated with the design of the new reply window. Having to click the formatting A to bring up the window to select a formatting option is a headache enough, but having to click another button on that to bring up another window to indent/deindent/comment is a huge pain. Since that second window closes whenever I press a button, indenting something multiple times requires me to go through this process over and over.
I’m having a similar issue with inserting links; needing to mouse over the + to bring it up as an option is an extra step that I do not understand the necessity of. This UI feels like a house where everything is neatly packed into boxes. It looks nice and clean, but you need to unpack and repack the whole damn thing every time you need your car keys.
There’s a ton of potential whitespace all along that lower bar that could be used for common functions, but it’s being “taken up” (only kind of because of that strange mouseover plus thing) by buttons that are going to see significantly less use (I have never “inserted an invitation” into an email, ever).
I realize that Google is a giant and you’re unlikely to push through changes because of one bit of unsolicited design feedback from the internet, but graphical simplicity is NOT the same as simplicity of use. The Google aesthetic is beautiful because it’s easy to use and its form follows that, but strong-arming the form to be “simple” can undermine what that form stands for. Thank you.
Here we go, Rubicon is now an open-source project; you can now download its code, art, and music from Rubicon’s repository over at Github.
To compile the code, you’re going to need the proprietary Blitzmax compiler. You have to buy a license to create distributable executables, but they also offer a free version that you can use to compile and run the code for yourself.
Please forgive the comments, for the nights were long and the puns were many.
A designer/scientist does not "express himself". We come up with a process that we think may produce some result (interesting, illuminating), carry out that procedure, then with fresh eyes look at the outcome to judge its actual result. Is it what we were expecting? Do we need to tweak the process? We must be able to honestly see and report what is there in order to provide the feedback that advances our knowledge and our art.
Quick 1.2 patch
Anonymous asked: Android port? :)
I wish. Blitzmax is great in that it makes porting to the supported platforms really easy, but mobile is not on that list. Once I release the source code (I’m still putting that together, I promise!), I’d be overjoyed to see that happen by somebody who knows what they’re doing better’n me.