On 26.04.2010 22:30, ext Renato Araujo Oliveira Filho wrote:
Hello all,
I have been following this thread and I have some considerations about
that PSEP. This is my personal feelings about the discussion.
You know, it'd be more constructive to participate in the discussion
while the document is evolving, not when it's just missing the final
stamp of approval...
First point is the name of PSEP. I did not like this "Adopt PyQt's API
2 for PySide" because the main point here is to create a pythonic API
and not just to follow the PyQt API. Some points of PyQt API are good,
I know, but one of the main ideas of creating a new Qt binding is to
avoid the problems found on PyQt API. I don't think following the PyQt
API is a good way to take
In my opinion, the current PSEP title is very much to the point. The
PSEP proposes that PyQt's API 2 should be adopted for PySide and
describes the differences to PyQt's approach. Do you have an alternative
title in mind?
As for the argument of principle of not following PyQt's API because we
didn't invent it ourselves, I think it's, well, maybe not entirely
logical. If something in PyQt is mature and well thought out, it serves
everyone's interests that we adopt the same API. If we're able to invent
something radically better, that's great, but abandoning compatibility
should always be a careful and weighed decision.
Also, I don't think your claim of the project's main point being
creating a Pythonic API completely resonates with the stated project
goals [1]. For me, the first priority has always been to create
liberally licensed Qt bindings for Python with a complete toolchain
available. Secondly, we have aimed for API-compatibility with PyQt. This
is a valuable goal in itself as it provides for much easier
interoperability and easier adoption of PySide. However, we have opted
to not do it blindly but make a conscious decision for adopting any new
PyQt APIs. That's the process we're in right now. So yes, we can strive
for a more Pythonic API but that should be done carefully and in a way
minimizing the impact for existing Python Qt developers.
[1] http://www.pyside.org/about/
I think we need to grow by ourselves with the community helping of
course, because we are creating the bindings to the community. I'm
afraid of being always following the PyQt API and never be original to
create best bindings. I think we need to discuss, not to choose if we
will adopt the PyQt API, but what is the best way to transform the
current Qt API in a more pythonic API. We need to be creative and
original to create a real pythonic API.
Please make proposals to improve the PSEP being discussed. I think that
would be the most productive way of approaching the issue...
Cheers,
ma.
_______________________________________________
PySide mailing list
[email protected]
http://lists.openbossa.org/listinfo/pyside
