Hi all,
Le 25/09/2014 11:10, Matthias Kuhn a écrit :
Aren't there two different possibilities in which such layers can be
used:
* As a scratch layer for the user, which he may want to save in the end
* As a means for plugins to show information to the user
One of the main reason memory
Hi Nathan, all,
Le jeudi 25 septembre 2014 09:56:58, Nathan Woodrow a écrit :
[..]
IMO we could in the future use sqlite in memory datastore for the memory
provider which gives us a lot more options and range.
Hugo is currently writing a QEP to exactly do that and as well address some
issues
saved.
Cheers
Chrsi
From: Matthias Kuhn [matthias.k...@gmx.ch]
Sent: 25 September 2014 19:19
To: Nyall Dawson
Cc: qgis-developer
Subject: Re: [Qgis-developer] Memory Layers - some proposals
Hi,
Please excuse my ignorance, but
Why would you want a memory
What about a icon in the legend to note that it it's not going to be saved?
- Nathan
On Thu, Sep 25, 2014 at 3:57 PM, Mathieu Pellerin nirvn.a...@gmail.com
wrote:
Thoughts:
- I don't think warning should be occurring when creating a memory layer
(that is when pasting as new layer, when
On 25/09/2014 4:03 pm, Nathan Woodrow madman...@gmail.com wrote:
What about a icon in the legend to note that it it's not going to be
saved?
I like that idea - I'd imagine if memory/scratch layers always displayed
the RAM icon in the legend and not the layer symbol then it would be a
permanent
Possibly although that'd clutter that space. Renaming Memory Layers to
Temporary Layers would also give a good clue.
That said, I must say I quite enjoy using the memory layer saver, I'd be
sad to see this function not making it into core.
Martin raised an important issue re format. What about
On 25/09/2014 4:27 pm, Mathieu Pellerin nirvn.a...@gmail.com wrote:
Possibly although that'd clutter that space.
Not really- it could be handled in the same way as the editing icon is at
the moment. That doesn't take up any extra room as it replaces the style
swatch.
That said, I must say I
Personally I like the memory layer and use it frequently.
The icon idea sounds good to me. Ideally it could be a RAM icon combined
with the type of geometry (Point, Line, Polygon).
I also like the idea of having the memory layer as a core feature - but
then there should be a user-friendly way to
I guess the main issue with replacing the style swatch is we loose that for
a ram icon that will be there all the time so you can't see the style set
on the layer.
Personally I do prefer the name Temporary rather then Memory.
- Nathan
On Thu, Sep 25, 2014 at 4:38 PM, Nyall Dawson
As a name, I like Scratch layer or Temporary layer. I see that
people can confuse Memory with permant storage.
Andreas
Am 25.09.2014 06:41, schrieb Nathan Woodrow:
I guess the main issue with replacing the style swatch is we loose that
for a ram icon that will be there all the time so you
Nyall, I don't think there's a compatibility issue with memory layers.
Those are by their nature QGIS-dependant data, the same way ArcGIS can't
simply open a .qgs project file, a .qml layer properties file, etc.
One of the nice feature of memory layers (and its sister plugin memory
layer saver)
On 25/09/2014 4:51 pm, Mathieu Pellerin nirvn.a...@gmail.com wrote:
Re Temporary Layers, I find it slightly better than Scratch Layer for non
native English speakers (i.e. more to the point in simple English :) ).
What happens when we port the memory layer saver to core though? Temporary
I agree.
It seem me a silly question.
If an user choose a memory layer it know that is a memory layer
:)
So it is not a permanent dataset.
I like the memory layer because they as really useful for temporary
elaborations and quickly tests.
lso another question is.
If an user choose the memory
On Thu, Sep 25, 2014 at 09:02:07AM +0700, Mathieu Pellerin wrote:
Regarding the saving aspect of it, IMO it needs to be worked out. I've had
a couple of users over here already reporting data loss with the
following scenario:
1. Open his/her project
2. Copies one polygon from a large dataset
Hey all,
I think the best course of action here is to hold off until after 2.6 so we
can review this thing as a whole solution rather then rushing it in last
minute and then moving the target later.
IMO we could in the future use sqlite in memory datastore for the memory
provider which gives us
On Thu, Sep 25, 2014 at 04:03:04PM +1000, Nathan Woodrow wrote:
What about a icon in the legend to note that it it's not going to be saved?
I like the icon idea, but would still additionally have a warning
at save time.
I see those temporary layers like drafts. That is, something you do
not
Aren't there two different possibilities in which such layers can be used:
* As a scratch layer for the user, which he may want to save in the end
* As a means for plugins to show information to the user
In the first scenario, the user may actually want to save the
information because he
Hi all,
The recent discussion around memory layers in another thread has started me
thinking about the best way to expose them more readily to users.
As such, I've opened a pull request which ports Borys Jurgiel's New Memory
Layer plugin to core (PR #1591). Hopefully this can be merged for 2.6.
Hi Nyall
On Thu, Sep 25, 2014 at 3:31 AM, Nyall Dawson nyall.daw...@gmail.com wrote:
Hi all,
The recent discussion around memory layers in another thread has started me
thinking about the best way to expose them more readily to users.
As such, I've opened a pull request which ports Borys
Regarding the saving aspect of it, IMO it needs to be worked out. I've had
a couple of users over here already reporting data loss with the
following scenario:
1. Open his/her project
2. Copies one polygon from a large dataset and pastes is as a new memory
layer (very useful feature introduced in
On 25.09.2014 04:02, Mathieu Pellerin wrote:
Regarding the saving aspect of it, IMO it needs to be worked out. I've
had a couple of users over here already reporting data loss with the
following scenario:
1. Open his/her project
2. Copies one polygon from a large dataset and pastes is as a
Thoughts:
- I don't think warning should be occurring when creating a memory layer
(that is when pasting as new layer, when adding the result of a processing
algorithm as memory layer, or creating a blank memory layer)
- I don't think the user should be able to disable the warning message
(which
22 matches
Mail list logo
