I would define cruft as the current format, not the classic plain text format. The current JSONFM format causes chromostereopsis by mixing the blue/red/green format that it is currently using. Creating apioutput.css isnt a solution, its ignoring the actual issue. This reminds me of the Visual editor debacle where the devs decided to say screw you to the community. Depending on an individual's color spectrum, and rendering this current output is horrendously hard to read. Providing a non-colorcoded output is logical, and far easier than creating the fucked up barely readable output that is the current version.

On Sat, Dec 13, 2014 at 4:50 PM, Brad Jorsch (Anomie) <bjorsch@wikimedia.org> wrote:
On Fri, Dec 12, 2014 at 7:24 PM, Betacommand <Betacommand@gmail.com> wrote:
can we get something like jsontxt added where we can get the un-prettifed version?

On Sat, Dec 13, 2014 at 9:24 AM, Yuri Astrakhan <yastrakhan@wikimedia.org> wrote:
I guess we could make format=jsonfm and format=jsonfm2 or something like that, where jsonfm2 is non-color-coded.

No, we're not going to add cruft like "format=jsontxt" or "format=jsonfm2".


On Fri, Dec 12, 2014 at 6:45 PM, Chad <innocentkiller@gmail.com> wrote:
You can't. The pretty one is so humans can read it better.

Or maybe you can disable CSS.

This. Specifically, in [[Special:MyPage/apioutput.css]]:
.source-javascript * {
    color: black !important;
}
Or you could do something more targeted at GeSHi's output to recolor the various pieces to colors you like better.


--
Brad Jorsch (Anomie)
Software Engineer
Wikimedia Foundation

_______________________________________________
Mediawiki-api mailing list
Mediawiki-api@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-api