Skip to content
This repository has been archived by the owner on Nov 22, 2022. It is now read-only.

Port to webextension #86

Open
wants to merge 31 commits into
base: master
Choose a base branch
from
Open

Conversation

marczellm
Copy link

@marczellm marczellm commented May 9, 2018

This is a working port to WebExtension. Fixes #66 and #85

I did not write a new Makefile as I'm not familiar with it.

@bpierre
Copy link
Owner

bpierre commented May 9, 2018

Thanks for this effort @marczellm, and I apologise for not being as active as I’d like to be on this project. I’ll have a look whenever possible in the next week.

@PerfectSlayer
Copy link
Collaborator

PerfectSlayer commented May 9, 2018

Nice @marczellm 👍 💖

I understand your concern but I am like you! I spent hours to fix some issues and maintain this add-on and I got no right to update it on AMO and no privileged contact with @bpierre 😞

The best I can do is test your (awesome) work and merge your PR.
But it still won't update the add-on on AMO 😢

Whatever you choose, ping me if you need help with Makefile. It's not so complicated once you learn it 😉

@PerfectSlayer
Copy link
Collaborator

@bpierre No worry, it's common in Open Source software that the maintainer became busy or move from a project.
But why do not you create a GitHub organization and list other maintainer as "extension developer" on AMO?
So we could continue to evolve the add-on without having to fork and loose all the users?

@bpierre
Copy link
Owner

bpierre commented May 9, 2018

@PerfectSlayer Sure thing! I didn’t see the release itself as the bottleneck, it’s a quick thing for me to do once we get something merged.

The problem is more to find the time to review PRs, especially this one, which is a rewrite that also contains at least one important UX change. I would like to review it properly before merging it. To be entirely honest, I also felt a bit discouraged when the new Firefox extension format got replaced by a new-new one, and lost some motivation. But I would be super happy to be able to use gtranslate again!

⬇️ Actions ⬇️

  • I think it does makes sense to use gtranslate/gtranslate. I used to think that an organization for a single project was overkill, but it is a common practice on GitHub nowadays. Doing it now. (EDIT: done ✨)
  • Shall we create a Gitter channel? We already have an IRC channel but Gitter might be easier to use nowadays. (EDIT: done https://gitter.im/gtranslate/gtranslate)
  • @PerfectSlayer I will give you the rights to publish releases on AMO too 👍

@marczellm sorry for polluting this PR 😅

@mote0230
Copy link
Collaborator

mote0230 commented May 9, 2018 via email

@marczellm
Copy link
Author

marczellm commented May 9, 2018 via email

@achernyakevich-tch
Copy link

Hi.

Maybe desired feature could be achieved by slight change of user behavior. For example, the following case could be valuable for me:

  • I do some selection on screen
  • I make right click
  • context menu is displayed
  • I navigate to gTranslate's menu item Translate ...
  • I click this menu item
  • on click extension will call Google Translate service, build next level submenu and show to me required information

So difference is only "click/press Enter" vs "on mouse over/selection item by keyboard".

From other side it will completely avoid problem of sending of selection to Google every time when context menu is called.

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

Successfully merging this pull request may close these issues.

Port to new WebExtension format
5 participants