[guidata/guiqwt] Merging "guidata" and "guiqwt" into a new library named...

[Pierre Raybaut]

Hi all,

Along with some code cleaning (and maybe some API breaks..), I'm thinking
of merging "guidata" and "guiqwt" into a single library which would only
depend on PyQt, PythonQwt, NumPy, SciPy and Pillow.

(Note that since guiqwt v3, PyQwt has been replaced by PythonQwt which is
pure Python [great for portability and easy deployment/installation] and
which supports both PyQt4 and PyQt5!)

The new library would be named...

...guiplot ? (*g*raphical *u*ser *i*nterfaces for image and signal *plot*ting...
or something like that)
...scigui ? (*sci*entific *g*raphical *u*ser *i*nterfaces)
...sigrail ? (*s*ignal and *i*mage *gra*ph*i*ng *l*ibrary) -> Python, Monty
Python, "Monty Python and the Holy Grail"...
...scigrail ? (*sci*entific *gra*ph*i*ng *l*ibrary) (variant)

Any thoughts?

-Pierre

[Cyril Giraudon]

An idea: SciForm

Cyril.

Post by Pierre Raybaut
Hi all,
Along with some code cleaning (and maybe some API breaks..), I'm thinking
of merging "guidata" and "guiqwt" into a single library which would only
depend on PyQt, PythonQwt, NumPy, SciPy and Pillow.
(Note that since guiqwt v3, PyQwt has been replaced by PythonQwt which is
pure Python [great for portability and easy deployment/installation] and
which supports both PyQt4 and PyQt5!)
The new library would be named...
...guiplot ? (*g*raphical *u*ser *i*nterfaces for image and signal *plot*ting...
or something like that)
...scigui ? (*sci*entific *g*raphical *u*ser *i*nterfaces)
...sigrail ? (*s*ignal and *i*mage *gra*ph*i*ng *l*ibrary) -> Python,
Monty Python, "Monty Python and the Holy Grail"...
...scigrail ? (*sci*entific *gra*ph*i*ng *l*ibrary) (variant)
Any thoughts?
-Pierre

[Pete Bachant]

What are the main uses of this library? In the past, I've used guiqwt
widgets in my PyQt apps for plotting real time signals where Matplotlib was
too slow. That seems to me the best niche for this library (competing with
pyqtgraph), since Bokeh is probably dominating the interactive plotting
applications now.

Post by Pierre Raybaut
Hi all,
Along with some code cleaning (and maybe some API breaks..), I'm thinking
of merging "guidata" and "guiqwt" into a single library which would only
depend on PyQt, PythonQwt, NumPy, SciPy and Pillow.
(Note that since guiqwt v3, PyQwt has been replaced by PythonQwt which is
pure Python [great for portability and easy deployment/installation] and
which supports both PyQt4 and PyQt5!)
The new library would be named...
...guiplot ? (*g*raphical *u*ser *i*nterfaces for image and signal *plot*ting...
or something like that)
...scigui ? (*sci*entific *g*raphical *u*ser *i*nterfaces)
...sigrail ? (*s*ignal and *i*mage *gra*ph*i*ng *l*ibrary) -> Python,
Monty Python, "Monty Python and the Holy Grail"...
...scigrail ? (*sci*entific *gra*ph*i*ng *l*ibrary) (variant)
Any thoughts?
-Pierre

[Pierre Raybaut]

Apart from the signal plotting performance, one could mention the huge gap between guiqwt and matplotlib in terms of image visualization performance (e.g. showing 20,000 x 20,000 images and zooming in/out continuously in real-time with your mouse is possible) and features (contrast adjustment, cross sections, mask tools, etc.).

As for the interactivity, I'm not comparing it to Bokeh since the end-user should not be the same:
As far as I know, Bokeh is for plotting data inside a web page.guiqwt produces Qt widgets that can be used to plot signals or show images à la MATLAB but it is especially suited for embedding such widgets in Qt desktop applications (to develop signal and image processing software).

So, to sum-up the main uses of this library, I'd say that it's mainly for developping desktop Qt-based signal and image processing software requiring fast visualization and interactive tools.



Date: Fri, 13 May 2016 05:57:32 -0700
From: ***@gmail.com
To: ***@googlegroups.com
Subject: [guidata/guiqwt] Re: Merging "guidata" and "guiqwt" into a new library named...

What are the main uses of this library? In the past, I've used guiqwt widgets in my PyQt apps for plotting real time signals where Matplotlib was too slow. That seems to me the best niche for this library (competing with pyqtgraph), since Bokeh is probably dominating the interactive plotting applications now.


On Friday, May 13, 2016 at 4:26:40 AM UTC-4, Pierre Raybaut wrote:Hi all,

Along with some code cleaning (and maybe some API breaks..), I'm thinking of merging "guidata" and "guiqwt" into a single library which would only depend on PyQt, PythonQwt, NumPy, SciPy and Pillow.

(Note that since guiqwt v3, PyQwt has been replaced by PythonQwt which is pure Python [great for portability and easy deployment/installation] and which supports both PyQt4 and PyQt5!)

The new library would be named...

...guiplot ? (graphical user interfaces for image and signal plotting... or something like that)
...scigui ? (scientific graphical user interfaces)
...sigrail ? (signal and image graphing library) -> Python, Monty Python, "Monty Python and the Holy Grail"...
...scigrail ? (scientific graphing library) (variant)

Any thoughts?

-Pierre
--
You received this message because you are subscribed to the Google Groups "guidata/guiqwt" group.

To unsubscribe from this group and stop receiving emails from it, send an email to guidata_guiqwt+***@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Michael S]

Given the popularity of the libraries in terms of their GUI capabilities,
their scientific basis and keeping the reference to guidata and guiqwt:

One suggestion would be: *guisci*

*gui: *Keeping the link with guidata & guiqwt and the awesome abilities the
merged library has wrt these.
*sci: *Beacuse fundamentally these libraries stem from a scientific use
case.

Just a suggestion :)

Post by Pierre Raybaut
Apart from the signal plotting performance, one could mention the huge gap
between guiqwt and matplotlib in terms of image visualization performance
(e.g. showing 20,000 x 20,000 images and zooming in/out continuously in
real-time with your mouse is possible) and features (contrast adjustment,
cross sections, mask tools, etc.).
As for the interactivity, I'm not comparing it to Bokeh since the end-user
- As far as I know, Bokeh is for plotting data inside a web page.
- guiqwt produces Qt widgets that can be used to plot signals or show
images à la MATLAB but it is especially suited for embedding such widgets
in Qt desktop applications (to develop signal and image processing
software).
So, to sum-up the main uses of this library, I'd say that it's mainly for
developping desktop Qt-based signal and image processing software requiring
fast visualization and interactive tools.
------------------------------
Date: Fri, 13 May 2016 05:57:32 -0700
Subject: [guidata/guiqwt] Re: Merging "guidata" and "guiqwt" into a new library named...
What are the main uses of this library? In the past, I've used guiqwt
widgets in my PyQt apps for plotting real time signals where Matplotlib was
too slow. That seems to me the best niche for this library (competing with
pyqtgraph), since Bokeh is probably dominating the interactive plotting
applications now.
Hi all,
Along with some code cleaning (and maybe some API breaks..), I'm thinking
of merging "guidata" and "guiqwt" into a single library which would only
depend on PyQt, PythonQwt, NumPy, SciPy and Pillow.
(Note that since guiqwt v3, PyQwt has been replaced by PythonQwt which is
pure Python [great for portability and easy deployment/installation] and
which supports both PyQt4 and PyQt5!)
The new library would be named...
...guiplot ? (*g*raphical *u*ser *i*nterfaces for image and signal *plot*ting...
or something like that)
...scigui ? (*sci*entific *g*raphical *u*ser *i*nterfaces)
...sigrail ? (*s*ignal and *i*mage *gra*ph*i*ng *l*ibrary) -> Python,
Monty Python, "Monty Python and the Holy Grail"...
...scigrail ? (*sci*entific *gra*ph*i*ng *l*ibrary) (variant)
Any thoughts?
-Pierre
--
You received this message because you are subscribed to the Google Groups
"guidata/guiqwt" group.
To unsubscribe from this group and stop receiving emails from it, send an
For more options, visit https://groups.google.com/d/optout.

[Big Stone]

Hi,

"PyQtGui" would fit nicely along "PyQtGraph"

Post by Michael S
Given the popularity of the libraries in terms of their GUI capabilities,
One suggestion would be: *guisci*
*gui: *Keeping the link with guidata & guiqwt and the awesome abilities
the merged library has wrt these.
*sci: *Beacuse fundamentally these libraries stem from a scientific use
case.
Just a suggestion :)

Post by Pierre Raybaut
Apart from the signal plotting performance, one could mention the huge
gap between guiqwt and matplotlib in terms of image visualization
performance (e.g. showing 20,000 x 20,000 images and zooming in/out
continuously in real-time with your mouse is possible) and features
(contrast adjustment, cross sections, mask tools, etc.).
As for the interactivity, I'm not comparing it to Bokeh since the
- As far as I know, Bokeh is for plotting data inside a web page.
- guiqwt produces Qt widgets that can be used to plot signals or show
images à la MATLAB but it is especially suited for embedding such widgets
in Qt desktop applications (to develop signal and image processing
software).
So, to sum-up the main uses of this library, I'd say that it's mainly for
developping desktop Qt-based signal and image processing software requiring
fast visualization and interactive tools.
------------------------------
Date: Fri, 13 May 2016 05:57:32 -0700
Subject: [guidata/guiqwt] Re: Merging "guidata" and "guiqwt" into a new library named...
What are the main uses of this library? In the past, I've used guiqwt
widgets in my PyQt apps for plotting real time signals where Matplotlib was
too slow. That seems to me the best niche for this library (competing with
pyqtgraph), since Bokeh is probably dominating the interactive plotting
applications now.
Hi all,
Along with some code cleaning (and maybe some API breaks..), I'm thinking
of merging "guidata" and "guiqwt" into a single library which would only
depend on PyQt, PythonQwt, NumPy, SciPy and Pillow.
(Note that since guiqwt v3, PyQwt has been replaced by PythonQwt which is
pure Python [great for portability and easy deployment/installation] and
which supports both PyQt4 and PyQt5!)
The new library would be named...
...guiplot ? (*g*raphical *u*ser *i*nterfaces for image and signal *plot*ting...
or something like that)
...scigui ? (*sci*entific *g*raphical *u*ser *i*nterfaces)
...sigrail ? (*s*ignal and *i*mage *gra*ph*i*ng *l*ibrary) -> Python,
Monty Python, "Monty Python and the Holy Grail"...
...scigrail ? (*sci*entific *gra*ph*i*ng *l*ibrary) (variant)
Any thoughts?
-Pierre
--
You received this message because you are subscribed to the Google Groups
"guidata/guiqwt" group.
To unsubscribe from this group and stop receiving emails from it, send an
For more options, visit https://groups.google.com/d/optout.

[Mous Tatarkhanov]

Hi Pierre,

Just checking to see if there has been a decision on the merged module.

SciGui or keeping the name as GuiQwt sound good!

Mous.

[Claude]

And the winner is ??

Claude

Post by Pierre Raybaut
Hi all,
Along with some code cleaning (and maybe some API breaks..), I'm thinking
of merging "guidata" and "guiqwt" into a single library which would only
depend on PyQt, PythonQwt, NumPy, SciPy and Pillow.
(Note that since guiqwt v3, PyQwt has been replaced by PythonQwt which is
pure Python [great for portability and easy deployment/installation] and
which supports both PyQt4 and PyQt5!)
The new library would be named...
...guiplot ? (*g*raphical *u*ser *i*nterfaces for image and signal *plot*ting...
or something like that)
...scigui ? (*sci*entific *g*raphical *u*ser *i*nterfaces)
...sigrail ? (*s*ignal and *i*mage *gra*ph*i*ng *l*ibrary) -> Python,
Monty Python, "Monty Python and the Holy Grail"...
...scigrail ? (*sci*entific *gra*ph*i*ng *l*ibrary) (variant)
Any thoughts?
-Pierre