Updated Python3.x series

[JamieKrueger]

@NinjaCyborg

I did receive your email and will attempt to answer your
questions in my response.

[nbache]

Hi guys

Don't forget that we already have a means of using ReAction from Python (and other languages, e.g. ARexx) in BroadBlues' fine ProAction package.

Best regards,

Niels

[JamieKrueger]

Very true.

The approach taken with ProAction is to send Arexx commands from
Python to an Arexx Host which renders the ReAction GUI. A fine idea
which works great for Arexx scripts and also allows Python a path to
using a GUI as well.

However, when writing in Python, you can simplify the code the user
needs to write by implementing the BOOPSI/ReAction classes as true
Python classes written as Python C Modules.

This allows the GUI classes to be tightly coupled with the Python
program itself, providing more power and flexibility in less lines
of code. It also does not require an outside program manage the
GUI in a different language from the one you are writing in.

[NinjaCyborg]

I haven't come across ProAction. Link please? I had a similar notion to use AWNPipe.

Jamie, back in the day I had plans to port SWIG so that we could automatically make python wrappers for C APIs.

[nbache]

I haven't come across ProAction. Link please? I had a similar notion to use AWNPipe.

http://www.broad.ology.org.uk/amiga/proaction/

Best regards,

Niels

[nbache]

However, when writing in Python, you can simplify the code the user needs to write by implementing the BOOPSI/ReAction classes as true Python classes written as Python C Modules.

This allows the GUI classes to be tightly coupled with the Python program itself, providing more power and flexibility in less lines of code. It also does not require an outside program manage the GUI in a different language from the one you are writing in.

Right, I get it.

But to most people writing in Python, it probably wouldn't matter much if they were using the already existing ProAction with its ARexx host intermediary, or a new tighter implementation. So I am just saying, make sure the effort spent implementing and documenting such a new class-based wrapper (if that's the correct term) gives enough benefit to everybody over using the already existing offering.

Mind you, I am looking at this from the outside. And from there, the prospect of having a newer version of Python itself, more compatible with the ones used on other platforms, is much more interesting.

Best regards,

Niels

[NinjaCyborg]

Thanks for the link. Andy Broad again! Wow that guy is prolific. Didn't he make AWNPipe in the first place? Maybe I'm confusing him with someone else.

My own idea for Python GUI was to port wxwidgets to run over reaction and then port wxpython. But that was in 2005 and I don't even know if wxpython is still a thing these days?

[nbache]

Thanks for the link. Andy Broad again! Wow that guy is prolific. Didn't he make AWNPipe in the first place? Maybe I'm confusing him with someone else.

You probably are. The original author seems to be William Parker, judging by the Aminet info entry (http://aminet.net/package/dev/misc/AWNP_2-54).

Andy made ProAction in connection with his graphics application SketchBlock, in which he uses it as the engine for many of the functionalities.

Best regards,

Niels

[amiganut]

I know this is an old thread but is there any progress on updating Python for OS4.1?