1. - Circle markers produced by TAsimage: They do not match was is produced on screen. The line width is too thick. Some other markers need to be tune a bit also but it is less important. pro - Title centering: Add possibility to center the axis titles with a global TStyle function. The first investigations show that the best way would probably be to change as TAxis the TStyle members fXaxis, fYaxis and fZaxis (they are now TAttAxis). pro - LibAfterImage: Synchronize asvisual.c. The change is small and would not even get compiled in with default configure flags. pro - Color palettes: Add to new predefined palette in TStyle “Gamma Ray” and “Grey Scale”. pro - Kerning not respected in PostScript: There is a fix form Oleksandr Grebenyuk it seems to work but a close look is required. Not sure to apply it yet. pro / dev Graphics Work Package Plan for the pro release 5.24 (2009/06) and dev release 5.23/2 (2009/02)

2. Graphics Work Package Plan for the pro release 5.24 (2009/06) and dev release 5.23/2 (2009/02) - Stressgraphics. Automatize the graphics visualisation the the reulst on various machines: http://couet.home.cern.ch/couet/root/stressGraphics.html Fix the bugs discovered running stressGraphics: like, for instance, in the test about exclusion graphs (coming from tutorials/graphs/exclusiongraph.C) which shows that the filled areas are not displayed the same way when saved with TASImage in batch mode. pro / dev - TParallelCoord: Give the possibility to change attributes of the various text displayed by the TParallelCoord. Basically the axis labels and the axis titles. As there is two type of text it night be not enough to just inherit from TAttText. Special setters might be required. pro (?) - TH2 painting: Scatter plot with negative content draw far too much points. The painting is very slow. pro (?) - PDF: Try to understand (and fix) why the PDF files are oriented "seascape" instead of landscape. pro (?)

3. Graphics Work Package Plan for the pro release 5.24 (2009/06) and dev release 5.23/2 (2009/02) - Access TTF fonts by name: TAttText::SetTextFont(const char *fontname) TTF::::SetTextFont(const char *fontname) already exists. Having this functionnality in TAttText would allow to access extra fonts in $ROOTSYS/fonts like: BlackChancery.ttf, verdana.ttf etc... or any ttf file users may want to put in $ROOTSYS/fonts. dev - graphviz: Need to implement a graphical tool allowing to display and interact with graphs. The graphs interpretation will be done thanks to the "graphviz" package: http://www.graphviz.org/ Graphs representations are needed in several places in ROOT. A generic tool using the power of the ROOT graphics and GUI would be really useful. dev (?)

4. HowTo’s: Migrated from the old web site. Converted into the Drupal style. Graphics Work Package Plans to move/create the web site to drupal & documentation (2009/01)

5. User’s Guide: Migrated from the old web site keeping the style Ilka had defined: Graphics Work Package Plans to move/create the web site to drupal & documentation (2009/01)

6. FAQs: A FAQ list is under construction. A better layout is needed, with the current on the FAQs are not clearly separated on the page: Graphics Work Package Plans to move/create the web site to drupal & documentation (2009/01)

7. THistpainter/TGraphPainter: All the plotting options are described in details here but it is not obvious for users to find them from TH1 or TGraph. No idea yet how to improve this …. Gallery: Collection of nice “ROOT view” or “ROOT applications” allowing to have a quick visual overview of all ROOT capabilities (not entering in the all the details of possibilities, this in THistPainter). Make some “session capture”: To show some “Typical ROOT session”. For instance a very simple one would be to show how to save a TCanvas in a “.C file” in order to demonstrate how an interactive modification on the canvas is reflected in the “.C code”. Will it be possible to execute these session directly from the web browser ? Graphics Work Package Plans to move/create the web site to drupal & documentation (2009/01)

8. “To Do” Pages ? I think it would be nice to have a list of the “To Do” items for each work package. Very often we have requests or ideas we have no time to implement quickly. Usually we reply to the user: “I will put it in in my To Do list…” It would be nice to have this To Do lists easily editable an visible by users to: Keep a better track of what should be done or what we think would be nice to have. Ease the building of the list of items we want to include in a release. Allow the users to see what we have in mind to provide and see if the question they have is not one of these items. Allow the users who are willing to help to pick some items if they want to implement it. Allow have a quick view of the topics we can offer to summer students. Etc … Graphics Work Package Plans to move/create the web site to drupal & documentation (2009/01)