just a question: do we need swig in GRASS 7? Python bindings has been
replaced by ctypes interface. Other bindings (e.g. perl) are not
maintained. Could be `swig` directory removed from source tree?
just a question: do we need swig in GRASS 7? Python bindings has been
replaced by ctypes interface. Other bindings (e.g. perl) are not
maintained. Could be `swig` directory removed from source tree?
from what I understand SWIG is pretty big with the Java crowd too*. can
anyone comment on that?
[*] just in the world of SWIG users, I've never heard of a grass user
using swig+java that way
just a question: do we need swig in GRASS 7? Python bindings has been
replaced by ctypes interface. Other bindings (e.g. perl) are not
maintained. Could be `swig` directory removed from source tree?
It's still used for the vdigit module. But both vdigit and nviz need
significant re-writes anyhow. My inclination for 7.0 would be to
remove everything related to SWIG, and disable the vdigit and nviz
modules.
If I could figure out how to do the latter without breaking wxGUI as a
whole, I would have done it already.
It's still used for the vdigit module. But both vdigit and nviz need
significant re-writes anyhow. My inclination for 7.0 would be to
I am planning to rewrite wxGUI digitizer to Python (probably later in August).
remove everything related to SWIG, and disable the vdigit and nviz
modules.
Do you speak about TCL/TK nviz or wxNviz? TCL/TK Nviz can be removed
when wxNviz is ready. wxNviz has been rewritten to Python by you.
AFAIU only one blocker is wxGUI digitizer.
> It's still used for the vdigit module. But both vdigit and nviz need
> significant re-writes anyhow. My inclination for 7.0 would be to
I am planning to rewrite wxGUI digitizer to Python (probably later in August).
> remove everything related to SWIG, and disable the vdigit and nviz
> modules.
Do you speak about TCL/TK nviz or wxNviz? TCL/TK Nviz can be removed
when wxNviz is ready. wxNviz has been rewritten to Python by you.
AFAIU only one blocker is wxGUI digitizer.
I'm referring to the nviz and vdigit modules for the wxPython GUI.
The problem is that these should be distinct processes rather than
part of the main GUI process. The main GUI should only use the
standard Python library (minus ctypes) plus well-tested, mainstream
add-ons such as wxPython and NumPy.
Under no circumstances should libgrass_anything.so find its way into
the main wxGUI process. The GRASS libraries are not suitable for such
purposes, and never will be.