Il 20/10/2012 02:16, Nathan Woodrow ha scritto:
> I'm really not a big fan of those back and forward buttons. My idea
> is to have a save button with three options:
>
> Save as
> - Application favourite
> - Project favourite
> - File
sounds good to me, thanks.
--
Paolo Cavallini - Faunalia
www
Hi Nathan,
On Fri, Oct 19, 2012 at 6:16 PM, Nathan Woodrow wrote:
> Saving with the layer isn't really that complicated as we already do
> it for the qml files so the code is already all there just needs to be
> tweaked for expressions. Although I do see project based and
> application wide expr
How about saving expressions in a "Clipbook"? An expression can be pasted
into a "Clipbook" which would also bring up a dialog to enter a name for
the expression. Several "Clipbooks" can be created in order to organize
these saved expressions. This would be handy in the Python console too.
Btw,
Saving with the layer isn't really that complicated as we already do
it for the qml files so the code is already all there just needs to be
tweaked for expressions. Although I do see project based and
application wide expressions to be of more use then per-layer.
I'm really not a big fan of those
I think you miss understand what is meant by saved expressions. It
would only be the expression text that is saved in the project file
with maybe a name:
name : expression
name : expression
name : expression
when the expression builder is open we just look in the project and
read in the expressi
I would liek saving expressions in file and a directory of my own choosing
would be ideal. At least that is what ArcGIS had (As far as version 9.3,
that I have used in the past.)
I would ask for simplicity and ease of use. Why make the project file
bloated and prone to corruption by adding field c
I agree with Alister that saving expressions for every layer seems
overly complex.
Maybe we could just have an interface similar to Spatialite GUI where
there are forward/backwards buttons besides the SQL input area. They
allow to go back in command history.
Best wishes,
Anita
On Fri, Oct 19, 2
Hi guys,
Personally I think saving expressions for every layer is unnecessarily
complicated. Have you thought of just having a drop-down list of recently used
expressions, and the ability to "pin" your favourite expressions to the list?
Do people really need expressions to be saved alongside t
Let me see what I can come up with after my exams are finished in a
week.
Sent from some fancy phone looking thingo
From: Paolo Cavallini
Sent: 19/10/2012 4:29 PM
To: Andreas Neumann
Cc: Nathan Woodrow; qgis-developer
Subject: Re: [Qgis-developer] Saving expressions
Il 19/10/2012 08:21, Andreas
Il 19/10/2012 08:28, Nathan Woodrow ha scritto:
> We can always have a save button that the user can pick to save a
> Application based expression (saved in the QGIS settings), or saved in
> the project file. I can see use cases for both.
>
Yes, several slightly different usages.
Thanks for thought
Il 19/10/2012 08:21, Andreas Neumann ha scritto:
>
> What do you expect from the loading? Automatic application to the
> field calculator (sounds scary to me), or just the ability to choose
> from past expressions?
I meant the latter.
>
> To me the expressions do not have a natural 1:1 match to a l
Subject: Re: [Qgis-developer] Saving expressions
Hi Paolo,
What do you expect from the loading? Automatic application to the field
calculator (sounds scary to me), or just the ability to choose from past
expressions?
If the latter, then maybe a central expression storage (per user) would
make
Hi,
I could imagine having several expressions for one layer (depending on
the field I want to do calculations on) so autoload needs to depend on
the layer and the field. On the other hand I could imagine having an
area field in many layers which I want to update with the geometry's
area. So
Hi Paolo,
What do you expect from the loading? Automatic application to the field
calculator (sounds scary to me), or just the ability to choose from past
expressions?
If the latter, then maybe a central expression storage (per user) would
make more sense than a per layer expression store. B
Il 19/10/2012 07:51, Andreas Neumann ha scritto:
> For me personally, copy/paste works fine. No need for load and save.
>
> I do not fully understand the use case for autoloading (association
> with a layer). Can you explain why this is desirable? Do you really
> always want the same expression in
For me personally, copy/paste works fine. No need for load and save.
I do not fully understand the use case for autoloading (association with a
layer). Can you explain why this is desirable? Do you really always want the
same expression in all projects for one particular layer?
In my experience
Il 19/10/2012 00:01, Nathan Woodrow ha scritto:
> Hey Paolo,
>
> Yes I have thought about this, just never got the time to flesh it out.
> What would peoples choice be for saving expressions. I have thought
> about the last 10 used but having them per layer could be handy to, or
> maybe both.
To me
: Paolo Cavallini
Sent: 18/10/2012 2:32 AM
To: qgis-developer
Subject: [Qgis-developer] Saving expressions
Hi all.
Currently we can use a variety of expressions in field calculator.
UNfortunately, they cannot be saved (if not copypasting as text). It
seems feasible and reasonable to save them as an XML
Hi all.
Currently we can use a variety of expressions in field calculator.
UNfortunately, they cannot be saved (if not copypasting as text). It
seems feasible and reasonable to save them as an XML, so we can reload
it. If saved with the same name and in the same dir as the original
file, they could
19 matches
Mail list logo
