Jasperr's blog

By Jasperr, history, 4 months ago, In English,

Hey there,

I recently switched from Chrome to Firefox (with the release of Firefox Quantum), and CHelper was one of the extensions which caused me to still use Chrome for some specific tasks. I always wanted to make a browser extension, and because the original CHelper extension got a few broken problem parsers, I decided to make my own.

There are a few differences between the original extension and this one:
- I fixed (most of?) the broken problem parsers
- I added contest parsers which can parse an entire contest at once (just like how you would parse a normal problem)
- It's available for both Chrome and Firefox (even though the original extension works fine on Firefox, but it is not published on Mozilla's AMO making it a bit harder to install)

Problem parsers are available for the following websites: - Atcoder
- Bayan
- CodeChef
- Codeforces
- CSAcademy
- DevSkill
- DMOJ
- E-Olymp
- Facebook Hacker Cup
- Google Code Jam (new)
- HackerEarth
- HackerRank
- Kattis
- LightOJ
- Panda Online Judge
- SPOJ
- Timus
- URI Online Judge
- USACO
- USACO Training
- Yandex

Contest parsers are available for the following websites: - AtCoder
- CodeChef
- Codeforces
- DevSkill
- DMOJ
- E-Olymp
- Google Code Jam (old)
- HackerEarth
- HackerRank
- Kattis
- LightOJ
- Timus
- URI Online Judge

The reason not to update the original extension is that the original extension is centered around the idea that the Java plugin parses the problem page, while I think JavaScript is a better tool for that job.

Available for Chrome and Firefox. The source code is available on GitHub.

Any feedback is greatly appreciated.

 
 
 
 
  • Vote: I like it  
  • +5
  • Vote: I do not like it  

»
4 months ago, # |
  Vote: I like it +5 Vote: I do not like it

Auto comment: topic has been updated by Jasperr (previous revision, new revision, compare).

»
3 weeks ago, # |
  Vote: I like it 0 Vote: I do not like it

Hey there, great job on the extension. Any chance we'll see support for the new Google Code Jam layout?

  • »
    »
    3 weeks ago, # ^ |
      Vote: I like it 0 Vote: I do not like it

    Do you have a link to a page where it's not working? If I go to https://code.google.com/codejam/contest/6314486/dashboard it seems to work just fine.

    • »
      »
      »
      3 weeks ago, # ^ |
        Vote: I like it 0 Vote: I do not like it

      They have a new contest platform for now. Check it out.

      • »
        »
        »
        »
        3 weeks ago, # ^ |
          Vote: I like it 0 Vote: I do not like it

        Thanks! I'll see what I can do in a few hours. Apparently the Java class needs to be called Solution, so that might require some more changes than just adding a new parser.

      • »
        »
        »
        »
        3 weeks ago, # ^ |
          Vote: I like it 0 Vote: I do not like it

        I got too busy yesterday with university assessments, so that's why there's no update yet. I will however make sure it is updated before the online qualification round starts (if access to the practice round on the new platform is not restricted after it ends, because I need something to test with).

      • »
        »
        »
        »
        3 weeks ago, # ^ |
          Vote: I like it +5 Vote: I do not like it

        I updated the extension to support the new platform. The only downside is that you have to manually rename the output class name from "Main" to "Solution", but you'll see that yourself by the notification that appears when parsing a problem on the new website.

        • »
          »
          »
          »
          »
          3 weeks ago, # ^ |
            Vote: I like it 0 Vote: I do not like it

          Thanks for the prompt update. On a similar note, the parser doesn't seem to be working on USACO. It doesn't light up on this problem. I'm on the newest Chrome and permissions are on for usaco.org and all of the defaults. Can you check that out?

          • »
            »
            »
            »
            »
            »
            3 weeks ago, # ^ |
              Vote: I like it 0 Vote: I do not like it

            I'll have a look at it later this week (exams have priority at the moment).

          • »
            »
            »
            »
            »
            »
            13 days ago, # ^ |
              Vote: I like it 0 Vote: I do not like it

            I just released an update that should fix this bug. It's currently in the reviewing stage in both Mozilla's AMO and Chrome's Web Store, so it should be available in a few hours.

»
3 weeks ago, # |
  Vote: I like it 0 Vote: I do not like it

Can anyone tell me what additional thing I will have to do to make this work?

The original parser has been troubling me for days now. I uninstalled it. But even after installing your new parser, whenever I click, nothing happens.

What extra settings (apart from downloading it) I will have to do to make it work?

Please help.

  • »
    »
    3 weeks ago, # ^ |
      Vote: I like it 0 Vote: I do not like it

    You need to have a CHelper project open in IntelliJ IDEA (with CHelper installed, obviously). In some cases you'll also have to refresh the webpage before the little plus icon becomes available (this issue happens quite a bit on HackerRank due to the way how they load the pages).

    If it still doesn't work, please send me a link to the problem page so I can look into it.

    • »
      »
      »
      3 weeks ago, # ^ |
        Vote: I like it 0 Vote: I do not like it

      The project is open. Check this. Is that wrong?

    • »
      »
      »
      3 weeks ago, # ^ |
        Vote: I like it 0 Vote: I do not like it

      and see this, your extension turns green but on clicking it, nothing is happening. :(

      • »
        »
        »
        »
        3 weeks ago, # ^ |
          Vote: I like it 0 Vote: I do not like it

        Hmm, that's odd, it works fine for me:

        There was someone with a similar problem some time ago, could you try uninstalling the extension and then re-installing it?

        • »
          »
          »
          »
          »
          3 weeks ago, # ^ |
            Vote: I like it 0 Vote: I do not like it

          Nope its still not working.

        • »
          »
          »
          »
          »
          3 weeks ago, # ^ |
          Rev. 2   Vote: I like it 0 Vote: I do not like it

          The strange thing or probably not so strange thing is that my normal parser works in Intellij.

          See this.

          Is there any problem with my chrome? Though, I believe that it's quite unlikely.

          • »
            »
            »
            »
            »
            »
            3 weeks ago, # ^ |
              Vote: I like it 0 Vote: I do not like it

            Very strange. The two parsers are not related, so that can't be it.

            I am quite busy this week and next week so I don't have much time to look into it, but I got two more questions:

            1. Can you successfully parse other problems, like for example https://open.kattis.com/problems/apaxiaaans?
            2. When you parse the problem you provided where it doesn't work, do you see something in IntelliJ IDEA's event log?

»
3 weeks ago, # |
Rev. 2   Vote: I like it 0 Vote: I do not like it

This is a great fix for the old buggy CHelper extension. One question though, is it able to parse USACO problems in analysis mode? Whenever I try to do that the icon is grayed out. I have my IntelliJ application open, and the extension works on everything but USACO. Ex:

  • »
    »
    3 weeks ago, # ^ |
      Vote: I like it +1 Vote: I do not like it

    At the moment it is only able to parse problem pages. I'll see if I can add support for analysis mode and train.usaco.org problems later this week.

  • »
    »
    13 days ago, # ^ |
      Vote: I like it +1 Vote: I do not like it

    I just released an update with support for USACO Analysis mode and USACO Training (among some other new parsers). It's currently in the reviewing stage in both Mozilla's AMO and Chrome's Web Store, so it should be available in a few hours.

    • »
      »
      »
      13 days ago, # ^ |
        Vote: I like it 0 Vote: I do not like it

      Works now, thanks!

    • »
      »
      »
      12 days ago, # ^ |
      Rev. 2   Vote: I like it 0 Vote: I do not like it

      The codeforces parser seems to be bugged currently, doesn't read in the input into the tester. Works for contest parser though, so that's kind of strange. Also, the task class doesn't have the problem name in the task name anymore, which is something I liked about this parser over the other one. Great job on your plugin so far though.

      • »
        »
        »
        »
        9 days ago, # ^ |
          Vote: I like it +1 Vote: I do not like it

        If someone else happens to have the same issue with the extension not reading the input and output: make sure you have the latest version of the CHelper plugin installed, and make sure you are not using CHelper Beta (the non-beta version is newer than the beta version).

        As for the issue with the names, I just released an update that fixes this. It's currently in the reviewing stage, so it should be available in a few hours.