On Wed, Sep 23, 2009 at 12:19:12AM +0100, Alberto Ruiz wrote: > 2009/9/22 Alessandro Dentella <[email protected]>: > >> I like it for extensibility and mapping to complex sql schema's, but > >> I was thinking if I could map all columns of a treeview and an extra > >> column for the path. The path could then be applied to create the > > > > in the first, non public, release of sqlkit I used a 1:1 mapping between > > liststore (I don't currently use treestores) and it turned out to be slower. > > > > Ythe reason is that in that case, you have to distribute the data you get > > from the class to the model for all values of the model, while I let the > > column's cell_data_function to do it just for the visible cells. > > Hi guys, > > What you guys should be doing is implementing the TreeModel interface > on top of your ORM instead of feeding a TreeStore/ListStore object. > > Note that treestore/liststore is just a reference implementation of > the treemodel interface that gets abused very often (actually due to > TreeModel being a huge interface to implement though). This would be > the only way to have a proper model with an acceptable performance.
that's an interesting idea, but the "huge interface to implement" scares me, and I have so many ideas to add to sqlkit before pushing the performance that is not bad anyhow. I'd give a try if sombody else implemented it, thought! sandro *:-) -- Sandro Dentella *:-) http://sqlkit.argolinux.org SQLkit home page - PyGTK/python/sqlalchemy _______________________________________________ pygtk mailing list [email protected] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://faq.pygtk.org/
