title: Opinions about Enthought Traits/TraitsUI for Python desktop development
body: <p>I'm looking for opinions and experiences about using <a href="http://code.enthought.com/projects/traits/">Traits</a> / <a href="http://code.enthought.com/projects/traits_ui/">TraitsUI</a> / <a href="http://docs.enthought.com/enaml/">enaml</a> for Python desktop development.</p>
  
  <p>The documentation and the Enthought support looks promising, so I wanted to know real first-hand experiences of developers using this stack.</p>
  
  <p>Update:</p>
  
  <p>My main focus of interest is to migrate old several desktop database 
  applications: CRUD / querying / reporting. Then, I'm particulary 
  interested in the data access layer: now, I'm using PosgtreSQL and
  <a href="http://peewee.readthedocs.org/en/latest/peewee/models.html#fields">peewee</a> (a minimalistic ORM):</p>
  
  <ul>
  <li>Is there any built in or side-project support for SQL databases?</li>
  <li>If so, is there any ORM support? (I suppose SqlAlchemy is the 'standard' here)</li>
  </ul>