[GRASS-dev] Interest in GSoC 2016

massimo di stefano massimodisasha at gmail.com
Fri Mar 25 05:46:43 PDT 2016

Hi Anna,

Depending on how much effort the implementation in Qt of the current rendering system will require
maybe is worth to explore new rendering tools. 
Or design the gui code base in a way that will make the adoption of new rendering systems as easy as possible. 
It is my understanding that the hardest part will be the development of tools to interact with the map canvas.

for the rendering I was thinking of 2 different approaches using library like vispy:

http://vispy.org/ <http://vispy.org/>

or datashader:

https://github.com/bokeh/datashader <https://github.com/bokeh/datashader>

the first is an OpenGL rendering system (smooth pan/zoom and continue rendering)
the second is suitable for large data (render billions of point without crashing the app)

I tried both with standard dataset.

vispy is an attractive library very fast rendering but I don’t know how much effort is required to implement 
“mouse events like digitizing and other map canvas interactive tools”

datashader is more “matplotlib-like”, at an api level, 
that should make the development of tools to interact with the map canvas a little easier.

I agree with you, a new rendering system can be coded outside GSoC, what you mentioned

> using the
> current rendering system and focusing on rewriting to qt plus
> refactoring of the current code

is indeed a lot of work for a single GSoC.
I’ve some experience with PyQt, and I’m willing to help in making this a successful idea.


> On Mar 24, 2016, at 10:32 PM, Anna Petrášová <kratochanna at gmail.com> wrote:
> On Thu, Mar 24, 2016 at 10:12 PM, massimo di stefano
> <massimodisasha at gmail.com <mailto:massimodisasha at gmail.com>> wrote:
>> Hi Ondřej,
>> I also think that Qt is a mature, powerful and stable framework to develop
>> GUI.
>> I was wondering if you considered the adoption of modern OpenGL based
>> rendering system.
> Could you be more specific about the OpenGL, do you have some
> solutions in mind? I thought this project would be about using the
> current rendering system and focusing on rewriting to qt plus
> refactoring of the current code because that alone is  a lot of work
> if you are not familiar with the current codebase. Better rendering
> could be added later on. But I think Ondrej is open to suggestions.
> Anna
>> Thanks,
>> Massimo.
>> On Mar 17, 2016, at 2:45 PM, Ondra.Lobo at seznam.cz wrote:
>> Hi,
>> My name is Ondřej Pešek and I am student of Czech Technical University in
>> Prague.  I am in the last year of bachelor studium (geodesy, cartography and
>> geoinformatics). My bachelor thesis is development of QGis plugin (for
>> aerial data leveling). I’m developing in python and I have some basics in
>> C++. Often I work also with other gis programs (ArcGis). I am very
>> interested in co-working with Grass for Google Summer of Code 2016.
>> My idea was to generalize GUI Code for Qt-based GUI. Nowadays, Qt (PyQt) is
>> increasingly used (look at QGis, for example) and I think it would be better
>> to have minimally the roots of GUI in Qt. It’s also much easier to maintain
>> with new features. Work with design is also much more user-friendly. It
>> seems that in the future, it can be nice shortcut to change something in the
>> GUI.
>> Thanks and I’m looking forward for your answers,
>> Ondřej Pešek
>> _______________________________________________
>> grass-dev mailing list
>> grass-dev at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/grass-dev
>> _______________________________________________
>> grass-dev mailing list
>> grass-dev at lists.osgeo.org <mailto:grass-dev at lists.osgeo.org>
>> http://lists.osgeo.org/mailman/listinfo/grass-dev <http://lists.osgeo.org/mailman/listinfo/grass-dev>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20160325/c75ce51b/attachment-0001.html>

More information about the grass-dev mailing list