Wikipedia:Graphics Lab/Resources/Research and Development

This page is designed to allow discussion of possible new standards for images or standards for creating them. Note that the completely finalized standards or methods will be displayed on Graphics Lab/Standards and Graphic Lab/Tutorials, respectively. All people are welcome to propose and discuss new ideas for standards here.

PS: don't hesitate to hide texts to make summarizations ! This keep the page clear and understandable.

A note on terminology and intent
The idea of this page is to create standards for classes of images on Wikipedia. By creating these standards and applying them to new and old images, we can obtain a professional look of uniformness and ease of understanding the information.

However, it must be known that none of these "standards" are immutably established, nor are they binding or mandatory on anyone who uploads an image to Wikipedia (or Commons). A standard should succeed by both vigorous promotion (IE. We convert all the images subject to it to the new standard), and its clear superiority to anything else out there.

Starting discussion for a new standard
If you have an idea for a new standard, an addition to a standard, or something worth discussing here, you are welcome to bring it up for discussion. New discussions with a clear explanation, an understandable intent, and (especially) images for explanation or as examples will generally go the farthest.

Anyone is welcome to comment on or suggest proposals, including creating example images. This is not restricted to those who have been around before, or who have done work for the graphics lab previously.

As with any discussion, keep in mind that it's not a matter of voting, but an attempt to find the best option by discussions. Similarly, any discussions should remain civil and cool, remain on topic, and not become rancorous or a competition between people instead of between ideas.

= Questions =


 * Please see WP:AG/FAQ to ask questions about the graphics lab, etc. If you want to propose a standard, but want to ask ahead of time, you can do so there, or just propose it below.

= Currently in discussion =

Amazing recent activity !
Summary:
 * Boom of activity : the English graphic lab have, apparently for no special reason (out of Segredo special disponibility and Chris active image hunting), a recent boom of his activity close to 3-4 request a day.
 * Take the lead : This recent boom and the size of the English wikipedians community let think that the English Graphic lab will, in end of 2008 or in 2009 as well, take the leadership in terms of production and research and development.
 * 2008 = follow the French standards : by the way, it was encourage to follow French team's standard for the moment, to avoid waste of energy on both side.

The several now active Graphic Labs are meeting difficulties which lead each graphic lab to set up graphic recommendations/standards. This section note how we should work for the moment to avoid wast of time and energy. :
 * 1) The English GLab is encourage to follow and copy the French choices and standards/recommandations, to avoid recommandations splits which may produce huge waste of time . ;
 * 2) a recommendation is composed by series of optimized rules (names' conventions, encouraged colors) and series of tools (list of icons to uses, links towards sources)
 * 3) feel free to create new recommandations/standard/legends, this is helpful ! but make them as proposal which may be merge into the current french recommandations (you can apply them for creation, but keep in mind that new global standard will come) ;
 * 4) when you think one proposal is optimized, propose it to fr:User talk:Sting for maps (icons, colors, etc), and fr:User talk:Walké or :fr:Séhmur for other conventions.
 * 5) This because these skilled graphists are currently listing all maps and graphic recommandations in the aim to produce by mid 2008 (?) some new Wikimedia graphic's (maps/diagrams) uniformized, optimized, and strongly encouraged recommandations/standards.
 * 6) Afterwhat, all maps (and many diagrams) on Wikipedia will have to be edit according to these recommandations. A global work probably on more than 5.000 images is planned for 2008-2009-2010 (Yes... huge project...), where all graphic Labs will have to collaborate.

The last thing, is that I encourage you to now (that you are really active ;] ) create your own Graphic Lab/Research and development for your own development and to overview the tutorials, the various news pages you create + have a graphist mediator always aware of new development on the French Graphic lab (fr). This again to avoid waste of time.

Your /Research and development may be first based on this post, and then expand by your teams.

Good Luck into your grow ! Your team still have lot to do, but I'am happy to see that the English GLab is now moving to a pretty good success and development. Muahaha ! Let's Roll !

Yug 06:31, 10 January 2008 (UTC) PS: for the next year I will just make about 5 edits a month. I will just come to post you some summaries such this one. Sorry to don't be able to help more.

Comments:

 * This looks like a very sensible proposal, and I support it wholeheartedly. Unfortunately, my French is not good, so I will only be of limited assistance in translating recommendations. --Slashme (talk) 11:09, 10 January 2008 (UTC)


 * We need a regular interpreter (English<->French G. Labs) :
 * We need a regular interpreter (English<->German G. Labs) :

Summary: we need users to keep a coordination between our Graphic Labs and graphic standards, this to avoid huge waste of time.

Proposed standard on the display of legislatures' compositions
Reading the above comments about standards gave me an idea of one area where we could easily standardize (And I didn't see this already dealt with on fR, but I don't know French): Representative distributions. Currently this is a mess, EG:

Does anyone think that it would be worth picking a standard of display of representation and slowly converting everything else to it (As well as, hopefully, having the new electoral images follow it)? Thanx, 68.39.174.238 (talk) 18:56, 11 January 2008 (UTC)


 * Summary : 1/ need of a Pie chart standard ; 2/ proposal of grey lines to show 50%, and super-majority ; 3/ biggest group on the lef ; 4/ a border line around the associated groups to show alliances.

Current Proposal
A proposition of recommendation, underlining the Country : Countryenglishname_YYYY's_ElectionName -languagecode.svg, i.e. : .svg. If you have a doubt for these names just check Wikipedia's article, i.e. Wikipedia use fluent names such as "French legislative election, 2007". But this should be put into basic english such as : France 2007's legislative election 1st-fr.svg (Taiwanese -> Taiwan ; Kenyanese ? Kenyan ? -> Kenya 2007's ...).
 * Here is a draft proposal, listing the mains parameters of this kind of charts, and giving my opinion about each of them.
 * Semi-circle and circle system : I don't really like semi-circle or circle. Why ? Because despite to be really clear, they have to show roughly two informations : the right number of deputy by color + the area of each color (in % of the circle) . And I think that this last points is difficult to edit on a SVG, difficult to check, and so may be falsified (i.e. a pro-republican may display the republican area bigger than is true %).
 * [[Image:Black x.svg|15px]] refused. Not convenient untill we don't have an easy way to make and check that each color area is conform to it's pourcentage.
 * One deputy/One colored point system: I like more this system. Because : 1/ editable by every SVG newbie, 2/ quickly checkable by everyone, 3/ easily expandable, 4/ the % can perfectly be remove to the Image:page.svg and in the article.
 * proposition supported : seems to me to be the best way to be easily makable, clear, and checkable.
 * Displaying the Assembly shape system : seem useless. That's more difficult to provide/draw, is different for every countries, and make then like that will ask us lot of work without comparative gain in the message.
 * [[Image:Black x.svg|15px]] refused.
 * 3D view VS 2D view (circle pie charts) : don't seems interesting. It look like one more difficulty adding to already existing difficulties link to 2D pie chart.
 * [[Image:Black x.svg|15px]] refused.
 * Colors ? : I prefer soft colors such display in the 1st and 4th images. An SVG displaying the list of the 12 (?) recommended soft colors should be create.
 * proposition valided : don't seems controversial. Stay to create an SVG listing the 12 (?) soft colors recommended, please wait the first attempt.
 * Include in the Image : country name or province name, years of vote ; total number of seats ; number of seat for each group/color ; % of each group (this is it really need here ?), exact day when the data was pick up such as "YYYY/MM/DD" (where to put this) . Do do not include (not forget) : groups' names (need on the image ? may be display on the legend using legend), explanations (should clearly be in the article)
 * proposition valided : seems to me the best optimization. To see clearly where put what, please wait the first attempt.
 * Exclude from the Image, include in the article : Legend explaining what means each color using the template legend : {{legend|#0000ff|Republican}} = {{legend|#0000ff|Republicans (127 seats; 43%)}}, with the number of seats and % of each groups.
 * proposition valided : seems to me the best optimization.
 * Naming convention : the name should contain all the following data : Country name, election name, year, language code (? not need if we agree to always produce free-of-text charts), and round number.
 * [[Image:Nuvola apps clock.png|16px]] proposition : seems to me the best optimization for international use -> validated, except if this name seems really ugly to native english speakers' ears (then -> French legislative election, 2007 1st-fr.svg, based on article's name.).
 * For standard creation, we have to keep in mind: that the image should be perfectly clear, able to say quickly and clearly the facts. In Wikipedia : the illustration will be accompanied by a legend, an article, etc, but the image will also be print by high school students, and so the image file need to bring the basis to be a good start point of a presentation. 1/ the filename provide the context   .svg , 2/ the image provide the data : year ; total number of seat ; seats by group ; % by group , 3/ yes, we expect from our "high school student" to be able to read file name and to remember the topic of his speech... 4/ but what provide the groups names ? I think we should also expect from our high school student to remember the image's legend and articles comments.
 * Yug 13:19, 12 January 2008 (UTC)

Comments
This current proposal finally encourage to avoid pie charts. Despite their good looking, they don't offer enough guarantees of accuracy to be raise to the level of a recommendation. I'm myself a little disapointed by this conclusion, but I had to make a choice between "Good looking" and "Easy to do, to check", I chosen the second one. If you know a way to color disk on Inkscape into pie charts by seting the % of each part, they please tell it. Yug. 17:55, 12 January 2008 (UTC)
 * Pie chart, or list of colored dot ?

Could I ask why some were arbitrarily marked "rejected" and how this is "90%" done? I think 3 people (Myself, you and User:Sagredo) have commented on this: far to few to be able to arbitrarily declare a standard and certainly not enough to "reject" proposals out of hand which obvious have some merit (They're being used in at least one articel). 68.39.174.238 (talk) 21:26, 12 January 2008 (UTC)
 * How to set up an optimized recommendation ?:
 * This text have been move to Wikipedia talk:Graphic Lab/Research and Development
 * Yug 09:34, 14 January 2008 (UTC)


 * I'm not (for obvious reasons) really involved with the means of consensus here, but I think that's a French system and not a universal one. The rough and ready blanket-primary-of-systems we have here seems to be working (Especially since this doesn't involve major wiki politics like pagemoving, etc.). Once a standard is adopted, it should be fairly easy for everyone (here) to follow it. 68.39.174.238 (talk) 16:27, 13 January 2008 (UTC)


 * 1) It's certainly time to start the page Editing Wikipedia:Graphic Lab/Research and Development and move this there. Perhaps put a note on the appropriate German and French pages, even if it's in English and on the images to improve page, everyone should be welcomed to make comments on the English page any language.  I think English will prove to be the most universal, but with any luck we'll get translators as well.  Perhaps we'll end up with a trilingual page.
 * 2) Slashme is a chemical engineer, and he has/knows about software which will generate all sorts of charts from raw data. Fvasconcellos may very well will know something as well.  I left notes on their talk pages.
 * 3) About all I can put in is the layman's point of view. And that just for the U. S.  I think the public is very used to circular pie charts for things like budgets.  Seating charts for things like legislatures.  I really don't have the technical knowlege to keep up with this.  I did study engineering, but that, too was a while back.       Sagredo &#8857;&#9791;&#9792;&#9793;&#9794;&#9795;&#9796; 23:53, 12 January 2008 (UTC)

I have had a look at the alternatives, and I strongly support the one-representative one-dot system. It gives more information at a glance than the pie chart: The pie chart shows you the balance of representation, but the dot-chart also shows you which parties only have one rep or two reps in sitting. The seating plan is cute, but I agree that it's not worth the added effort, and is inefficient in terms of pixels used per amount of information presented. --Slashme (talk) 06:52, 13 January 2008 (UTC)
 * Ok, I also made this choice because it's the most efficient. It stay to find a way to be nice and efficient in the same time : delete space between square ? use dot ? etc. Yug 15:09, 13 January 2008 (UTC)
 * NO. If you run all of the squares together, then you have to guess at the true number. With a separation, you can just multiply the rows by columns and add any extras. 68.39.174.238 (talk)


 * I like circles for this. Then you don't have to worry about the thickness of the lines in between the rows and columns.--Slashme (talk) 10:50, 16 January 2008 (UTC)

As for the soft colours, nice idea to keep a standard SVG for this purpose. --Slashme (talk) 06:52, 13 January 2008 (UTC)
 * Ok. Yug 15:09, 13 January 2008 (UTC)
 * I suggest using the locally (EG. Within the legislature's jurisdiction) understood symbols.

Talks about Slashme's script solution

 * See also : Slashme's current script and the associated talk page

How about giving the option of making it an HTML table (wikitable?) or an SVG at the user's discretion? It could in principle look exactly the same, and has some technical advantages when you have a grid, and might be easier to fix for people without graphic design experience or software when a by-election changes one seat. --Slashme (talk) 06:52, 13 January 2008 (UTC)

I'll look into methods of automatically generating the SVG of the table. I'm sure it can't be too hard, in fact it might be possible to do by template! --Slashme (talk) 06:52, 13 January 2008 (UTC)
 * Interesting idea, we are here to test new ways... so go ahead if you think that can produce a gain. Yug 15:09, 13 January 2008 (UTC)

Summary: 1/ 8.39.174.238's proposat to organize the page "research and development" between "Standard" VS "New" ; 2/ 8.39.174.238's proposal to use the symbolic colors use by the parties themselves into our output SVG.

I'm busy writing my script to generate an SVG given a list of parties and their representation levels. I'm going to implement it as a cgi script and make the code available for improvement. As soon as I have a working copy, I will give the web address and post examples. Doing it in the evenings makes progress a bit slow, but it will probably be ready by Monday. --Slashme (talk) 10:38, 16 January 2008 (UTC)

I've now got a python script which draws a nice-looking array of squares, each "party" being represented by its own (random at the moment) colour. I'm still going to: I have karate and Go this evening, but sometime this weekend I should have a working script for you all to test.--Slashme (talk) 10:06, 17 January 2008 (UTC)
 * Fix the scaling (at the moment it just draws the squares 50x50 with 10 space in between and doesn't worry about page size, so I'll make those lengths multiples of the page size, easy to do)
 * Set a standard list of colours: Where do I get the list? Someone please mail me or drop a note on my talk page in case I miss any responses.
 * Make it draw a legend at the bottom (will be easy)
 * Give the option of circles as well as rectangles so that we can decide what looks better (really easy).
 * Implement it as a CGI script on my freeshell account (not hard to do)


 * Thus far I've discovered Political colour, Party name with colour and Category:Political parties colours templates. 68.39.174.238 (talk) 15:55, 17 January 2008 (UTC)

Well, the Stellenbosch Go Club only starts meeting next week, so I got the script into a state where it writes OK pictures, but I'm not quite done yet: Please see User_talk:Slashme/parliament.py. You can check out the source code at User:Slashme/parliament.py. Sorry, no comments yet!!
 * Need to make circles as well
 * Inkscape seems to mess up the file when I save as "plain svg"
 * Need to convert to CGI and host on freeshell.org
 * Need to check out the standard colours

Here are some example images:


 * but only the step will work in general, because the slice depends on having a complete rectangle, which becomes difficult when you have (for example) 239 seats in your legislature. It seems pretty easy to code, except for collision avoidance, which I'll leave up to the user, so I'll do it some time in the next two weeks. --Slashme (talk) 14:06, 21 January 2008 (UTC)


 * Why does the "slice" say that 30 is 1/3 of 100?! I do see what you're saying though, about the two methods, only why is the line divide the seats in fractions? 68.39.174.238 (talk) 18:08, 21 January 2008 (UTC)


 * Well, the "slice" doesn't cut at 30, it cuts 1/3 of the way through the 31-40 column, giving 33 1/3. As for dividing the seats into fractions, how else would you represent 33 1/3? --Slashme (talk) 05:15, 22 January 2008 (UTC)


 * I've had another think about this. For a majority vote threshold you need a certain number of votes.  For example in a legislature with 100 seats, you need 67 votes to pass a 2/3 majority motion.  I won't be coding this weekend due to having a busy social calendar, but when I get around to it, I intend to allow specification of:
 * Fractions (e.g. "2/3" or "1/2") or
 * Number of seats (e.g. "67" or "50")
 * I don't intend allowing percentages, because then too many people will type "66%" when they mean "67%".


 * Comments please? --Slashme (talk) 08:38, 23 January 2008 (UTC)


 * I would prefer fractions, since that's how they are usually constitutionally specified, EG. "Two-thirds of both Houses concurring", not "67 here and 290 there", however allowing specific numbers may be useful for showing, EG. "Two-thirds were needed (One line), but only 117 voted for it". Also, do you think we should have specific colors for the lines for different purposes (EG. One color for a simple majority, another color set to mean "Majority to change the constitution", "majority to override vetoes", "Majority to impeach the executive", etc)? 68.39.174.238 (talk) 19:44, 23 January 2008 (UTC)


 * OK, I think you have a point here; I'll stick to fractions and numbers for flexibility, though. I don't think different colours of lines are really necessary:  This is not likely to become a standard, as there are so many possible variations on the theme.  What I suggest is that I allow the user to specify a list of fractions and numbers, and I'll put a line in at each fraction or number given, with the label of the line being the fraction or number as given.  If the user asks for too many lines, the diagram will look stupid, and they'll hopefully notice that.  If the user wants different colours, that's really easy to do in inkscape (or even a text editor) afterwards.  I suggest that I round all fractions upwards to the nearest integer, as that's the most logical sense to be made from the diagram. --Slashme (talk) 05:54, 24 January 2008 (UTC)


 * Just remember to round up. 68.39.174.238 (talk) 17:54, 26 January 2008 (UTC)


 * Also, why circles?

Just an alternative that was suggested above.--Slashme (talk) 06:49, 18 January 2008 (UTC)


 * Anyway, thanx; this'll be the best thing ever when refined: we can create SVGs by the THOUSANDS... for EVERY LEGISLATURE... EVER. :DDDDD 68.39.174.238 (talk) 00:40, 18 January 2008 (UTC)

Thanks for the support! much appreciated. Everyone, please put bug reports and feature requests on User_talk:Slashme/parliament.py. --Slashme (talk) 06:49, 18 January 2008 (UTC)

Coalitions
A new idea: For legislatures where parties form superparties or blocks (Think Taiwan & their two coalitions), what would we do? I suggest having the parties in a block have their representatives squares bordered by the color of their coalition (EG. In the current Alaska Senate, we would have blue squares (Democrats), but the squares borders would be purple (Coalition). The uninvolved Republicans could be just red squares. 68.39.174.238 (talk) 21:18, 13 January 2008 (UTC)


 * This is a good suggestion. I will add it to the "wishlist" section of User_talk:Slashme/parliament.py. --Slashme (talk) 12:49, 18 January 2008 (UTC)

Majortarian indications
Summary: Suggestion to add lines to indicated various majorities: 1/3 1/2 and 2/3 proposed. It was noted that these would have to be specified by the image creator as different legislatures have different working majorities.

Special sections
Another idea, which may or may not be useful: What about indicating separately special seats? Many countries have legislatures with a certain %age of seats allocated specifically for certain groups, EG. the new Montenegro Assembly has 5 seats for Albanians. Is there an easy and logical way to indicate these? Should we care (etc.)? 68.39.174.238 (talk) 04:17, 27 January 2008 (UTC)


 * Very good point! In general, I assume there could be some parties which have seats in the reserved and non-reserved sections.  How about allowing numbers in the form of "aRb" (e.g. 12R3) meaning that there are 12 seats of which three are reserved, and then all reserved seats are shown as circles in the party colour instead of squares?  I will only be working on the script again after 14 Feb, as I have to prepare a talk on my M.Sc. work, so please discuss other suggestions in the meantime. --Slashme (talk) 06:45, 28 January 2008 (UTC)


 * It depends: in some cases, the seats are competed for by totally different parties (EG. The ethnic ones), in others (EG. The ones requiring a certain % or number to be women), that may be fought over by all the parties. The last one though, makes be think of states in a federal affair: We would be drawing hundreds of lines to show the individuals state representation (EG. MA is all blue, but NJ has 7 and 8)! 68.39.174.238 (talk) 19:19, 28 January 2008 (UTC)


 * Well, I guess we could leave the details to the user, maybe having different classes of seat be represented by different symbols. For example, the user could type:

Barking Mad Party:35,3(Women),2(Youth):#FFAAAA;Monster Raving Loony Party:0,3(Sith),4(Women):#d768c5;Very Silly Party:11,3(Jedi):#AAAAFF and get a diagram with the Barking Mad Party having 35 pink squares, 3 pink circles and 2 mauve triangles, the Monster Raving Loony Party with 3 mauve pentagons and 4 mauve circles and the Very Silly Party with 11 powder-blue squares and 3 powder-blue crosses. The key would then show the parties each with a square in its colour, and also have a list with the symbols just given as transparent shapes with black outlines. If the list becomes unwieldy due to its length, I might have to code it as a few text boxes for each party with a button to add a party. This would be much more user-friendly. --Slashme (talk) 09:19, 29 January 2008 (UTC)


 * I like the idea of a new UI (If possible). Feeding it a long string is probably the easiest way to parse, but it will get really unwieldy with things like Papua New Guinea. 68.39.174.238 (talk) 04:31, 30 January 2008 (UTC)

Script now hosted on freeshell.org
I have implemented:
 * A title for the diagram
 * Giving numbers of seats and percentages for the different parties in the key
 * User selection of colours for parties

Go check out the script on my freeshell account, and please put bug reports and feature requests on User_talk:Slashme/parliament.py, and feel free to implement bug fixes and new features on User:Slashme/parliament.py, and drop me a line so that I can upload them. --Slashme (talk) 14:07, 20 January 2008 (UTC)

I still have to do:
 * Majority lines
 * Try what it looks like with circles instead of rectangles
 * Put the date (either user-submitted or current date) in title

I still want to do:
 * Use borders of blocks to indicate coalitions.
 * Make the key in two columns if necessary
 * Make the instructions and error messages at least borderline understandable.


 * One (Offtopic) question: Why is the image there claim it was uploaded by "Special:Contributions" ? 68.39.174.238 (talk) 15:42, 20 January 2008 (UTC) PS. I'm off to test it now.


 * As you correctly pointed out, the script was not working all of last night (South Africa night, that is ;-), but I fixed it this morning. As for the "Special:Contributions" thing, are you talking about Image:TestParlSVG3.svg? Every user has a "Special:Contributions" page, maybe you're seeing a link to mine? --Slashme (talk) 06:35, 21 January 2008 (UTC)


 * No, it claimed that the uploader was "Special:Contributions", however it appears that that was a server error and has been fixed. 68.39.174.238 (talk) 21:20, 22 January 2008 (UTC)


 * Ah, ok. --Slashme (talk) 08:30, 23 January 2008 (UTC)

Script unavailable
I see I have to upgrade my membership at freeshell to get continued use of the cgi facilities. This isn't very expensive, but I will only get around to it in a few days. Until then, the script is unavailable. Sorry!! --Slashme (talk) 05:28, 20 February 2008 (UTC)


 * OK, now the script is again available: See User:Slashme. There are now two scripts, one for semicircular diagrams, one for rectangles. --Slashme (talk) 09:04, 29 May 2010 (UTC)

Other solution : Website making SVG pie charts !

 *  Yug 18:25, 12 January 2008 (UTC)
 * I need an english speaker, my english is not enough to fully understand things like : Creating SVG Pie Charts through XSLT via a Web Service. I have to stop here my involvement since my coding and english abilities are clearly not enough. You can have a look at google query Pie+Chart+SVG, here is probably a website providing such creation. If you find one, even better : if it is under free licence, then we will be able to ask on http://bugzilla.wikimedia.org to create for us a page to create [semi-]circle pie charts according to our standards !!! So : your eyes are really welcome to find a such website !! Yug 18:55, 12 January 2008 (UTC)
 * I finally made a request to the gods... we will see what they say. —Preceding unsigned comment added by 210.203.61.15 (talk) 19:22, 12 January 2008 (UTC)


 * Create A Graph. Free online graph creation tool at the NCES website. Bar charts, Line charts, Area charts, Pie charts, and XY graphs. Choice of PDF, PNG, JPG, EMF, EPS, and SVG output.


 * For more charting tools, see the resources section at commons:Category:Charts. --Timeshifter (talk) 17:45, 20 January 2008 (UTC)
 * Holiday 2015 present, a pie-chart creating with Extension:Graph using Vega version 2 specification:

{ "version": 2, "name": "Vega Visualization", "height": 50, "width": 50, "legends": [{"title": "Fruits","fill": "color"}], "padding": "auto", "marks": [ {     "properties": { "enter": { "innerRadius": {"value": 0}, "stroke": {"value": "white"}, "startAngle": {"field": "layout_start"}, "x": {"mult": 0.5,"group": "width"}, "outerRadius": {"value": 50}, "endAngle": {"field": "layout_end"}, "fill": {"field": "x","scale": "color"}, "y": {"mult": 0.5,"group": "height"} }     },      "from": { "data": "table", "transform": [{"field": "y","type": "pie"}] },     "type": "arc" } ],  "data": [ {     "name": "table", "values": [ {"x": "peaches","y": 100}, {"x": "plums","y": 32}, {"x": "blueberries","y": 180}, {"x": "strawberries","y": 46}, {"x": "bananas","y": 21} ]   }  ],  "scales": [ {     "name": "color", "range": [ "rgb(166,206,227)", "rgb( 31,120,180)", "rgb(178,223,138)", "rgb( 51,160, 44)", "rgb(251,154,153)" ],     "domain": {"data": "table","field": "x"}, "type": "ordinal" } ] } Happy baking pies! Ad Huikeshoven (talk) 21:26, 23 December 2015 (UTC)

Archivery
Not really a graphics standard, but about archiving this page. Collapsing sections and summarizing them (When useful or finished) is OK, but after a while we'll need to actually archive something. As such, I propose that 3 or 4 days after a standard is finalized (Moved to the standards page), all the discussion relating to it (Unless it's turned into something else) be sent to an /Archive. 68.39.174.238 (talk) 16:08, 19 January 2008 (UTC)