You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(33) |
Dec
(20) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(7) |
Feb
(44) |
Mar
(51) |
Apr
(43) |
May
(43) |
Jun
(36) |
Jul
(61) |
Aug
(44) |
Sep
(25) |
Oct
(82) |
Nov
(97) |
Dec
(47) |
| 2005 |
Jan
(77) |
Feb
(143) |
Mar
(42) |
Apr
(31) |
May
(93) |
Jun
(93) |
Jul
(35) |
Aug
(78) |
Sep
(56) |
Oct
(44) |
Nov
(72) |
Dec
(75) |
| 2006 |
Jan
(116) |
Feb
(99) |
Mar
(181) |
Apr
(171) |
May
(112) |
Jun
(86) |
Jul
(91) |
Aug
(111) |
Sep
(77) |
Oct
(72) |
Nov
(57) |
Dec
(51) |
| 2007 |
Jan
(64) |
Feb
(116) |
Mar
(70) |
Apr
(74) |
May
(53) |
Jun
(40) |
Jul
(519) |
Aug
(151) |
Sep
(132) |
Oct
(74) |
Nov
(282) |
Dec
(190) |
| 2008 |
Jan
(141) |
Feb
(67) |
Mar
(69) |
Apr
(96) |
May
(227) |
Jun
(404) |
Jul
(399) |
Aug
(96) |
Sep
(120) |
Oct
(205) |
Nov
(126) |
Dec
(261) |
| 2009 |
Jan
(136) |
Feb
(136) |
Mar
(119) |
Apr
(124) |
May
(155) |
Jun
(98) |
Jul
(136) |
Aug
(292) |
Sep
(174) |
Oct
(126) |
Nov
(126) |
Dec
(79) |
| 2010 |
Jan
(109) |
Feb
(83) |
Mar
(139) |
Apr
(91) |
May
(79) |
Jun
(164) |
Jul
(184) |
Aug
(146) |
Sep
(163) |
Oct
(128) |
Nov
(70) |
Dec
(73) |
| 2011 |
Jan
(235) |
Feb
(165) |
Mar
(147) |
Apr
(86) |
May
(74) |
Jun
(118) |
Jul
(65) |
Aug
(75) |
Sep
(162) |
Oct
(94) |
Nov
(48) |
Dec
(44) |
| 2012 |
Jan
(49) |
Feb
(40) |
Mar
(88) |
Apr
(35) |
May
(52) |
Jun
(69) |
Jul
(90) |
Aug
(123) |
Sep
(112) |
Oct
(120) |
Nov
(105) |
Dec
(116) |
| 2013 |
Jan
(76) |
Feb
(26) |
Mar
(78) |
Apr
(43) |
May
(61) |
Jun
(53) |
Jul
(147) |
Aug
(85) |
Sep
(83) |
Oct
(122) |
Nov
(18) |
Dec
(27) |
| 2014 |
Jan
(58) |
Feb
(25) |
Mar
(49) |
Apr
(17) |
May
(29) |
Jun
(39) |
Jul
(53) |
Aug
(52) |
Sep
(35) |
Oct
(47) |
Nov
(110) |
Dec
(27) |
| 2015 |
Jan
(50) |
Feb
(93) |
Mar
(96) |
Apr
(30) |
May
(55) |
Jun
(83) |
Jul
(44) |
Aug
(8) |
Sep
(5) |
Oct
|
Nov
(1) |
Dec
(1) |
| 2016 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
(3) |
Sep
(1) |
Oct
(3) |
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
(5) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
(7) |
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
1
(2) |
2
(3) |
3
(7) |
4
(8) |
5
(10) |
6
(4) |
7
|
|
8
|
9
(13) |
10
(1) |
11
(10) |
12
(4) |
13
|
14
|
|
15
|
16
(1) |
17
|
18
(3) |
19
(7) |
20
|
21
(4) |
|
22
|
23
(14) |
24
(5) |
25
(3) |
26
(3) |
27
(8) |
28
(1) |
|
29
(3) |
30
(2) |
31
(3) |
|
|
|
|
|
From: Andrew S. <str...@as...> - 2009-03-12 15:14:08
|
Paul Kienzle wrote: > On Mar 12, 2009, at 9:49 AM, Michael Droettboom wrote: > > >> We've done some experiments with Enthought Traits at various times to >> address this issue. There were always various obstacles to making it >> work, but it may be worth another look. Traits has its nice auto- >> built >> property editors (that may address your request), but it would also >> address one of my long-standing niggles that properties of graphs are >> often checked far too late and the error messages presented to the >> user >> are very obscured because of it. >> >> Of course, all that is a major undertaking -- basically rewriting all >> the getters and setters on the artist classes to use traits -- but I >> could see it having quite the payoff in the end. >> >> > > I'm not sure if traits can do it. > Why not? Everything you describe below screams "traits" to me. > I would like to see CSS-like properties, so that when I change the > font size on the graph, the title, which is size +2, and the legend > which is size -1 also get updated. I can imagine changing the font > for an axes, for a figure or for all figures. The latter should be > stored in a resource file so it doesn't have to be done every > session. Properties which are not set should look up their values > elsewhere; if the property of some object has been specialized, then > it should not change when the figure properties are set. Properties > for printed figures may be different from properties of figures on > the screen, e.g., because the printer is monochrome. > > Eventually I would like interactive editing of properties by point > and click. Particularly for plotted data the question will be > whether the change applies to the data point only, to its line, or to > all lines on the graph, to all graphs on the figure, or to all > figures, depending on the property. Doing this without cluttering > the UI will be a challenge. > |
|
From: Paul K. <pau...@ni...> - 2009-03-12 14:52:59
|
On Mar 12, 2009, at 9:49 AM, Michael Droettboom wrote: > We've done some experiments with Enthought Traits at various times to > address this issue. There were always various obstacles to making it > work, but it may be worth another look. Traits has its nice auto- > built > property editors (that may address your request), but it would also > address one of my long-standing niggles that properties of graphs are > often checked far too late and the error messages presented to the > user > are very obscured because of it. > > Of course, all that is a major undertaking -- basically rewriting all > the getters and setters on the artist classes to use traits -- but I > could see it having quite the payoff in the end. > I'm not sure if traits can do it. I would like to see CSS-like properties, so that when I change the font size on the graph, the title, which is size +2, and the legend which is size -1 also get updated. I can imagine changing the font for an axes, for a figure or for all figures. The latter should be stored in a resource file so it doesn't have to be done every session. Properties which are not set should look up their values elsewhere; if the property of some object has been specialized, then it should not change when the figure properties are set. Properties for printed figures may be different from properties of figures on the screen, e.g., because the printer is monochrome. Eventually I would like interactive editing of properties by point and click. Particularly for plotted data the question will be whether the change applies to the data point only, to its line, or to all lines on the graph, to all graphs on the figure, or to all figures, depending on the property. Doing this without cluttering the UI will be a challenge. - Paul |
|
From: Michael D. <md...@st...> - 2009-03-12 13:49:35
|
We've done some experiments with Enthought Traits at various times to address this issue. There were always various obstacles to making it work, but it may be worth another look. Traits has its nice auto-built property editors (that may address your request), but it would also address one of my long-standing niggles that properties of graphs are often checked far too late and the error messages presented to the user are very obscured because of it. Of course, all that is a major undertaking -- basically rewriting all the getters and setters on the artist classes to use traits -- but I could see it having quite the payoff in the end. Mike João Luís Silva wrote: > Paul Kienzle wrote: > >> Hi, >> >> What's the status of interactive property editors for mpl graphs? >> >> I would like something that would allow me to change properties such >> as the size and position of the graph, grids, scales, ranges, colors, >> symbols, line styles, fonts, etc., and add annotations. Some of this >> already exists, but allowing users to enter specific values will need >> an underlying widget toolkit. >> >> Does anybody have anything that I can build on for wx? >> >> > > I though about making such a program but concluded it would be a major > undertaking. I considered using GTK because that's what I use, but > otherwise any toolkit will do. I still have some major unresolved design > issues to implement such an application: > > - How would the state of the editor be saved? In a new file type (in > json for example)? Is there any standard format for this? If it was > feasible I'd like to import and export small python scripts, but the > import capabilities seem unlikely. > > - Mpl is very flexible (just look at the gallery). Would the editor be > limited to a subset of the capabilities or the objective would be to > take mpl to the limit? Including subplots? and heterogeneous graphics? > The interface could get very complex very quickly indeed. > > - I seem to recall an open source graphics application along these > lines, but can't remember its name (maybe SciGraphica). > > If someone is working on such a thing, or if you want to make one I > could tinker a bit, but I really don't have enough time to start a major > application. BTW I'm not a mpl developer, just a satisfied user :) > > Regards, > João Silva > > > ------------------------------------------------------------------------------ > Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are > powering Web 2.0 with engaging, cross-platform capabilities. Quickly and > easily build your RIAs with Flex Builder, the Eclipse(TM)based development > software that enables intelligent coding and step-through debugging. > Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com > _______________________________________________ > Matplotlib-devel mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > -- Michael Droettboom Science Software Branch Operations and Engineering Division Space Telescope Science Institute Operated by AURA for NASA |
|
From: João L. S. <js...@fc...> - 2009-03-12 13:39:13
|
Paul Kienzle wrote: > Hi, > > What's the status of interactive property editors for mpl graphs? > > I would like something that would allow me to change properties such > as the size and position of the graph, grids, scales, ranges, colors, > symbols, line styles, fonts, etc., and add annotations. Some of this > already exists, but allowing users to enter specific values will need > an underlying widget toolkit. > > Does anybody have anything that I can build on for wx? > I though about making such a program but concluded it would be a major undertaking. I considered using GTK because that's what I use, but otherwise any toolkit will do. I still have some major unresolved design issues to implement such an application: - How would the state of the editor be saved? In a new file type (in json for example)? Is there any standard format for this? If it was feasible I'd like to import and export small python scripts, but the import capabilities seem unlikely. - Mpl is very flexible (just look at the gallery). Would the editor be limited to a subset of the capabilities or the objective would be to take mpl to the limit? Including subplots? and heterogeneous graphics? The interface could get very complex very quickly indeed. - I seem to recall an open source graphics application along these lines, but can't remember its name (maybe SciGraphica). If someone is working on such a thing, or if you want to make one I could tinker a bit, but I really don't have enough time to start a major application. BTW I'm not a mpl developer, just a satisfied user :) Regards, João Silva |