On Sat, Nov 9, 2013 at 10:22 AM, maaza mekuria wrote:
> I am sorry that people are not encouraging the use of C++ for programming.
> I think this is not helpful at all.
>
There are many reasons to skip Pyhton infavor of C++. In my experience
> Python is very slow for real computationally intensiv
Hi Maaza, I think that for a plugin python makes much more sense due to the
easier distribution. I developed plugins in both c++ and python and I must
say that python was much faster to develop also.
I m not saying c++ is bad, on the contrary, i like its structured and
robust nature, I m just makin
Dear Nathan and fellow QGIS Users/Developers:
I am sorry that people are not encouraging the use of C++ for programming. I
think this is not helpful at all. There are many reasons to skip Pyhton infavor
of C++. In my experience Python is very slow for real computationally intensive
work. Also Q
Hi Regis,
Do you also think that this does not happen (at least as often) with QGIS 1.8?
Best regards,
Pedro
- Mensagem original -
> DE: Régis Haubourg
>
> Confirmed for me yesterday! A commit process stays idle in database server. I
> was blaming antivirus at start, but it seems r
Confirmed for me yesterday! A commit process stays idle in database server. I
was blaming antivirus at start, but it seems related to the number of commit
done in an edit session..
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/QGIS-2-becomes-slow-and-freezes-when-editing-
Hi,
In the recent times it has happened to me a strange thing, and I do not know
what is the source, it may be that you have already identified something.
When working with Postgis layers in QGIS, every time I "save" changes of an
editing layer, I notice that the recording process is slower, un
the problem was due to a missing dll in GRASS GIS package
See http://lists.osgeo.org/pipermail/grass-dev/2013-November/066251.html
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/r-profile-in-QGIS-2-0-crashes-without-any-message-tp5087787p5088266.html
Sent from the Quant
This discussion reminds me of a discussion in the Gnome team not long ago.
I think QGis developers might be helped with this:
http://www.reviewboard.org/
All the best,
Sjoerd
On 11/08/13 17:10, Werner Macho wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Paolo!
Thats exactly why I s
Hi Jürgen
Is that really significant? I suppose using the same connection as syncDb()
would help (just because it does it's thing in a transaction).
That was it, I moved everything into a transaction and it is super fast now.
Who's bad idea was it to call that thing tr()? ;) transformati
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Paolo!
Thats exactly why I suggested a monthly IRC meeting with the developes
that have time ..
Discuss .. Pull .. or just assign the code to the developer that is
"responsible" for that part..
I mean .. easy code that I cann fully read and unders
Hi list
I don't know it this is related to the recent processing upgrade, but I
cannot get plugins that add themselves as processing providers to get their
geoalgorithms loaded by default when I start QGIS.
This is hapenning with a custom plugin that I am writing, but I have
noticed it happening
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 08/11/2013 10:50, Werner Macho ha scritto:
> Following the words of Richard ..
Richard, Werner: this is a long standing problem. We have tried to deal with
it, with
limited success. We do not want to spoil our code contributors, but on the
other
On Fri, Nov 08, 2013 at 09:05:26AM -0200, George Silva wrote:
> Hello Sandro.
>
> I dont think this is a GEOS bug. I was following the various discussions on
> this bug/unexpected behavior.
>
> On one of them, in discussion with Marco, you said that it might be a
> problem with GEOSDifference. An
Compared to C++, Python is pretty easy to pick up. There are some really
good Python videos and after you watch a few of them (or even just one) I
would say you would feel comfortable in it. Because the PyQt and Qt C++
APIs are almost the same in terms of porting the code it almost comes right
ov
Hello Sandro.
I dont think this is a GEOS bug. I was following the various discussions on
this bug/unexpected behavior.
On one of them, in discussion with Marco, you said that it might be a
problem with GEOSDifference. And after that theres our chat in IRC, which
seems to fit the problem.
We can
Hi Paolo,
yes, our company has to come to a strategic decision in the next time. And
I'm not sure what to suggest. I don't know python but i think i need much
time to port ca. 3000 lines existing code, otherwise in future it should
grow up much more. Besides I'm spoiled of the IDE of VS, i nee
Following the words of Richard ..
Maybe we could just meet on IRC one evening a month and discuss the
open pull requests and probably merge them if possible ..
Like every second thursday in a month or so?
Would that be possible?
regards
Werner
On Fri, Nov 8, 2013 at 11:25 AM, Richard Duivenvoo
Hi George,
it's not clear to me from the QGIS tickets that there is a problem in GEOS.
Can you come up with a clear description of what you think is a GEOS bug ?
--strk;
On Thu, Nov 07, 2013 at 11:09:33AM -0200, George Silva wrote:
> Hello everyone,
>
> We have an important QGis digitizing issue
Hi Devs,
while adding a minor pull request, I saw that we have 30 open pull requests.
While not able to judge them, some of them look like feasable to pull.
Maybe I'm wrong, and they are all nasty ones, but then (as a community)
I think we should at least add a comment to them, telling the reque
On Thu, Nov 7, 2013 at 6:26 PM, George Silva wrote:
> QGis does the explicit noding of the first adjancent feature, but the
> results are inconsistent.
>
> Sometimes it works, sometimes it doesnt. I've tried many things to see if I
> could find a reproducible series of steps, but without success.
20 matches
Mail list logo
