On Sat, Aug 4, 2012 at 5:16 PM, Tim Sutton li...@linfiniti.com wrote:
Hi All (Especially Paolo and Victor)
For interest of others, Paolo, Victor and myself had an offlist
discussion about the procedure for moving SEXTANTE into QGIS core.
This weekend I took the first step my exporting the
Thank you, Tim. That helped a lot.
On Thu, Jul 19, 2012 at 3:38 AM, Tim Sutton li...@linfiniti.com wrote:
Hi
On Thu, Jul 19, 2012 at 9:36 AM, Tim Sutton li...@linfiniti.com wrote:
Hi
On Wed, Jul 18, 2012 at 12:58 AM, Camilo Polymeris cpolyme...@gmail.com
wrote:
Hello all,
I have had
Hello all,
I have had some difficulty with implementing the tests for Sextante,
in particular, using QgsProviderRegistry.
cf:
http://code.google.com/p/sextante/source/browse/trunk/soft/bindings/qgis-plugin/src/sextante/tests/qgis_interface.py
The providers seem not to load. Note that the qgis
Hello again,
in case you missed the post on the soc mailing list, I have posted a
first report on this project at sextante-gsoc.blogspot.com
I haven't figured out how to attach files to blogger posts so I'll
just attach a diff to this thread, so you can have a look at the
preliminary
Hello Victor,
cc: qgis-developers mailing list.
I am working on the mt thing. You can see the approach I am taking in
the attached diff, but it basically revolves around starting a QThread
for each algorithm qt signaling.
Still not sure how to replace e.g. the progress objects.
Also, created a
On Sun, May 13, 2012 at 5:13 PM, Victor Olaya vola...@gmail.com wrote:
Here is my opinion on all that, in short:
-The main idea of using threads is not now to execute multiplep
algorithms at the same time, so we can remove a lot of complexity
(like 2 processes writing the same file, as it was
in sextante
To: Camilo Polymeris cpolyme...@gmail.com, Victor Olaya
vola...@gmail.com, Alexander Bruy alexander.b...@gmail.com,
Giuseppe Sucameli sucam...@faunalia.it
Hi all.
I'm here with Giuseppe AKA brushtyler, and we're having a very
interesting discussion
about threads sextante. I would suggest
On Tue, Apr 24, 2012 at 6:55 AM, Anne Ghisla a.ghi...@gmail.com wrote:
Hello all, and sorry for cross-posting,
let me introduce our 4 accepted students for OSGeo Google Summer of
Code 2012:
- Camilo Polymeris, mentored by Victor Olaya on the project Orfeo
Toolbox backend for the Sextante
On Tue, Mar 27, 2012 at 4:18 AM, Victor Olaya vola...@gmail.com wrote:
Yes, I wonder about that too. I don't haven't really figured out how
sextante works, but it seems a very different approach: calls backends
through the commandline, which makes it much simpler to implement, of
course, but
[0] http://lists.osgeo.org/pipermail/qgis-developer/2012-March/018823.html
[1]
http://code.google.com/p/sextante/source/browse/#svn%2Ftrunk%2Fsoft%2Fbindings%2Fqgis-plugin
Sure, having two frameworks makes no sense.
Anyone had the time to check the new sextante implementation?
If I
On Thu, Mar 22, 2012 at 5:31 AM, Martin Dobias wonder...@gmail.com wrote:
On Wed, Mar 21, 2012 at 7:23 PM, CzendaZdenda tramt...@seznam.cz wrote:
If there is possibility that output parameter of the module can have any
type, how can I handle with modules' outputs? Or just raster/vector layers
I understand it *does* mean that you have to be the one sending the
source. If you distribute a GPL'd binary without source you have to
include a written offer to send the source to any party that receives
that binary, even indirectly. In general it should be easier to
include the source in
It would be any user getting their hands on this binary. If your client
gives a copy to his friend then his friend has the right to the source (it
doesn't mean that YOU have to the one sending the source).
I understand it *does* mean that you have to be the one sending the
source. If you
Hello all,
Yes, I will glad to help you. At beginning, is there some small problem, on
which I can test me, whether my programming skills are enough and I am able
to help you?
I think Camilo is the best person to talk to. Please have a look to the
archives of
the ML, and to
Hello Zdenek,
Yes, I will glad to help you. At beginning, is there some small problem, on
which I can test me, whether my programming skills are enough and I am able
to help you?
if you are looking for a smaller task to get familiar with the code
base, we have a list of pending issues, here:
:
http://www.gvsig.com/files/images/screenshots/gvSIG_Sextante_02.png
or, a patchbay-style GUI:
On Tue, Aug 23, 2011 at 9:45 PM, Camilo Polymeris cpolyme...@gmail.com
wrote:
A bit like qjackctl's patchbay:
http://ubuntu.allmyapps.com/data/q/j/qjackctl-jack-control/UBUNTU-9.04
Hello again,
there is another processing-framework-related issue I would like your
opinion on:
The input and output layers of modules are currently stored in the
/temp directory or its windows equivalent. These files are, of course,
not persistent between sessions. Or as Paolo wrote in the
I am not much of a designer... but still, had fun creating a variation
of your idea:
http://imageshare.web.id/images/xb6dtdeotcghebwct53k.png
Regards
Camilo
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
I agree with martin - such a Modeler could be a great improvement but
I assumed it would be somethink like the WxGUI_Modeler ..
Yes, I also imagine something similar.
But, I prefer more ordered layouts, where you have all outputs in a
column on the left side, and all inputs in a column on the
It's great to see the final touches improving the usability.
Regarding the number of settings it would be good to offer as few
choices as possible. Many times the settings can be avoided and a
sensible default choice can be used. For example the setting Number
of tags to show is very
Hello everyone,
I am happy to say that this week saw many improvements in the QGIS
Processing Framework and the interface to SAGA.
Primarily, raster input and output works now, thanks to help from SAGA
developer Volker Wichmann. Single band local QGIS rasters are
transparently converted to SAGA
Now we have to think about human interface. One thing is: which terms should
be used?
SAGA uses grid, whereas QGIS uses raster. To me, the idea is to have a
consistent
GUI in QGIS, so better use the QGIS terms not to scare off our users, but
this could
be confusing for previous SAGA
Hello
This week I have implemented Range parameters and tried to implemented
the SAGA's raster output. To do this I have tried to solve various
issues, mostly regarding specifying grid systems to the module. I have
implemented a widget that allows the user to set a custom grid system
and
I have fallen a bit behind schedule while trying to implement data
exchange. Many issues have arisen, but finally vector output (from
SAGA's perspective) is working. Neither input nor raster work yet.
Next, I'll consider the former, while also fixing some bugs in
parameter selection (especially
Hello everyone,
This week+, I polished different parts of the module dialog, adding
specific widgets callbacks (signals) for actions value changes,
including, e.g. a FileSelector widget for paths, and a combobox for
available layers or module specific choices. See screenshot [1].
This will
On Fri, Jul 8, 2011 at 1:25 AM, Paolo Cavallini cavall...@faunalia.it wrote:
Il 07/07/2011 23:06, Camilo Polymeris ha scritto:
identify a few and compile a short list[1], to try to keep focused
List missing ;)
Oops.
[1] https://github.com/polymeris/qgis/wiki/Timeline
On Fri, Jul 8, 2011 at 2:53 AM, Tim Sutton li...@linfiniti.com wrote:
Hi
Sorry I just caught up on this thread now. I share Martin's concern
about dropping C++ support by adopting traits directly. Have you made
a decision on this, is C++ still on the cards?
Yes, it still is -- I intend to
Hello everyone,
the end of GSoC's first term is nearing and while I think we have made
a significant progress, many things are still pending. I have tried to
identify a few and compile a short list[1], to try to keep focused
during the next few weeks.
I'll try to create a proper timeline with
I don't know if this is relevant to the crashes you have been getting, but
TraitsUI and most other Enthought Qt-oriented GUI projects use version 2 of
the SIP QString and QVariant APIs:
https://github.com/enthought/pyface/blob/master/pyface/qt/__init__.py
This is done so they can swap
Hello saga developers,
in case you haven't followed the development of the QGIS Processing
Framework and SAGA interface, a short introduction:
I was selected to implement a QGIS to SAGA interface in context of
Google's Summer of Code 2011 program. The last weeks have been spent
designing and
I have ported the parameter system to traits, but am not sure if I am
taking the right approach. Dynamically generating the module
definitions and instances is problematic using traits. A more elegant
way would be to create a new python type for each module (perhaps
using `type()`), subclassing
On Mon, Jun 27, 2011 at 3:59 PM, Camilo Polymeris cpolyme...@gmail.com wrote:
Given that there are no objections I have studied the traits docs
without finding any reason against it, I'll start migration of the
framework.
Having trouble with that.. QGIS segfaults when I try to load any
On Mon, Jun 27, 2011 at 3:59 PM, Camilo Polymeris cpolyme...@gmail.com
wrote:
Given that there are no objections I have studied the traits docs
without finding any reason against it, I'll start migration of the
framework.
Having trouble with that.. QGIS segfaults when I try to load any
I can confirm the crash on Fedora 15, QGIS 1.6 and ETS 3.5. However, after
installing the fresh ETS 4.0 from Github (http://code.enthought.com/source/)
I can import traits.api (namespace 'enthought' has been removed in 4.0)
through QGIS Python console. Same applies to openSUSE 11.4 (64-bit)
The saga-qgis interface is pretty much non-functional yet. Could you specify
which problems you have encountered?
Are you using the faunalia version?
Camilo
El jun 28, 2011 12:35 p.m., Agustin Lobo alobolis...@gmail.com escribió:
Johan,
Problem solved by adding your repository:
deb
On Tue, Jun 21, 2011 at 7:28 AM, Noli Sicad nsi...@gmail.com wrote:
It seems that PyQT is probably just new. Hence, we have not heard about this,
Currently, the supported GUI toolkits are wxPython and PyQt. While
both toolkits funtion with Traits, integration with wxPython is
currently more
On Tue, Jun 21, 2011 at 9:31 AM, Julien Malik julien.ma...@c-s.fr wrote:
One point somewhere in this thread was about having (in the future) the
framework in core, implemented in C++, with a Python binding on top of it.
This would go against it, but I'm not sure now whether the C++ side is a
This week the Framework's design saw many changes. Julien has started
to experiment with interfacing it to the Orfeo Toolbox, and from the
ensuing discussion the conclusions of creating a separate plugin for
the framwork's gui, sort of a module manager, now called
processingplugin and removing
On Thu, Jun 9, 2011 at 5:18 AM, Michael Pfeiffer
michael.pfeif...@bd.so.ch wrote:
Hi everybody,
no hints for this problem?
I have the same problem with the mapcomposer window.
When closing the mapcomposer window I want to get the close signal or close
event of the window.
I need this
On Mon, Jun 13, 2011 at 10:15 AM, MALIK Julien julien.ma...@c-s.fr wrote:
Hello,
Hello, Julien.
You bring up some very important points.
Here are some remarks :
- It's good to have deleted the Library class. I had no use of it. This
makes the code much more simpler.
- Is the Plugin class
On Sat, Jun 4, 2011 at 9:06 PM, Nathan Woodrow madman...@gmail.com wrote:
Looking good. My hope onces this is all done is to be able to rewrite all
the tools in fTools to use the framework. That way eventually everything
can be linked together and called in the same way.
- Nathan
Thanks.
Hello,
This week, I coded a GUI list of modules, sorted by tag (which in the
case of SAGA are determined programmatically), plus the basics of a
'run module' dialog. I have started working on the parameter passing
aspect of the framework.
I also set out to handle class generation for the GUI
- Even though its clear that the main objective is to have this framework
well integrated in Qgis, it would be nice if it could be accessed without
running Qgis, at least for the back end part. Being able to access it
through a standard Python shell would be very usefull. I think it converges
On Fri, Apr 29, 2011 at 7:31 AM, Julien Malik julien.ma...@c-s.fr wrote:
Hi Martin !
The point is actually not to provide every possible parameter type in
the framework. IMO we should have a base parameter type with several
common types such as integer, string, vector layer, enumeration. Such
Well, you're not alone :)
Paolo is right!
Yes, I have noted there is a great deal of interest in this project!
Thanks for all the support,
Camilo
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
Thanks, Martin, for your well-thought-out response!
https://github.com/polymeris/qgis/wiki/QGIS-Processing-Framework
Would that more or less fit what you have in mind? Please comment/criticize.
The discussion was not going into implementation details, we were
mostly collecting the ideas how
On Wed, Apr 27, 2011 at 4:58 PM, Mayeul Kauffmann
mayeul.kauffm...@free.fr wrote:
Le mercredi 27 avril 2011 à 20:46 +0200, Paolo Cavallini a écrit :
Il giorno mer, 27/04/2011 alle 12.00 -0400, Camilo Polymeris ha
scritto:
Good point. SAGA, as far as I know, does not provide information
Best of luck to all who weren't accepted this year... there are many
Summers of Code to come -- but you can take the opportunity to get
involved in your projects-of-choice NOW-- I wouldn't be surprised if
some of you delivered better code and more contributions to QGIS than
those of us who were
It's not very elegant, but you could use QObject.sender(), see
http://doc.qt.nokia.com/4.7/qobject.html#sender
Regards,
Camilo
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer
On Wed, Apr 13, 2011 at 5:21 AM, G. Allegri gioha...@gmail.com wrote:
As soon as I find a minute for it, I will publish my experience on a wiki
page (where? I will see...).
Add it to the same wiki at github if you want.
On an unrelated note: Do you know if a particular python version is
Hi Camilo.
Could you please start a wiki page, accumulating the info so far?
Thanks.
Sure.
I had stated to keep links (to APIs, forum threads, etc.) and some notes here:
http://github.com/polymeris/qgis/wiki
I can move some of that to the QGIS wiki and add the info I find in
the threads. Is
But I don’t any auto-completion for the QGIS libraries. Wing doc explain to
use a *.pi file but I can’t translate core.pyd or gui.pyd to core.pi or
gui.pi …
pi files or Python Interface files describe the interface of binary
only python modules.
Wing ships with a script that extracts pi
Just for the record, under linux I had to pass the following options
to the configure script:
--enable-python
--enable-unicode
The first is to build the python modules (could be done by hand, too).
The second forces saga to use unicode, so it matches debian's wx
packages.
No problems otherwise,
Hello Rashad,
I don't wish to be rude, and your proposal does sound interesting.
Still, I find it strange that you copied such a great part of my own
proposal [1] verbatim, including the project plan: list of
deliverables and timeline (down to the dates).
I understand you may be under time
On Thu, Apr 7, 2011 at 11:38 PM, Mohammed Rashad
mohammedrasha...@gmail.com wrote:
sorry sorry sorry
I am using net from outside so to do not miss deadline i did so
I am at home now and changing the timeline
sorry again
No problem. I understand -- and as I said, your project seems very
I would try any of the following:
self.dlg.comboBoxNew = QtGui.QComboBox()
- set the Combobox's parent to the dialog or layout:
self.dlg.comboBoxNew = QtGui.QComboBox(self.dlg)
self.dlg.comboBoxNew.setObjectName(comboBox)
GUI: Any ideas? So far I think I'll just clone SAGA's.
I think it would be good if you could follow either the GdalTools or the
GRASS plugins approach.
Here is a screenshot of what it looks right now:
www.udec.cl/~cpolymeris/QGIS_Screenshot_04032011.png
You think that's a good direction?
On Sun, Apr 3, 2011 at 5:02 AM, G. Allegri gioha...@gmail.com wrote:
I was out yesterday, and I'm glad to see how things are going on!
Camilo, I've browsed your repo but I can't find the parts where saga_cmd is
being called... I suppose I missed some files.
You are right.. seems I forgot to
Anyway, we need to build the single GUI module on the fly, and that is
what I'm trying to do. In my mind:
- mainteiner side:
generate a xml file from saga_apy python called with all modules and related
parameters;
- user side:
only use plugin with saga installed, without need to
the plugin is in code.google (http://code.google.com/p/qgis-saga-plugin/).
This is what I have done so far:
https://github.com/polymeris/qgis/tree/master/python/plugins/sagamodules
Same as you, but basically I am trying to use only saga_cmd to keep
things simple.
The C++ version of the plugin I
What I don't understand is: we'd have the same problems using python.
There are, as far as I know, no Python-saga packages.
Debian's libsaga[2], for instance, does *not* include python bindings.
That means we'd have to compile ship the python-saga binding
ourselves, anyway. Or am I missing
Sorry to insist, but I think this is not a good choice. We already had
experiance with several non-core C++ plugins, some of them extremely
useful, and all of them are essentially unavailable to users. On the other
hand, it is probably unfeasible to add a dependency on SAGA.
What I don't
What about: https://github.com/qgis/qgis
Is that repo official/maintained? It was updated a month ago. I forked
from that, should I rather switch to Francesco's, then?
Regards
Camilo
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
Hello, Paolo, and thanks for your swift answer.
Please do: I think this is quite interesting. Please note that Gianluca
Massei has started some work on this, so he may be able to start
quicker.
Has Gianluca published his code? I'd like to see his approach and
maybe work together. Mine is at
On Wed, Mar 30, 2011 at 9:59 AM, G. Allegri gioha...@gmail.com wrote:
Hi Camilo.
I agree with your approach. I already expressed it in past emails on this
topic.
Even if working at low levels requires some more overhead (cross platform
builds and support), it would bring a higher level of
Hello everyone,
I am considering implementing this idea:
http://www.qgis.org/wiki/SAGA_Toolbox_for_QGIS
I use SAGA often and would like to see a modern interface to it. I
have no experience with the QGIS code, though. The last few days I
have been coding a little, just to get a feeling of how
66 matches
Mail list logo
