On Sun, Mar 1, 2009 at 8:17 AM, sam tygier <samtyg...@yahoo.co.uk> wrote:
> Eric Firing wrote:
> > Sandro Tosi wrote:
> >> Hi Sam,
> >>
> >> On Wed, Feb 25, 2009 at 09:35, sam tygier <samtyg...@yahoo.co.uk>
> wrote:
> >>> I think this topic has come up before, but i don't think anything has
> >>> resulted from it.
> >>>
> > Correct, because the capability would require a *lot* of work to
> > implement,
>
> Would i be right in assuming that it would take roughly the same amount of
> effort as writing a new backend? ie for each motplotlib action it would need
> a function to store that action and a function to call that action again.
>
> > and most of us don't see a compelling need; we believe that a
> > better practice is to structure one's work so that plotting is separated
> > from data (result) generation in any cases where the latter is highly
> > time-consuming.
>
> It might not be essential, but it would offer an additional work flow, that
> a few people seem to like.
>
> I think it would be especially useful when it comes to putting plots into
> papers. I often find that i want to tweak something like the font size or
> labels. having a modifiable plot format seems the easiest way to achieve
> that. maybe the could even be some integration into latex so that if you
> were to resize your plot in your paper, it would be re-rendered with the
> fonts adjusted.
Other than the automatic regeneration from latex, what you want sounds like
what we already have: small python scripts.
In general, I'm completely amazed by how many people want to develop a new
markup/script language to wrap what is already a simple and expressive
language, both for plots and (at least around here) analyses. If there are
some spots that require too many lines of code to accomplish something
really simple, then maybe we need to API additions. But in general, I think
we have a format for specifying how to make a plot: python. Now, if we're
taking the output from some monstrous application or set of scripts, it
might be nice to get the commands that made the plot, like MayaVi 2 and its
ability to record. However, at the end of the day what MayaVi creates is a
python script, and I think that's more useful than any general markup since
I can look at that file and figure out what's going on without learning
anything new.
Now, a matplotlib backend that writes out python code could be useful and
cool, though it would only matter for the large applications/scripts. In
fact, it's at the application level that such functionality would probably
belong.
My 0.02 anyways.
Ryan
--
Ryan May
Graduate Research Assistant
School of Meteorology
University of Oklahoma
Sent from: Norman Oklahoma United States.
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
