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
[GEOT-7109] Swt Module review and update #3921
Conversation
…iles due to wrong formatting
@IanMayo , for your info. This is the PR. I am sorry it took that long, but after the fixes I never got to do the docs until today. Which resulted in merge conflicts. Should be all green now. |
Thanks @moovida , you've done a good job. I'm surprised at the volume of SWT changes - but I guess you've done some general tidying/refactoring too, right? Is it an option to distribute the sample shapefile with the tutorial? Loading/displaying the coastlines does give an "acknowledgement" that data has been loaded/rendered, IMHO. |
Hi @IanMayo , yes there have been a couple of quick refactorings to cleanup and give the possibility to handle actions. I am not sure how you mean to distribute a shp sample? You would like to be able to run the example and have a shp directly loaded? Or a sample to load with the "open shapefile" option? |
Hello @moovida , for the tutorial element of the PR, it would seem useful to finish with some loaded data - since this demonstrates:
I see there is already a shapefile distributed in |
Hi @IanMayo , I like the idea. We could also show how a "load default shp" action is added:
Which would be nice for the user to load something right away. Or, we could just show how to load a shp at startup. My main issue is that a user that is trying this is not forced to be doing this from the geotools source. In fact I imagine most people doing this from maven geotools. Therefore a shp from the repo might not be an option. Should we just tell in the tutorial to place the path to an existing shapefile on the user's disk? |
oops, of course. Just in case the "student" doesn't work with shapefiles (and may not have one handy), but still wants to complete the tutorial. I guess we could provide a URL for a shapefile that we can expect to be persistent - such as: https://www.naturalearthdata.com/downloads/110m-physical-vectors/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please run the formatting tools on the code and the pom file; specifically the pom file was formatted according to the project rules, but that is destroyed with this PR.
You can use mvn clean install -T1.1C -f modules/unsupported/swt/pom.xml
Thanks a lot for this. |
@IanMayo, let me know what you think. I can make it even more tutorial-verbose, but I think this might be out of scope. |
The new version, with OSM & Shapefiles is great - thanks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Appreciate both the fixes/updates and the more comprehensive tutorial.
Added labels for automatic backport (I think you might want to backport this right?). |
Bot ready, squash merging and checking if any backport PR is automatically generated. |
The backport to
stderr
stdout
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-27.x 27.x
# Navigate to the new working tree
cd .worktrees/backport-27.x
# Create a new branch
git switch --create backport-3921-to-27.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick 79d16038bee6129ff05c2241e0c48b7fb81d0957,c2a5c2e8d344cc06c221d16494738c8fc8e9aed9,30e6a273475cbe42cc943c8d48a48f9703455dcf,784b32c08a5a3b02b6c42a3fa03dccbf31c4fd77,90ca7bf9646f5cdc9896895eb92ff6bc46b28517,4ce2d1a2f773411096134ff62ea5e4b145b1694d,1f0307e4e34c5441fcc24e7e63376e15b7c218fe,04cb51b513f862dbf95c02fd369017a6d5008757
# Push it to GitHub
git push --set-upstream origin backport-3921-to-27.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-27.x Then, create a pull request where the |
The backport to
stderr
stdout
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-26.x 26.x
# Navigate to the new working tree
cd .worktrees/backport-26.x
# Create a new branch
git switch --create backport-3921-to-26.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick 79d16038bee6129ff05c2241e0c48b7fb81d0957,c2a5c2e8d344cc06c221d16494738c8fc8e9aed9,30e6a273475cbe42cc943c8d48a48f9703455dcf,784b32c08a5a3b02b6c42a3fa03dccbf31c4fd77,90ca7bf9646f5cdc9896895eb92ff6bc46b28517,4ce2d1a2f773411096134ff62ea5e4b145b1694d,1f0307e4e34c5441fcc24e7e63376e15b7c218fe,04cb51b513f862dbf95c02fd369017a6d5008757
# Push it to GitHub
git push --set-upstream origin backport-3921-to-26.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-26.x Then, create a pull request where the |
Well it run, but found conflicts... looks like a backport will have to be done manually, if you plan to do one. |
Hi @aaime , thank you. |
Correct, it should not.... try to do a cherry-pick and find out what is the source of the conflict :-D |
Well, I tried the manual backport and fixed the small issues it had for 26.x Am I supposed to do this?
even if along the way it took the original geotools repo as upstream? It is the first time I try to do a backport. |
Just a push on your fork, no need to set the upstream there, you can set it while opening the PR. |
In my case origin is my repo, so the push should be there right (the set-upstream should take care of it in the push?)? Yes, 27 is next, if I am able to close 26. |
Hello @moovida No, the backport won't bring value to me. If it just worked, then that would be fine. If it's troublesome then my needs are met with the |
Ok, I was just trying to go against the wrong branch. In fact it should work now. Were really small fixes. The 2 PR are now open for 26 and 27. |
This PR upgrades the SWT module as per discussions had in the mailinglist.
This basically upgrades swt libraries, updates to latest gt api and fixes the bugs reported in JIRA.
After some discussion, it has been decided to remove the RCP related part, since it is too complex to maintain (it would need an existing RCP project in a different repository). Also in the docs these parts were removed.
Checklist
main
branch (backports managed later; ignore for branch specific issues).