Highlights
The trial competitions, first solo and now in teams of two, taught us a lot, and most of this week went into what they showed. Thanks to everyone taking part and sending feedback. Behind the scenes, work on a new Studio built from the ground up is starting; more about that next week.
- Questions and announcements: competitors ask the organizers from the event page, and the published answers and the organizers' announcements appear there too.
- Team submissions: team members see all of their team's submissions and who sent each one.
- Re-judging: organizers re-judge one submission or every submission of a problem after fixing a test case. A tolerance change re-judges only the results it flips.
- Several administrators per event, picked with a user search.
- Studio: END is added when you type a TO line, the colour picker has all 16 Logo colours, and the code lists can be searched and filtered.
- Thank you, Judge0. When a student runs or submits a Python or C++ program, the code runs on Judge0, the open-source code execution system by Herman Zvonimir Došilović. Without it, competitions in those languages would not be possible. This week its connection to Blocks Code also became more robust.
New features
Studio (students and teachers)
- Event page. A questions card with the published answers and announcements, and the whole team's submissions with their authors.
- Logo auto-end. The END of a procedure is added when its TO line is entered.
- All 16 Logo colours in the simple colour picker.
- Code lists. Search in the Name column, a filter by type, and the lists load as they scroll.
- NULA Mini blocks and a blink example for Soldered boards.
- Colours. The Logo tag is green and the C++ tag blue in the code list, and the turtle blocks wear the logo yellow with dark labels.
- Shop ad points at the new Edu Robo Shop.
- Translations. The submission result cards and the problem preview are translated, and an empty program cannot be submitted.
Administration (organizers, mentors and admins)
- Questions, answers and announcements. A Questions tab on the event page.
- Event administrators. An event can have several administrators, chosen with a user search for organizers.
- Team members read their teammates' submissions.
- Re-judge. One submission, or every submission of a problem from the problem drawer. Results show failed and pending judgements, and a tolerance change re-judges only the results it flips.
- Codes. A paged and searchable codes list.
- Workshops. A status filter and a date range on the list, usernames on attendance rows and bulk adding of users.
- Users and licenses. Import adds existing members to the class, and a license's end date can be cleared.
- Superadmin. Create an organization, and purge a deactivated organization or user together with their self-contained content.
- Security. Sessions expire after 30 idle days or 180 days at most, and repeated failed team join attempts are slowed down.
Fixes and improvements
Studio
- Blocks editor. Starting blocks stay clear of the first flyout, and the formula preview resets with the formula text.
- Playground panels remember their sizes.
- Croatian messages for too many join attempts and for an empty program, and the shop ad's Novo tag stays inside its card.
- Behind the scenes, signing in and the calls to the server got tidier and faster.
Administration
- Judging no longer waits forever on a slow run: a run that takes too long is stopped and reported.
- Soldered and Pybricks problems take no submissions.
- Results show unattempted problems as not attempted and hide the score of a not-attempted event cell.
- Accessibility. A skip link, one heading per page, and Croatian numbers and error messages everywhere.
- Lists keep filter changes after opening a filtered address and keep a filter picked right after typing a search.
- Import handles zip archives with Croatian letters in their file names, and a broken inline picture no longer fails the import.
- Drawings are judged faster.
Content and documentation
- Studio user guide: the competition chapters updated for administrators, questions, feedback and team submissions, and the Logo book lists colour indices 8 to 15.
- Administration docs: the competition manual updated for events, teams and questions.