These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Player Features and Ideas Discussion

 
  • Topic is locked indefinitely.
Previous page123
 

Unintended Genetic Discrimination? EVE's Color Blind.

First post First post
Author
Previous Topic Next Topic
Mark Androcius
#41 - 2013-06-24 10:21:06 UTC
imbaRabbit wrote:
I understand what you're trying to say, but do you have any clue how EvE code looks like?


Nope, 11.9 GB says enough though ( audio and video takes up only 972 MB ), 10.7 GB just in files in the main folder.

imbaRabbit wrote:
Anyway, I do hope they're not attacking their own database with silly requests such as 'text(#).getColor()'.


They'd be getting the color from a local file ( the xml file ).
I don't know if text comes from database or client side ( i think it's client side ), but in both cases they'd still need to grab the text codewise and they'd still need to change that code to reflect this change.

https://androcius.wordpress.com
Dristan Evrard
Federal Navy Academy
Gallente Federation
#42 - 2013-06-24 12:21:52 UTC
Reuben Johnson wrote:

There isn't any common color scheme the devs can configure to. I've learned to adapt baed on true colors and how I actually see them.
I know grass isn't orange. even though that's how I see it..so when I see that shade, i know it's really green. You start messing with base colors and you screw up people like me who've learned to adapt what they see with what it actually is.


You may not have adapted as well as you think. Did you know for example that your toon has a rather sickly yellow color, or can you honestly say this was fully intentional? And anyway, what works for you doesn't work for everyone. You are likely to have quite a mild form of colorblindness. There are many forms, and to minimize their issues based solely on your experiences is a bit self-centered.

There is a scientific way of making colors more distinguishable to all the common forms of colorblindness, and that is to use colors along the yellow-blue axis, rather than the red-green axis, or "traffic lights" scheme, favored by most of society.
The Djego
Hellequin Inc.
#43 - 2013-06-24 12:41:40 UTC  |  Edited by: The Djego
Mark Androcius wrote:
imbaRabbit wrote:
I understand what you're trying to say, but do you have any clue how EvE code looks like?


Nope, 11.9 GB says enough though ( audio and video takes up only 972 MB ), 10.7 GB just in files in the main folder.

imbaRabbit wrote:
Anyway, I do hope they're not attacking their own database with silly requests such as 'text(#).getColor()'.


They'd be getting the color from a local file ( the xml file ).
I don't know if text comes from database or client side ( i think it's client side ), but in both cases they'd still need to grab the text codewise and they'd still need to change that code to reflect this change.


While I am not aware what kind of education you got in the IT business, lets assume you didn't work on bigger projects like client/server applications yet.

70% or more of the program is generally graphics, textures, 3d models
10% DB stuff
10% Shared components
10-15% code, since a single megabyte of compiled code translate into hundreds to thousands pages programming. Bin folder in the client is under 100mb, lib 2.8 MB etc. What you got is tons of .stuff files that contain graphics, textures and models, not tons of code.

For example a application(self build prototype/single distribution solution) I did for a strong arm board in combination with a touch screen using a linux like gui(programmed in c with the nano-x toolset) had including all the graphics less than 3 MB, with only like 180kb worth of code I actually implemented. This application still included over 400 pages of code in c, a self made font(because the standard ones where to big), lots of bitmap icons and masks to simulate a clicking feedback, full screen pictures for backgrounds in 480x320, start up logo for the company, nano-x logo because it is awesome, and the headers and shared stuff to make it run on the arm.

You don't save something like text colour in the database, that would be highly redundant wast of space. You don't pull it out of a xml file(because you have a client server architecture here and not a web browser interpretation), you add it directly in c(or what ever language is used in the front end for the client) with the function that directly applies a color to the text, since it is a common feature and the reason, you get different color even in chat if you start up with "/" for the old debug commands and devs got different chat colors. Changing a text color in a front end application is not a complex thing since you work directly with a programming language on the machine, instead of a work around if you only can interpret stuff with a browser.

Improve discharge rigging: https://forums.eveonline.com/default.aspx?g=posts&t=246166&find=unread
Malcanis
Vanishing Point.
The Initiative.
#44 - 2013-06-24 12:43:57 UTC
I can confirm that CCP do consider colour blindness when discussing UI features, but there's a huge backlog of existing UI features to work through.

"Just remember later that I warned against any change to jump ranges or fatigue. You earned whats coming."

Grath Telkin, 11.10.2016
Previous page123