One point somewhere in this thread was about having (in the future) the
framework in core, implemented in C++, with a Python binding on top of it.
This would go against it, but I'm not sure now whether the C++ side is a
must-have or not.
All the tools listed for possible inclusion in this framework are either
in Python or have Python wrapper on top of them (I was claiming for C++
support in the past, this is now history, and the OTB-Qgis glue can and
will be done in Python).
Julien
Le 21/06/2011 13:40, Camilo Polymeris a écrit :
On Tue, Jun 21, 2011 at 7:28 AM, Noli Sicad<[email protected]> wrote:
It seems that PyQT is probably just new. Hence, we have not heard about this,
"Currently, the supported GUI toolkits are wxPython and PyQt. While
both toolkits funtion with Traits, integration with wxPython is
currently more complete. All future development, however, will focus
on supporting PyQt."
I think we would mostly interact with trait's GUI abstraction,
anyways. So we could start development& hope that later PyQt support
will improve (so that we don't depend on wxWidgets).
[...]
I had the same feeling, but I do not know that project.
Any stronger opinions?
I don't think it would be to hard to switch to traits (looks quite
similar to our design), I'll wait a few days to see if someone more
experienced chimes before taking a decision. There may be hidden
limitations or complexities we are not considering.
In the meanwhile focus on converting the module tree to MVC.
Regards,
Camilo
_______________________________________________
Qgis-developer mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/qgis-developer
_______________________________________________
Qgis-developer mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/qgis-developer
