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

Port to GTK3 #2

Closed
alexandrucosminmihai opened this issue Feb 16, 2018 · 6 comments
Closed

Port to GTK3 #2

alexandrucosminmihai opened this issue Feb 16, 2018 · 6 comments

Comments

@alexandrucosminmihai
Copy link

I would like to try to port this activity to GTK3

@quozl
Copy link
Contributor

quozl commented Feb 17, 2018

Thanks. When you do, please also;

  • use the sugar-toolkit-gtk3 classes instead of the bundled toolkit classes in this repository,
  • move into the top level directory any toolkit classes that are not in sugar-toolkit-gtk3,
  • remove the bundled toolkit classes,
  • test the ported activity and document your test environment in your commit.

Looking forward to seeing your work.

@quozl
Copy link
Contributor

quozl commented Feb 19, 2018

Recommend that you not try to port the toolkit classes until you have proved that they are not in sugar-toolkit-gtk3.

The activity was written to be Sugar version independent by a contributor who was very good at doing that. For the activity to be installed on a very old Sugar version, where certain toolkit features are absent, the contributor added newer Sugar toolkit features into the activity.

So there is some duplication between toolkit in this activity and the sugar-toolkit sources.

As the issue is porting to GTK+ 3; a move from sugar-toolkit to sugar-toolkit-gtk3, you should check for and remove this duplication. Otherwise the code will suffer from two future problems;

  • features or bug fixes in sugar-toolkit-gtk3 won't be effective in the activity, leading to issues being reported,
  • further porting to GTK+ 4 expected within a few years will be more expensive than it needs to be; because there will be more lines of code to port and review.

You should also use flake8 to correct any problems. One of the problems is wildcard imports, which makes it harder to do this port. See https://github.com/sugarlabs/sugar-docs/blob/ee2f983b35d7821971ba3f6422e8ba834c4755ec/src/desktop-activity.md#coding-standards

@alexandrucosminmihai
Copy link
Author

Thank you very much for this information! Things are clearer in my mind now. I still want to work on this issue, but it will probably take me some time. I hope this is not a problem.

@quozl
Copy link
Contributor

quozl commented Feb 20, 2018

No problem. If there is a delay, check the commits, branches and forks before you begin work; in case someone else has done work on it.

@yell0wfl4sh
Copy link
Contributor

@JuiP
Copy link
Member

JuiP commented Aug 10, 2020

#6 merged, closes this issue :)
@quozl @chimosky

@quozl quozl closed this as completed Aug 11, 2020
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

No branches or pull requests

4 participants