> As I mentioned in my earlier post, when we migrate to traits
> for matplotlib artist properties, we will get a pretty rich
> interactive UI configuration layer.
Any sense of when this might happen?
There is no specific timeline, but Darren did a bunch of the hard work
getting a traits enabled rc configuration option (off by default) in
0.91.2. The plan is to turn get this turned on by default in the next
release of the trunk (0.98) so we can get as much pain in at once
rather than in doses. Since migrating apps to the trunk requires some
changes in the API (transformations, bounding boxes) already, this
would probably be a good time to migrate the rc configuration too.
Is there anybody outside of enthought who are deploying applications
based on TraitsUI for Windows/Mac/Linux? I would love to hear about
successful examples before committing to more dependencies in our own
applications.
Well, we are already installing enthought.traits and have not
experienced any significant user problems, so I don't think we will be
introducing a significant dependency here. This can be done so that
users who have a UI enabled traits will get the UI benefits and those
who don't will get the basic traits benefits minus the UI. So we
wouldn't need to depend on the UI components, and we have already
(mostly) solved the dependency problem on the non UI component (see
matplotlib/lib/enthought).
I say mostly because there is a problem that Gael first reported
recently that having our enthought traits installed ahead of
enthought's version can break some enthought apps, so we need to
address this. And yes, there are some startup time problems with a
namespace enabled version of enthought's packages that have caused
some concern.
What's going to happen with Qt/Gtk/Tkinter backends? We are already
using wx so this isn't an issue for us, but last time I looked TraitsUI
only had wx support.
As far as I understand, there is a fully featured wx version and qt is
coming along nicely. Again, matplotlib would continue to work as
before with the other UI backends, your just wouldn't get the traits
dialogs.
A specific concern we had when investigating Traits a couple of
years ago was long start up times. The lack of clear boundaries
between traits and other parts of enthought was a further concern,
since it would make deployment more difficult.
This is getting much better, but it is still a work in progress.
traits is now in debian, for example.
JDH
···
On Feb 13, 2008 10:04 AM, Paul Kienzle <pkienzle@...537...> wrote:
On Wed, Feb 13, 2008 at 08:24:35AM -0600, John Hunter wrote: