Details
-
Type:
Improvement
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Obsolete
-
Affects Version/s: Current Version
-
Fix Version/s: Far Future
-
Component/s: OIOIOI
-
Labels:None
Description
To be discussed:
IMHO we should change the submission/testrun form from "one for all" to "one per problem". Why?
1. To easily display the number of submissions/testruns and limits
2. To prepare different forms for different problem types (eg. for zeus problems)
3. To accept (and show proper hint) different language sets for different problems.
4. It's hard (or impossible) to maintain and develope all those features in current way.
5. ... @Matrach?
IMHO we should change the submission/testrun form from "one for all" to "one per problem". Why?
1. To easily display the number of submissions/testruns and limits
2. To prepare different forms for different problem types (eg. for zeus problems)
3. To accept (and show proper hint) different language sets for different problems.
4. It's hard (or impossible) to maintain and develope all those features in current way.
5. ... @Matrach?
Activity
- All
- Comments
- History
- Activity
- Transitions
- Commits
Connect your code to JIRA
Link every code change to JIRA just by adding an issue keys in commit messages. Bridge the gap back to your source and know which changes fixed which JIRA issues.
Git & Mercurial in the cloud
Collaborate across unlimited private code repositories.
Git behind the firewall
Manage and collaborate on Git repositories behind a firewall.
Browse and search code
Browse, search, and track source code repositories.
