Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[need-docs] reorganize the new spatialite layer dialog #5824

Merged
merged 1 commit into from Dec 8, 2017

Conversation

nirvn
Copy link
Contributor

@nirvn nirvn commented Dec 8, 2017

Description

The PR harmonizes the create spatialite layer dialog to match recent improvements done to the create geopackage layer dialog (and others).

Before vs. PR:
screenshot from 2017-12-08 11-51-38

Checklist

Reviewing is a process done by project maintainers, mostly on a volunteer basis. We try to keep the overhead as small as possible and appreciate if you help us to do so by completing the following items. Feel free to ask in a comment if you have troubles with any of them.

  • Commit messages are descriptive and explain the rationale for changes
  • Commits which fix bugs include fixes #11111 in the commit message next to the description
  • Commits which add new features are tagged with [FEATURE] in the commit message
  • Commits which change the UI or existing user workflows are tagged with [needs-docs] in the commit message and containt sufficient information in the commit message to be documented
  • I have read the QGIS Coding Standards and this PR complies with them
  • This PR passes all existing unit tests (test results will be reported by travis-ci after opening this PR)
  • New unit tests have been added for core changes
  • I have run the scripts/prepare-commit.sh script before each commit

@nirvn
Copy link
Contributor Author

nirvn commented Dec 8, 2017

@m-kuhn , BTW, while working on this, I noticed the autoincrementing fid field isn't marked as Autogenerated in the new feature attributes dialog that pops up. It's forcing the users to enter a value there, not the best UX.

@nyalldawson
Copy link
Collaborator

Nice work!

There's another ui inconsistency here... I think this dialog is the only place the proper crs selector combobox widget isn't used in QGIS. Is that straightforward to swap?

@nirvn
Copy link
Contributor Author

nirvn commented Dec 8, 2017

@nyalldawson , can't be done unless there's a way to call setOgcWmsCrsFilter() through the projection selection widget.

@m-kuhn
Copy link
Member

m-kuhn commented Dec 8, 2017

That's a spatialite issue. I think @elpaso recently looked into this.

@nirvn
Copy link
Contributor Author

nirvn commented Dec 8, 2017

@m-kuhn , cool.

While refreshing the dialog, I noticed our spatialite provider driver doesn't support curved geometries too, while GDAL 2.x does support such geometry for spatialite datasets.

@nirvn nirvn merged commit 11c1f3a into qgis:master Dec 8, 2017
@nyalldawson
Copy link
Collaborator

While refreshing the dialog, I noticed our spatialite provider driver doesn't support curved geometries too, while GDAL 2.x does support such geometry for spatialite datasets.

Yet another compelling reason to kick it to the kerb and just always use GDAL for this...

@m-kuhn
Copy link
Member

m-kuhn commented Dec 8, 2017

Yet another compelling reason to kick it to the kerb and just always use GDAL for this...

Major question for me here: if we create an aggregate expression compiler, can we

  • detect which tables come from the same DB (I guess so)
  • JOIN other tables from the DB within a request

CC @rouault

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants