Possible renaming

[Joel B. Mohler]

Hello,

For quite awhile now I've been worried about the 'PyQt' in 'PyQtBindings'
since I suspect that pyside is going to be the preferred qt for python. For
that reason and to reflect the fact that this is (I think) mostly about the
sqlalchemy back-end, I am inclined to rename PyQtBindings to QtAlchemy. I
would welcome any feedback about such a change.

Along with the name change, I'm moving to segment the source tree a bit to
provide guidance about which parts work together. Potentially it could look
like this:

qtalchemy: contains model code like PyQtModels and UserAttr
qtalchemy.entities: contains DomainEntity and supporting classes
qtalchemy.widgets: contains PBKeyEdit and PBTable
qtalchemy.dialogs: contains the list/search dialogs and auth-dialog(s)

I'm not sure if that is too granular, but it reflects the fact that
pyqtbindings/qtalchemy is meaningful (and should be) with-out the more higher
level features in the sub-modules. I think that some of those higher level
features impose my own views too strongly (e.g. DomainEntity and the search
dialogs).

By the way, I'm here at pycon 2011 hacking full time on pyqtbindings right now
for a couple of days.

Thoughts?

Joel

[Tamás Bajusz]

On Tue, Mar 15, 2011 at 3:33 PM, Joel B. Mohler <jo...@kiwistrawberry.us> wrote:
> Hello,
>
> For quite awhile now I've been worried about the 'PyQt' in 'PyQtBindings'
> since I suspect that pyside is going to be the preferred qt for python.  For
> that reason and to reflect the fact that this is (I think) mostly about the
> sqlalchemy back-end, I am inclined to rename PyQtBindings to QtAlchemy.  I
> would welcome any feedback about such a change.

I think the rename is reasonable and creating subpackages is good too.

> Along with the name change, I'm moving to segment the source tree a bit to
> provide guidance about which parts work together.  Potentially it could look
> like this:
>
> qtalchemy:  contains model code like PyQtModels and UserAttr
> qtalchemy.entities:  contains DomainEntity and supporting classes
> qtalchemy.widgets:  contains PBKeyEdit and PBTable
> qtalchemy.dialogs:  contains the list/search dialogs and auth-dialog(s)
>
> I'm not sure if that is too granular, but it reflects the fact that
> pyqtbindings/qtalchemy is meaningful (and should be) with-out the more higher
> level features in the sub-modules.  I think that some of those higher level
> features impose my own views too strongly (e.g. DomainEntity and the search
> dialogs).

I think so. I can imagine others will create other widgets/dialogs or
subclass yours.

> By the way, I'm here at pycon 2011 hacking full time on pyqtbindings right now
> for a couple of days.

Cool! I hope your project will get more users/coders there.
Keep up the good work!

Tamás

[bigt]

after trying a few alternatives, I think that qt-alchemy scans best as a name

[Joel B. Mohler]

On Wednesday, April 13, 2011 11:09:03 am bigt wrote:
> after trying a few alternatives, I think that qt-alchemy scans best as a
> name

Thanks, I'll probably be doing this renaming soon. I wanted to have some more
of the module restructuring in place before I renamed it and put it on the
wiki at http://www.sqlalchemy.org/trac/wiki/SAApps .