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

initial gitpod configuration #445

Merged
merged 1 commit into from
Nov 10, 2023
Merged

initial gitpod configuration #445

merged 1 commit into from
Nov 10, 2023

Conversation

GitMensch
Copy link
Contributor

  • setup and building, including dependency KDDockWidgets
  • x11 config allowing to preview the GUI in the browser

This enables easy direct work on Hotspot if you only have the browser around and removes the necessary setup for that.
Just start (wait a bit until that all is built) and work.

@GitMensch GitMensch marked this pull request as draft December 3, 2022 22:42
@GitMensch GitMensch force-pushed the gitpod branch 5 times, most recently from 4b6f73f to ae63a15 Compare December 3, 2022 23:33
@GitMensch GitMensch marked this pull request as ready for review December 3, 2022 23:34
@GitMensch GitMensch marked this pull request as draft December 3, 2022 23:48
@GitMensch
Copy link
Contributor Author

This actually worked out quite good. Apart from the initial config I've added a second commit with a README adjustment, allowing you to "click" on it and have a look what it does. This second commit can be amended or dropped completely.

@milianw what do you think?

@milianw
Copy link
Member

milianw commented Dec 4, 2022

can you explain when one would want to use that? can one open local files in the hotspot that is opened there? or is this meant to be used for development by people who don't want to have a local dev setup?

generally, I don't know anything about gitpod and have never used nor heard about it yet. please give a better motivation in your commit message.

also, we do have a pretty full featured docker image already, would it help to re-use that for gitpod? the problem would be where to host the image, as the images on ghcr.io cannot be accessed without a github token.

@GitMensch
Copy link
Contributor Author

GitMensch commented Dec 4, 2022 via email

@GitMensch
Copy link
Contributor Author

Does the link in the updated README work for you? Maybe you can tinker around a bit (keeping in mind that the initial setup takes a bit because of updating the system to QT 5.15 and building KDDockWidgets up front.... (I'm creating the Docker issue right now...)

@milianw
Copy link
Member

milianw commented Dec 4, 2022

I don't get it, how would I compile the code in the browser then?

Generally, as this is not something I'm endorsing myself, please state that clearly in the README blurb. Also better document how one would use that to work on the project, or link to the necessary documentation. As-is it's not clear to me at all how I would be using this.

@GitMensch
Copy link
Contributor Author

I don't get it, how would I compile the code in the browser then?

maybe just have a look? What is happening when you click on

Open in Gitpod

In short:

  • a docker container is loaded for you which has a web-x11 configured, that will start hotspot once it is build and has an automated checkout of the repo from the URL
  • this container also features a web-coding via "vscode in the browser" where you actually interact with that container and allows you to use any command via its GUI or via the terminal window
  • it then builds the software (see the recipe in the yml file, should be similar enough scripts+definitions found in this repo)
  • starts hotspot (you see that in the web preview, but can also move that out to a separate browser window)

@milianw
Copy link
Member

milianw commented Dec 5, 2022

I did try that out, but the last two points didn't happen for me. I saw a VS code editor and an XFCE desktop. I tried to build but the "build and run" said that the cmake tools are not installed. I just tried it again and could reproduce that:

Screenshot_20221205_111833

@GitMensch
Copy link
Contributor Author

Thanks for trying it out - Interesting.

Note: very likely the complete installation was not finished (this should get much faster with #446)

Please have a look at the 4 tasks (those in the lower right corner) that start when the workspace starts they wait for each other and I think the last one was not finished, as soon a it is (and it waits for all other tasks as necessary) hotspot should open (and then you may open the xfce in a separate window).

@milianw
Copy link
Member

milianw commented Dec 5, 2022

Where do you see the 4 tasks, can you please highlight the area in the screenshot? I cannot see anything indicating an ongoing task

@GitMensch
Copy link
Contributor Author

Sure. To ensure I have a "clean start" for that I've went to https://gitpod.io/workspaces and clicked on "delete" of the existing workspace, then opened it new (from URL or from workspace overview, doesn't matter).
As I've configured the gitpod branch in the repo as the default one, it is started, and as you've recognized, builds something and starts the X11 session.

The tasks (active and finished) ar in the lower right corner
grafik
waiting a bit (you can click on the tasks to see what they perform) leads then to hotspot being build and as last task that waits for the others, starts it - this was the exact moment where this happened:

grafik

As you may see now, the three above are a bit "greyed out" - because they ar finished, what you also see is that hotspot was started.

... at least I hope you can reproduce it.

And hey, that is X11 again so the issue #339 can be seen there, too.

@GitMensch
Copy link
Contributor Author

Rebased and rechecked, open for comments.

The main "open" issue was: can we include the online/gitpod note and "link" in HACKING or should the last commit be adjusted/removed?

@GitMensch GitMensch marked this pull request as ready for review March 7, 2023 13:51
HACKING.md Outdated Show resolved Hide resolved
@GitMensch GitMensch force-pushed the gitpod branch 2 times, most recently from 4707370 to b3049a5 Compare October 19, 2023 13:01
@GitMensch GitMensch force-pushed the gitpod branch 2 times, most recently from 4a812a2 to 1defb54 Compare October 19, 2023 13:48
@GitMensch
Copy link
Contributor Author

Rebased to current master, updated all dependencies and updated to Ubuntu Jammy.

@GitMensch GitMensch requested a review from milianw October 24, 2023 08:59
@GitMensch GitMensch force-pushed the gitpod branch 3 times, most recently from cc78a04 to 2953d41 Compare October 30, 2023 19:02
@GitMensch
Copy link
Contributor Author

@milianw I've moved the doc note. If you're fine with the current state I'd adjust it to this repo, so you can pull; if not please drop a note which changes you would like to see.

Copy link
Member

@milianw milianw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this can (should?) all be one commit as the individual pieces don't really add any value on their own?

that said - for me only the little remark in the documentation is needed before this can land. As I won't be using this myself, I want to make it clear that I won't maintain this myself. Can we maybe instead just link a GitPod.md file in your fork of hotspot on github, where you explain this setup and then people can report issues there?

.gitpod.yml Outdated Show resolved Hide resolved
HACKING.md Show resolved Hide resolved
@GitMensch
Copy link
Contributor Author

Squashing the commits would be possible, sure.

Linking to an external repo seems bad, as there is no control over that (and personally I try to clean up the repos under my username on GH, too).

Still adding a sentence like "Note: This Gitpod setup is maintained by @GitMensch and not used by @KDAB itself." to that paragraph would be possible.

What do you think?

* setup worker
* build KDDockWidgets
* build perf
* build hotspot
* x11 config allowing to preview the GUI
* gitignore for clangd
@milianw milianw merged commit ed4bbb8 into KDAB:master Nov 10, 2023
12 checks passed
@milianw
Copy link
Member

milianw commented Nov 10, 2023

thanks

@GitMensch
Copy link
Contributor Author

Thanks for merging it in, this makes at least my PRs a lot easier :-)
I'll watch out for improvements, the biggest one may be integration of #446.

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.

2 participants