<div dir="ltr">Just my two thoughts, I suspect this project would have more success if you used OpenCV as the basis. OpenCV already has many of the features you will need to implement, such as Regions of Interest, in the core engine. It also already has Qt bindings. <div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jun 30, 2017 at 6:13 PM, <span dir="ltr"><<a href="mailto:imagepy@sina.com" target="_blank">imagepy@sina.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>Hi Stefan and Dongyao:</div><div> I think the most difference between camera image, semiconductor industry and biology is the image format, and some specific algrism, As a plugin system, we just need to build general environment, supporting Numpy(uint8, int16, float32, float64), and some common mark(lookup table, scale ruler). about the difference, Developer in different fields can wrote their own reader plugins(such as pydicom).</div><div> bwt:I do not appreciate integrate ui and plugins in scikit-image, scikit-image should be pure a processing library.</div><div><br></div><div> About the ui, wxPhoenix has support Py2, Py3, on Win, Mac ,Linux. You can find Linux whl <a href="https://wxpython.org/Phoenix/snapshot-builds/linux/" target="_blank">here</a> and will be avalible in pypi soon. (In fact I had tested ImagePy on win, mac, linux with py2/py3) I think QT and WX are both OK, but wx is more light weighted (just 10M on win), It is friendly for user to download.</div><div><br></div><div> I also agree with That web is the best choice. But I have no energy to do it myself, I am not good at web, js, I just see the image show and parameter adjust in Jupyter's demo (but the most difficult is to edit the roi line, curve, circle, and polygon, edit the node, sometimes with holes). I would be very happy If I can get contact with their developer!</div><div><br></div><div>Best</div><div>YXDragon</div><div><br></div><div id="m_-3686982500864908881origbody"><div style="background:#f2f2f2">----- 原始邮件 -----<br>发件人：Dongyao Li <<a href="mailto:lidongyao.br@gmail.com" target="_blank">lidongyao.br@gmail.com</a>><br>收件人："Mailing list for scikit-image (<a href="http://scikit-image.org" target="_blank">http://scikit-image.org</a>)" <<a href="mailto:scikit-image@python.org" target="_blank">scikit-image@python.org</a>><br>主题：Re: [scikit-image] building scikit-image plugin and tool set.<br>日期：2017年07月01日 03点40分<br></div><div><div class="h5"><br><div dir="ltr">Hi YXDragon and Stefan:<div><br></div><div>I am a process engineer in semiconductor industry. I wrote a SEM/STEM/TEM analysis software with UI based on scikit-image, pyqt, and others, using the concept of plugins. I agree with Stefan's point that there is a market for this. However my experience is that the images from scientific instruments like SEM/STEM/TEM/MRI are quite different with images from cameras. And people in semiconductor industry and people working on biology have very different needs. I feel like the focus right now is mostly on the biology community.</div><div><br></div><div>I am very happy to hear that we can possibly build a web-based UI for image analysis now. It will integrate the image analysis and further data analysis greatly, which is the our future direction. It would be great if scikit-image could include some demo of it in the future, just like the "viewer" package skimage has right now.</div><div><br></div><div>Best,</div><div>Dongyao</div><div><br></div></div><div><br><div>On Fri, Jun 30, 2017 at 10:48 AM, Stefan van der Walt <span dir="ltr"><<a href="mailto:stefanv@berkeley.edu" target="_blank">stefanv@berkeley.edu</a>></span> wrote:<br><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u>
<div><div>Hi, YXDragon<br></div><span>
<div><br></div>
<div>On Fri, Jun 30, 2017, at 01:46, <a href="mailto:imagepy@sina.com" target="_blank">imagepy@sina.com</a> wrote:<br></div>
<blockquote type="cite"><div> Now I think It is time to build a project named <a href="https://github.com/Image-Py/skimg-plgs" target="_blank">skimg-plgs</a>. And I had <a href="https://github.com/Image-Py/skimg-plgs" target="_blank">wrote some presentative demo</a> with friendly interact. these demo are all from the gallery, (interactive snake contours, interactive watershed...) I want to build a full plugin system and tool set covering scikit-image's every module. Then we can build a large user community like ImageJ, not only programers but also the doctors and biologists.<br></div>
</blockquote><div><br></div>
</span><div>Given the immense success of projects such as ImageJ, and based on feedback I've received from practitioners in microscopy, there is certainly a market for a GUI built on top of scikit-image.<br></div>
<div><br></div>
<div>I don't personally have the time to contribute to such an effort at the moment (my focus is probably best spent keeping skimage on track!), but I am appreciative of the work you are doing, and encourage you to continue.<br></div>
<div><br></div>
<div>I may have mentioned this to you before, but I am not sure about the long-term viability of WXPython. I heard that they have a Phoenix rewrite underway, but looking at the latest PyPI release (<a href="https://pypi.python.org/pypi/wxPython/4.0.0a1" target="_blank">https://pypi.python.org/pypi/<wbr>wxPython/4.0.0a1</a>) they also only support Windows and MacOS.<br></div>
<div><br></div>
<div>With a Jupyter Lab release imminent, I would strongly consider using the web as UI, and building components that integrate with that project. I can put you in contact with their developers, if you like.<br></div>
<div><br></div>
<div>Best regards<br></div>
<div>Stéfan<br></div>
<div><br></div>
</div>
<br>______________________________<wbr>_________________<br>
scikit-image mailing list<br>
<a href="mailto:scikit-image@python.org" target="_blank">scikit-image@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/scikit-image" rel="noreferrer" target="_blank">https://mail.python.org/mailma<wbr>n/listinfo/scikit-image</a><br>
<br></blockquote></div><br></div>
______________________________<wbr>_________________<br>scikit-image mailing list<br><a href="mailto:scikit-image@python.org" target="_blank">scikit-image@python.org</a><br><a href="https://mail.python.org/mailman/listinfo/scikit-image" target="_blank">https://mail.python.org/<wbr>mailman/listinfo/scikit-image</a><br></div></div></div><br>______________________________<wbr>_________________<br>
scikit-image mailing list<br>
<a href="mailto:scikit-image@python.org">scikit-image@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/scikit-image" rel="noreferrer" target="_blank">https://mail.python.org/<wbr>mailman/listinfo/scikit-image</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">Robert McLeod, Ph.D.<br></div><div dir="ltr"><a href="mailto:robert.mcleod@unibas.ch" target="_blank">robert.mcleod@unibas.ch</a></div><div dir="ltr"><span style="font-size:small"><a href="mailto:robert.mcleod@ethz.ch" target="_blank">robert.mcleod@bsse.ethz.ch</a></span></div><div><a href="mailto:robbmcleod@gmail.com" target="_blank">robbmcleod@gmail.com</a><br></div></div></div></div></div></div></div></div></div></div></div></div>
</div>