Hi Matthias (and others),
I read your paper and I like the idea of the dual view because currently
it is not possible to open the attribute editor from the table. On the
other hand I am not convinced of the filter/selection proposal. IMHO one
of the strengths when using GIS data is the unity of geometry and
attribute data. Currently selecting a feature in the map also selects
its attributes in the corresponding table and vice versa.
examples:
1) Select in map and investigate attributes: If a filter was applied the
data might not be visible in the table without clicking "selection to
filter".
2) filter logical in table and investigate these features in the map:
You would need an additional "filter to selection" button to handle this.
3) field calculator: will it update the selected or the filtered datasets?
I think the whole concept will confuse average users. I would favour to
keep the well established solution of features being selected no matter
where (table or map) the selection was performed.
my 2 cents
Bernhard
Am 09.01.2013 12:43, schrieb Nathan Woodrow:
Hey Matthias,
Interesting idea. Look forward to seeing the development of this feature.
Two questions before I ask any others.
- Does this change the behaviour of the identify tool? What happens when
I am in edit mode and click on a feature? Same as it currently is? If we
could add multi edit, multi select to the identify tool that would be neat.
- How would you handle custom UI forms? Just embed them in the split view.
Overall I think it's a great idea and would greatly welcome a feature like
this.
- Nathan
On Wed, Jan 9, 2013 at 6:44 PM, Matthias Kuhn<matthias.k...@gmx.ch> wrote:
Dear list,
Denis, Andreas and I have been working on a proposal concerning the
attribute table and attribute editor.
We are convinced that it is a good idea to combine these two into a single
window and add/change some functionality.
There is a document [1] online which describes our ideas and contains some
mockups. We will start working on this soon and would like to encourage
everybody to read and comment on our ideas.
Regards,
Matthias
[1]: https://docs.google.com/**document/d/**1dL965ky4OoyeN9fEcqP9SWHVeQxTj
**1IFkBrEXTUBZuY/edit?pli=1#**heading=h.seeehmi30hq0<https://docs.google.com/document/d/1dL965ky4OoyeN9fEcqP9SWHVeQxTj1IFkBrEXTUBZuY/edit?pli=1#heading=h.seeehmi30hq0>
______________________________**_________________
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/**mailman/listinfo/qgis-**developer<http://lists.osgeo.org/mailman/listinfo/qgis-developer>
_______________________________________________
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer
