From: Thomas C. <tca...@gm...> - 2015-04-26 17:52:22
|
I am in favor of doing in in PR comments so we can to line comments. On Sun, Apr 26, 2015 at 3:47 AM Nicolas P. Rougier <Nic...@in...> wrote: > > Great ! Thanks for setting this up. One comment, it would be great to have > a README.rst in the directory to have abstract of all MEPS at once in > github (I can make a PR). > > > I've started working on MEP28 ( > https://github.com/rougier/matplotlib/blob/MEP28/doc/devel/MEP/MEP28.rst). > I intend to make a PR once it is a bit more polished or should I make a PR > right now to initiate the discussion on the PR ? (It is not clear to me if > the preferred medium for discussion is the mailing list or the PR comments). > > > Nicolas > > > On 25 Apr 2015, at 23:04, Thomas Caswell <tca...@gm...> wrote: > > > > The MEP tree has been moved into the main repo > https://github.com/matplotlib/matplotlib/tree/master/doc/devel/MEP > > > > I am pretty excited about this feature. > > > > I don't remember if this got mentioned upthread, but this ties in with > https://github.com/matplotlib/matplotlib/issues/1109 as a nice way to set > up all of the constraints. > > > > Tom > > > > On Thu, Mar 19, 2015 at 1:10 PM Nicolas P. Rougier < > Nic...@in...> wrote: > > Ok. I'll wait for the MEP directory to start writing a proposal. > > Here is a flavor of what I think could be done (to be seen using a fixed > width font): > > > > > > "AB": > > ┌────────┐┌────────┐ > > │ A ││ B │ > > │ ││ │ > > │ ││ │ > > └────────┘└────────┘ > > > > "ABB": > > ┌──────┐┌──────────┐ > > │ A ││ B │ > > │ ││ │ > > │ ││ │ > > └──────┘└──────────┘ > > > > "ABD" > > "CCD": > > ┌───────┐┌───────┐┌───────┐ > > │ A ││ B ││ D │ > > │ ││ ││ │ > > │ ││ ││ │ > > └───────┘└───────┘│ │ > > ┌────────────────┐│ │ > > │ C ││ │ > > │ ││ │ > > └────────────────┘└───────┘ > > > > "AaBb": > > ┌───────┐┌─┐┌───────┐┌─┐ > > │ A ││ ││ B ││ │ > > │ ││ ││ ││ │ > > │ ││ ││ ││ │ > > └───────┘└─┘└───────┘└─┘ > > > > " b " > > "aABCc": > > ┌───────┐ > > └───────┘ > > ┌─┐┌───────┐┌───────┐┌───────┐┌─┐ > > │ ││ A ││ B ││ C ││ │ > > │ ││ ││ ││ ││ │ > > │ ││ ││ ││ ││ │ > > └─┘└───────┘└───────┘└───────┘└─┘ > > > > > > > > > >> On 19 Mar 2015, at 15:34, Benjamin Root <ben...@ou...> wrote: > >> > >> two problems with that: 1) that really doesn't make me want to use this > approach, especially since I wouldn't know what ratios I would want in the > first place. 2) it can't tell if I want a horizontal or vertical colorbar, > whereas the lower-case notation could have some logic to auto-detect the > user's intent (e.g., all lower-case letters in the last row indicates > horizontal bars). It would also allow us to return the plotting axes > separate from the colorbar axes, which is how axes_grid1 does it, and it is > very nice that way. > >> > >> On Thu, Mar 19, 2015 at 6:31 AM, Nicolas P. Rougier < > Nic...@in...> wrote: > >> > >> I think you could specify colorbars using: ["AAAAAAAAAB"] > >> (B is a vertical colorbar, 1/10 of total width) > >> > >> Nicolas > >> > >> > >> > >> > On 18 Mar 2015, at 18:52, Eric Firing <ef...@ha...> wrote: > >> > > >> > On 2015/03/18 7:42 AM, Benjamin Root wrote: > >> >> A thought... could this perhaps be extended somehow to specify > colorbars > >> >> in the layout? > >> > > >> > A lower-case letter could indicate a colorbar-size Axes: > >> > > >> > layout = ["ABc", > >> > "DE ", > >> > "ff "] > >> > > >> > would put a vertical think axes to the right of B, and a double-wide > >> > hoizontal one below D and E. > >> > > >> > All of this seems like an alternative API for gridspec and axes_grid1. > >> > > >> > I am concerned about ending up with too many ways to do things, but > with > >> > subtle differences. > >> > > >> > How much control over spacing and sizing would be provided by kwargs > or > >> > other adjustment mechanisms? How would this relate to subplot_params? > >> > > >> > Eric > >> > > >> > > >> > > >> > > ------------------------------------------------------------------------------ > >> > Dive into the World of Parallel Programming The Go Parallel Website, > sponsored > >> > by Intel and developed in partnership with Slashdot Media, is your > hub for all > >> > things parallel software development, from weekly thought leadership > blogs to > >> > news, videos, case studies, tutorials and more. Take a look and join > the > >> > conversation now. http://goparallel.sourceforge.net/ > >> > _______________________________________________ > >> > Matplotlib-devel mailing list > >> > Mat...@li... > >> > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > >> > >> > >> > ------------------------------------------------------------------------------ > >> Dive into the World of Parallel Programming The Go Parallel Website, > sponsored > >> by Intel and developed in partnership with Slashdot Media, is your hub > for all > >> things parallel software development, from weekly thought leadership > blogs to > >> news, videos, case studies, tutorials and more. Take a look and join the > >> conversation now. http://goparallel.sourceforge.net/ > >> _______________________________________________ > >> Matplotlib-devel mailing list > >> Mat...@li... > >> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > >> > > > > > ------------------------------------------------------------------------------ > > Dive into the World of Parallel Programming The Go Parallel Website, > sponsored > > by Intel and developed in partnership with Slashdot Media, is your hub > for all > > things parallel software development, from weekly thought leadership > blogs to > > news, videos, case studies, tutorials and more. Take a look and join the > > conversation now. > http://goparallel.sourceforge.net/_______________________________________________ > > Matplotlib-devel mailing list > > Mat...@li... > > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > > |