Having a specific memory storage have pros and cons that you explained very
well Chris.
From a user point of view, one drawback is that if something goes wrong in
memory layer loading whe project opens, or on memory layer save, data is
lost. So User will for sure ask for a "Add memory layer" provi
Am Mittwoch, 25. Juli 2012, 17.01:28 schrieb Vincent Picavet:
>
> +1 for having the Python version in a separate Git repository somewhere.
+1, with a preference for https://github.com/qgis as repo location. I promise
the first pull request within a week...
--
Pirmin Kalberer
Sourcepole - Lin
Hi Larry,
On 26.07.2012 03:23, Larry Shaffer wrote:
I will be documenting on the wiki a proposed process for taking QGIS's
many GUI components from their current state to a more cohesive,
adaptable, finished-looking, and HIG-compliant tool set for version
2.0. I welcome any and all input or help
Hi,
seems qgsAffine plugin [0] project created not as subproject
of "User plugins". Can anyone fix this?
[0] http://hub.qgis.org/projects/qgsaffine
--
Alexander Bruy
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org
On Thu, 2012-07-26 at 13:10 +0300, Alexander Bruy wrote:
> Hi,
>
> seems qgsAffine plugin [0] project created not as subproject
> of "User plugins". Can anyone fix this?
>
> [0] http://hub.qgis.org/projects/qgsaffine
fixed
___
Qgis-developer mailing
Hi all.
On current master, self packaged on Debian, I cannot find the OWS entry
in the browser. A colleague is seeing it on Windows. Is this a general
pattern (a bug), or is a local problem?
All the best.
--
Paolo Cavallini - Faunalia
www.faunalia.eu
Full contact details at www.faunalia.eu/pc
Nuo
Hi
On Thu, Jul 26, 2012 at 12:29 AM, Paolo Cavallini wrote:
> Il 26/07/2012 00:20, Tim Sutton ha scritto:
>> Hi All
>>
>> Good news, as it seems regular team recruitment is happening with new
>> talented developers joining our project! We now have 18 'core'
>> committers on the project as we can
Il 26/07/2012 13:53, Tim Sutton ha scritto:
>> /s/Guiseppe/Giuseppe
>
> Sorry about that!
>
no problem, I'm also used to Paulo, and a few other variants ;)
all the best, Tom.
--
Paolo Cavallini - Faunalia
www.faunalia.eu
Full contact details at www.faunalia.eu/pc
Nuovi corsi QGIS e PostGIS: http:
Hi,
In general I like the new icon set, because the icons look slicker and
clearer.
But I just noticed this inconsistency between the "Map Navigation"
toolbar and the print composer. The pan tool in the "Map Navigation"
consists of four arrows into all directions. In the print composer it is
one
Hi Matthias and Tim,
As I can see, switching off ML subscription during holidays is not a
good idea ;)
On 26.07.2012 14:10, Matthias Kuhn wrote:
But I just noticed this inconsistency between the "Map Navigation"
toolbar and the print composer. The pan tool in the "Map Navigation"
consists of
My answer was too fast...
On 26.07.2012 14:27, Robert Szczepanek wrote:
Hi Matthias and Tim,
On 26.07.2012 14:10, Matthias Kuhn wrote:
But I just noticed this inconsistency between the "Map Navigation"
toolbar and the print composer. The pan tool in the "Map Navigation"
consists of four arrows
I don't know much about the memory layer handling - but here are some thoughts:
I think Jürgen's idea makes a lot of sense: keep in-memory spatialite
database, and save/restore when the project is saved/opened. And the
user can export the layer to a preferred format if he/she wishes.
Perhaps this
We are designing the raster save as in a way that could be re-used
elsewhere, perhaps vector saving could follow the same route -
although not much (nothing) can be shared between the vector and
raster dialogs.
Etienne
On Thu, Jul 26, 2012 at 2:29 AM, Paolo Cavallini wrote:
> Il 26/07/2012 06:31
On Thu, Jul 26, 2012 at 3:14 AM, Marco Hugentobler
wrote:
> Hi Etienne
>
>
>> What I have done for the format options is make is a standalone
>> widget, and it is included in the file save as dialog and gdal
>> options, as well as in the gdaltools dialogs (overviews only for
>> illustration). Woul
Hi Robert,
I like the consistent look of your icon set. The results of Tim's poll
clearly show many wish to switch to your set right away [0].
Since QGIS is icon- and toolbar-heavy in overall look (in default
configuration), whatever you can do to improve the definitive visual
change from the old
Hi,
my opinion is somewhere between Larry's and Yve's..
GIS theme has two main drawbacks IMHO:
1. Global render of toolbars is a cold blue - gray, in opposite of all QGIS
relate support, that are colorfull (sites, GUI). It looks very old school
GIS to me.. My wife, who likes painting, and somet
Hi
On Thu, Jul 26, 2012 at 7:27 PM, Larry Shaffer wrote:
> Hi Robert,
>
> I like the consistent look of your icon set. The results of Tim's poll
> clearly show many wish to switch to your set right away [0].
>
> Since QGIS is icon- and toolbar-heavy in overall look (in default
> configuration), w
Hi all.
Now that there is much work on refactoring the raster classes, wouldn't
it be the right time to implement a series of colour ramps to be
applied, instead of having only the current ugly blue-red one, based on
equal intervals? The 1-band plugin is a very good guidance for this.
The current s
I was thinking about that, we could leverage the existing colorramps
for vectors.
We should probably refactor QgsVectorColorRampV2 as QgsColorRamp, and
if need be create 2 subclasses (vector, raster). We could probably
use existing dialogs pretty easily also, and do the same.
Unless there is a f
Il 26/07/2012 21:14, Etienne Tourigny ha scritto:
> I would colunteers to so this work - I just need a little guidance on
> overall implementation details.
>
That would be great, merci Etienne.
In this case, I think we should add several ramps that, although useful
for both, are really necessary fo
Hi Etienne,
> In this case, I think we should add several ramps that, although useful
> for both, are really necessary for raster (e.g. DTM). See 1-band plugin
> for a very nice set of ramps, and classification methods.
> From the user point of view, having the same colours available would be
> a
On Thu, Jul 26, 2012 at 4:25 PM, Giovanni Manghi
wrote:
> Hi Etienne,
>
>
>> In this case, I think we should add several ramps that, although useful
>> for both, are really necessary for raster (e.g. DTM). See 1-band plugin
>> for a very nice set of ramps, and classification methods.
>> From the u
Il 26/07/2012 21:29, Etienne Tourigny ha scritto:
> Is there anything in the vector color ramps that should NOT be
> available for raster color ramps?
I think they will not hurt, and often can be useful. Of course, if you
are going to implement >20 ramps, a classification/tagging/tree method
will b
Il 26/07/2012 21:29, Etienne Tourigny ha scritto:
> Is there anything in the vector color ramps that should NOT be
> available for raster color ramps?
Beware that many ramps have a meaning only when applied to absolute
values (e.g. DTM), not on a relative (0-100%) scale. This is true for
both, prob
Hi Even
Thanks for the suggestion and code examples - very helpful. I haven't followed
up on this yet partly because this has prompted me to look at other storage
formats for the data (something I'd been putting off).
If I understand the GML driver documentation properly then I would have to
m
Hi
On Thu, Jul 26, 2012 at 9:29 PM, Etienne Tourigny
wrote:
> On Thu, Jul 26, 2012 at 4:25 PM, Giovanni Manghi
> wrote:
>> Hi Etienne,
>>
>>
>>> In this case, I think we should add several ramps that, although useful
>>> for both, are really necessary for raster (e.g. DTM). See 1-band plugin
>>>
Le jeudi 26 juillet 2012 21:41:57, Chris Crook a écrit :
> Hi Even
>
> Thanks for the suggestion and code examples - very helpful. I haven't
> followed up on this yet partly because this has prompted me to look at
> other storage formats for the data (something I'd been putting off).
>
> If I und
Good points. I'm thinking perhaps the solution is to use Sqlite/spatialite
(don't get me wrong - I like and use spatialite a lot). But perhaps use the
python spatialite driver directly, rather than the QgsVectorFileWriter class as
I am currently doing, as I cannot see any OGR options for writi
On Thu, Jul 26, 2012 at 1:40 PM, Paolo Cavallini wrote:
> Il 26/07/2012 21:29, Etienne Tourigny ha scritto:
>> Is there anything in the vector color ramps that should NOT be
>> available for raster color ramps?
> Beware that many ramps have a meaning only when applied to absolute
> values (e.g. DT
Hi Even
Sorry .. lost wasn't quite correct. The point is that my code for saving some
users data and then reloading needs to take account of whether they have a
field called fid or not if I want the list of fields unchanged after saving and
reloading the data.
Either I have to record somewher
Hi Paolo
This is about saving the persisting the data in memory data provider layers,
which by default is discarded when the project is closed (although the layer
definition is in the project file, all the data is lost). It is not related to
fTools. It is specific to the memory data provider.
Le jeudi 26 juillet 2012 22:52:47, Chris Crook a écrit :
> Hi Even
>
> Sorry .. lost wasn't quite correct. The point is that my code for saving
> some users data and then reloading needs to take account of whether they
> have a field called fid or not if I want the list of fields unchanged
> afte
Hi,
I have created a draft roadmap for the GUI for 2.0. At this time it is
mostly focused on fixing problems, making components consistent and
adherence to HIG for the project [0].
http://hub.qgis.org/wiki/quantum-gis/GUI_roadmap_for_version_20
If you are interested in helping with this process,
33 matches
Mail list logo
