On 12/13/06, Paul McNett <[EMAIL PROTECTED]> wrote: > Ed Leafe wrote: > > On Dec 13, 2006, at 1:29 AM, Nate Lowrie wrote: > > > >> I think that matplotlib is our winner by far. > > > > Out of those you named matplotlib is the only one I've ever seen > > mentioned, so it's probably the best bet. > > I agree. > > > >> Should I put these in the uiwx folder or another graphs folder? > >> Implementation of specific backends into dabo objects will probably be > >> GUI specific, so wx might be a good idea. > > > > Let's think this through first. If there are some features that may > > be called from non-GUI areas, it might best be placed in dabo/lib. > > There can be a GUI-specific implementation that uses the code in dabo/ > > lib. That's what we've done with properties and events. > > > > If it is GUI-only, and it supports other toolkits such as Tkinter, > > it should go in dabo/ui, with another class in dabo/ui/uiwx that is a > > wxPython-specific implementation. This way if anyone ever takes on > > development of uitk or uiqt, there is a common base of code. > > I agree on thinking it through, but don't let it stop you from > contributing stuff we can look at. IOW, if it seems to make sense to put > it in uiwx for now, do it. We can refactor it as we go into dabo.ui, > dabo.lib, etc. We just started the 0.8 development branch, so there's > probably a decent amount of time before the location needs to stabilize. >
Oh I am not. I figured that I would code and upload as normal and if the location or name didn't fit we'd change it. I like the plan of refactoring it as we go. I've been looking at the documentation and have noticed some things: All graphs are held in a Figure. The Figure can support a number of Axes objects, which are the main workhorses for the plotting. This model allows for a potentially infinite number of various plots to occur in the same Figure. That said, these Figures and Axes are managed separately from any backend interface to a GUI package. Also, each different type of graph (bar, scatter, pie, etc.) stems from the Axes class and the Figure doesn't care what type of graph it is. So, we should be able to create a graph widget set that is UI agnostic, then have specific widget implementations for the FigureCanvas backends. In the implementation that is UI agnostic, we should be able to create a single graph object class that contains all of the control functionality we need. Then, any additional widgets we might want to add like Line Plot or Pie Chart widgets can subclass the main graph object and just configure the Axes properly to display that type of chart. I am hoping that we can get all of the matplotlib functionality into a small subset of code and that switching backends will be transparent and seamless.. > -- > pkm ~ http://paulmcnett.com > > > _______________________________________________ > Post Messages to: [email protected] > Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev > _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
