After reading through the Wiki pages the main question I would have
is: What is the future for contrib packages that do not use the
documentation standards of wxWidgets? I noticed a mention of removing
gizmos (which I have never used), but I think for example that the
styled text control gets used more, and from memory is even part of
PyCrust, which I use.
I also have very, very rough bindings of wxWebConnect which are
certainly not ready for contrib at the moment, but which I think could
theoretically be useful in contrib one day iff it was well supported
for Windows, Linux and Mac (well, better than wxHTML, anyway).
Whether or not it were in contrib I would still want to build it, and
wxWebConnect doesn't have a lot in the way of header documentation.
Jon
···
On Oct 27, 11:37 am, Robin Dunn <ro...@alldunn.com> wrote:
Hi all,
As promised I've published some information about what I am calling
Project Phoenix, also known as the new way to produce the wxPython
wrappers that myself and others have been hinting about for a couple
years now. I've moved a few of my local documents about it up to the
wiki, which list some goals of the project and also a very high level
view of the methodology that I think will be the way to move forward.
I've done some work already on the tools and I will commit them to the
repository once I get an end-to-end test working, hopefully in the next
few days. For now you can read these pages to get a better feel for
what I have in mind.
http://wiki.wxpython.org/ProjectPhoenix
Comments on those pages are welcome, but I think I would prefer to have
discussions here in the mail list for detailed questions, suggestions or
answers.
As promised I've published some information about what I am calling
Project Phoenix, also known as the new way to produce the wxPython
wrappers that myself and others have been hinting about for a couple
years now. I've moved a few of my local documents about it up to the
wiki, which list some goals of the project and also a very high level
view of the methodology that I think will be the way to move forward.
I've done some work already on the tools and I will commit them to the
repository once I get an end-to-end test working, hopefully in the next
few days. For now you can read these pages to get a better feel for
what I have in mind.
Comments on those pages are welcome, but I think I would prefer to have
discussions here in the mail list for detailed questions, suggestions or
answers.
After reading through the Wiki pages the main question I would have
is: What is the future for contrib packages that do not use the
documentation standards of wxWidgets? I noticed a mention of removing
gizmos (which I have never used), but I think for example that the
styled text control gets used more, and from memory is even part of
PyCrust, which I use.
STC has been moved to wxWidgets core in 2.9, so it is safe. The mention of removing gizmos is because the code itself is not maintained, not because its documentation is substandard.
I also have very, very rough bindings of wxWebConnect which are
certainly not ready for contrib at the moment, but which I think could
theoretically be useful in contrib one day iff it was well supported
for Windows, Linux and Mac (well, better than wxHTML, anyway).
Whether or not it were in contrib I would still want to build it, and
wxWebConnect doesn't have a lot in the way of header documentation.
The new method will not prevent creating the bindings generator code by hand, it simply automates most of the work in creating that code if the headers are able to be run through Doxygen.
···
On 10/27/10 6:17 AM, Jonathan Morgan wrote:
On Oct 27, 11:37 am, Robin Dunn<ro...@alldunn.com> wrote:
Comments on those pages are welcome, but I think I would prefer to have
discussions here in the mail list for detailed questions, suggestions or
answers.
After reading through the Wiki pages the main question I would have
is: What is the future for contrib packages that do not use the
documentation standards of wxWidgets? I noticed a mention of removing
gizmos (which I have never used), but I think for example that the
styled text control gets used more, and from memory is even part of
PyCrust, which I use.
STC has been moved to wxWidgets core in 2.9, so it is safe. The mention of removing gizmos is because the code itself is not maintained, not because its documentation is substandard.
I also have very, very rough bindings of wxWebConnect which are
certainly not ready for contrib at the moment, but which I think could
theoretically be useful in contrib one day iff it was well supported
for Windows, Linux and Mac (well, better than wxHTML, anyway).
Whether or not it were in contrib I would still want to build it, and
wxWebConnect doesn’t have a lot in the way of header documentation.
The new method will not prevent creating the bindings generator code by hand, it simply automates most of the work in creating that code if the headers are able to be run through Doxygen.