On Sat, Oct 27, 2012 at 10:29 PM, Tim Sutton wrote:
> By the way, what is the URI for your branch / repo - is it in a usable
> state for others to play with?
Tim, my branch is available here [1], but I haven't updated it
recently because I have been modifying QgsFeature attributes from a
map to a
Hi
On Sat, Oct 27, 2012 at 10:28 PM, Tim Sutton wrote:
> Hi
>
> On Sat, Oct 27, 2012 at 9:45 PM, Martin Dobias wrote:
>> On Sat, Oct 27, 2012 at 7:37 PM, Tim Sutton wrote:
>
> while myProvider.nextFeature(myFeature): # or equivalent in new api
> myGeometry = myFeature.g
Hi
On Sat, Oct 27, 2012 at 9:45 PM, Martin Dobias wrote:
> On Sat, Oct 27, 2012 at 7:37 PM, Tim Sutton wrote:
while myProvider.nextFeature(myFeature): # or equivalent in new api
myGeometry = myFeature.geometry()
myFooValue = myFeature['foo']
On Sat, Oct 27, 2012 at 7:37 PM, Tim Sutton wrote:
>>>
>>> while myProvider.nextFeature(myFeature): # or equivalent in new api
>>> myGeometry = myFeature.geometry()
>>> myFooValue = myFeature['foo']
>>> do stuff .
>>
>> Good news, that's on the branch already
On Sat, Oct 27, 2012 at 2:46 PM, Matthias Kuhn wrote:
>
> Sounds like something worth considering.
> Something else I have been thinking of and what would increase
> performance pretty good in some situations would be to be able to select
> by an expression:
>
> myFeatureSet = provider.select( Qgs
Hi
On Sat, Oct 27, 2012 at 11:16 AM, Sandro Santilli wrote:
> On Sat, Oct 27, 2012 at 01:41:49AM +0200, Tim Sutton wrote:
>
>> * One of the major limitations I and the many people that contact me
>> about QGIS experience is lack of performance. Just yesterday I got an
>> email from someone in Sud
Hi Martin
On Sat, Oct 27, 2012 at 12:08 PM, Martin Dobias wrote:
> Hi Tim
>
> On Sat, Oct 27, 2012 at 1:41 AM, Tim Sutton wrote:
>> In terms of the release roadmap for 2.0 the following
>> items were discussed in the hackfest in Essen as being the key
>> features we would hold the release for:
>
Thanks, that did the trick. I can see that building the full QGIS would
make sense though, so I'll get my build environment set up to do that. For
now it's good to know how to just compile sextante though.
Thanks,
Rudi
On Sat, Oct 27, 2012 at 5:21 PM, Alexander Bruy wrote:
> As Victor said, you
As Victor said, you only need to compile resource file and some dialogs
(currently only About dialog). Just run commands
pyrcc4 -o /path/to/sextante/resources_rc.py /path/to/sextante/resources.qrc
pyuic4 -o /path/to/sextante/about/ui_aboutdialogbase.py
/path/to/sextante/about/aboutdialogbase.ui
Y
You do not actually have to build SEXTANTE, just a couple of GUI files
(the about dialog and a resources file). I guess Alex can give you
better advise in this, since he introduced that changed. Until that, I
was doing the GUI files directly without using the pyQt tools (not the
optimal way, I gues
Okay, I see I'll have to figure out CMake... Is there an easy way to build
just the sextante plugin, or do I have to build the whole QGIS system?
On Sat, Oct 27, 2012 at 4:04 PM, Rudi von Staden wrote:
>
> On Sat, Oct 27, 2012 at 4:00 PM, Rudi von Staden wrote:
>
>> I have cloned the GitHub rep
Sorry, accidentally hit the send button too early.
On Sat, Oct 27, 2012 at 4:00 PM, Rudi von Staden wrote:
> I have cloned the GitHub repo, and have symbolically linked the
> ~/.qgis/python/plugins/sextante directory to
> Quantum-GIS/python/plugins/sextante.
>
> When I load QGIS, it does give me
I have cloned the GitHub repo, and have symbolically linked the
~/.qgis/python/plugins/sextante directory to
Quantum-GIS/python/plugins/sextante.
When I load QGIS, it does give me an error, stemming from
sextante/about/AboutDialog.py; in particular, 'from ui_aboutdialogbase
import Ui_DlgAbout' pro
Il 27/10/2012 16:57, Alexander Bruy ha scritto:
> 2012/10/27 Paolo Cavallini :
>> BTW, could please somebody move the important plugins still missing in
>> the new repo?
> Where we can find this list of important plugins?
>
good questions. I think for those on the new repo, the downloads and
votes
On Thu, 2012-10-25 at 13:52 +0200, Martin Dobias wrote:
> Yes, with the current design only one thread (iterator) can read
> particular data at the same time.
>
Thank you for clarification.
In this case +1 from me for breaking the API.
Maybe most plugins can even be fixed with sed? And for othe
On Sat, 2012-10-27 at 11:16 +0200, Sandro Santilli wrote:
> On Sat, Oct 27, 2012 at 01:41:49AM +0200, Tim Sutton wrote:
>
> > * One of the major limitations I and the many people that contact me
> > about QGIS experience is lack of performance. Just yesterday I got an
> > email from someone in Sud
2012/10/27 Victor Olaya :
> I do not know if I will get a notification if there is a
> SEXTANTE-related pull request in the QGIS repo, but I guess that is a
> good idea. Opening a ticket in the SEXTANTE bug-tracker with the patch
> is also a good idea
AFAIK all devs get notifications about all pul
>> 1) As far as I can tell, active development is now happening on GitHub QGIS
>> core rather than svn; if I fork the QGIS repo, can I use just the sextante
>> plugin with old faithful QGIS 1.8.0, or could I run into conflicts?
>
> Yes, you can use SEXTANTE from core with older QGIS versions.
I co
2012/10/27 Rudi von Staden :
> 1) As far as I can tell, active development is now happening on GitHub QGIS
> core rather than svn; if I fork the QGIS repo, can I use just the sextante
> plugin with old faithful QGIS 1.8.0, or could I run into conflicts?
Yes, you can use SEXTANTE from core with old
Hi all,
There's quite a bit of activity on the Sextante plugin, and I'd like to
keep up with the latest developments. It seems things have changed recently
so I have a couple of questions about the best approach:
1) As far as I can tell, active development is now happening on GitHub QGIS
core rat
On Sat, Oct 27, 2012 at 11:16 AM, Sandro Santilli wrote:
> On Sat, Oct 27, 2012 at 01:41:49AM +0200, Tim Sutton wrote:
>
>> * One of the major limitations I and the many people that contact me
>> about QGIS experience is lack of performance. Just yesterday I got an
>> email from someone in Sudan t
Hi Tim
On Sat, Oct 27, 2012 at 1:41 AM, Tim Sutton wrote:
> In terms of the release roadmap for 2.0 the following
> items were discussed in the hackfest in Essen as being the key
> features we would hold the release for:
>
> 1) Raster overhaul
> 2) WMTS Support
> 3) Atlas integration for composer
On Sat, Oct 27, 2012 at 01:41:49AM +0200, Tim Sutton wrote:
> * One of the major limitations I and the many people that contact me
> about QGIS experience is lack of performance. Just yesterday I got an
> email from someone in Sudan trying to use QGIS to work with ~300 000
> point records and it t
2012/10/27 Paolo Cavallini :
> BTW, could please somebody move the important plugins still missing in
> the new repo?
Where we can find this list of important plugins?
--
Alexander Bruy
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
htt
24 matches
Mail list logo
