I think you can add these things about cph

[agrawal-d]

Thanks for these feature requests. As an when I get time, I will implement the ones I find feasible.

• Num 1, Num 2 seem good. I will try to add these in the future.

• I can't do num 3. because it will make the usage too complicated and it's not a priority.

• Num 4. is not a priority for now.

• Num 5. is unnecessary.

• I can't do num 6. because it's too complicated and really not necessary.

• I cant do num. 7 because its a very niche feature, and it's not a priority.

I don't understand what you mean by num 8. Can you please elaborate?

[SPyofgame200]

Can I suggest some ideas ? (These may slowdown the test so can you do a Advance Mode for advance setting allowed ?)

1) Add some more verdicts instead of Success and Failed

-> AC: Accepted (Compare to the Expected Output)

-> WA: Wrong Answer (Compare to the Expected Output)

-> TLE: Time Limit Exceed (Given Excution Time Limitation)

-> MLE: Memory Limit Exceed (Given Memory Using Limitation)

-> ILE: Idleness Limit Exceed

-> CPE: Compile Error (Error in the Code)

-> RTE: Run Time Error (Error while running Code)

-> Skip: Don’t verdict for some reason or marked for not testing

-> ANO: Custom Verdict

2) Advance Settings for Each Testcase

-> Expected Output Floating Point Detection (0 as default)

-> Excution Time Limitation (2000ms as default) // Only affect the verdict but not stop program when it pass limit

-> Extra Excution Time (0ms as default, limit + extra <= 10000ms) // Will stop the program after it pass the limit + extra

-> Memory Using Limitation (10Mb as default) // Only affect the verdict but not stop program when it pass limit

-> Extra Memory Using (0Mb as default, limit + extra <= 256Mb) // Will stop the program after it pass the limit + extra

3) Advance Settings for All Testcases

-> Show upto line (10 as default) // If want to show more or less, press Show more/Show less

-> Move up button

-> Move down button

-> Move to first

-> Move to last

-> Move to position (#0 as default)

-> Skip? // Block or Allow to test

-> Secondary Expected Output? (Disable as default) // If the code doesnt pass the first expected output

-> Save (In same directory as default) // Store testcases to default file for latter use

-> Stder output? (Disable as default) // for debugging using cerr output

"4) Advance Settings for codes

-> Testcase comparing button // Verdict both then compare

Hope your project become success and well-known <3

[agrawal-d]

Thanks for the suggestions, @SPyofgame. I'll keep them in mind.

[karan221]

Python support will be great.

[mr2rm]

Python support will be great.

@karan221 I think it's a good idea to create a new issue for it. Also I've created #18 PR to add Python support and It's already in progress.

[agrawal-d]

Closing as it's a stale feature request.