Difference between revisions of "User:OverPowered/GSoC2021 Progress Report"
Jump to navigation
Jump to search
OverPowered (talk | contribs) (Created page with "'''Google Summer of Code 2021 Progress Report- A Reworked Apertium Browser Plugin''' * [https://wiki.apertium.org/wiki/User:OverPowered/GSoC2021Proposal Original GSoC Propos...") |
OverPowered (talk | contribs) m (added a few lines to progress) |
||
| Line 18: | Line 18: | ||
=== Progress === |
=== Progress === |
||
I've gone through the [https://wiki.apertium.org/wiki/Apertium-apy Apertium Apy] code and built it from source. The parts that I need are outlined in the initial proposal and I don't feel I need to add anything more. As for the [https://wiki.apertium.org/wiki/Geriaoueg Geriaoueg] extension, given how outdated it is, it's better to build a new one from scratch with web-ext than to use parts of it. |
I've gone through the [https://wiki.apertium.org/wiki/Apertium-apy Apertium Apy] code and built it from source. The parts that I need are outlined in the initial proposal and I don't feel I need to add anything more. As for the [https://wiki.apertium.org/wiki/Geriaoueg Geriaoueg] extension, given how outdated it is, it's better to build a new one from scratch with web-ext than to use parts of it. |
||
As for other extensions, I've been looking at [[https://github.com/artemave/translate_onhover OnHover Translate with Google Translate]] for inspiration regarding layout and background processes. I also believe it's best not to copy the exact method they've used there and opt for a normal popup.html instead of a element created with JavaScript on the page itself. |
|||
=== Layout === |
|||
Revision as of 07:10, 28 May 2021
Google Summer of Code 2021 Progress Report- A Reworked Apertium Browser Plugin
Community Bonding Period (May 17 - June 7)
Planned Work
- Understand better how the Apertium API works
- Identify parts of the Geriaoueg extension that still work
- Check Source Code of similar extensions
- Design tests, experiments and evaluation procedures for an extension (which sites it should be able to read, etc.)
- Write a workflow diagram of the improved extension, what background processes it will have and what permissions it will need
Progress
I've gone through the Apertium Apy code and built it from source. The parts that I need are outlined in the initial proposal and I don't feel I need to add anything more. As for the Geriaoueg extension, given how outdated it is, it's better to build a new one from scratch with web-ext than to use parts of it.
As for other extensions, I've been looking at [OnHover Translate with Google Translate] for inspiration regarding layout and background processes. I also believe it's best not to copy the exact method they've used there and opt for a normal popup.html instead of a element created with JavaScript on the page itself.
