@jutge.org/toolkit 4.2.22 → 4.2.24

package/assets/problems/games/the-walking-dead.pbm/ca/Viewer/viewer.sh

@@ -0,0 +1,28 @@
+#!/bin/bash
+
+
+command_exists () {
+    type "$1" &> /dev/null ;
+}
+
+UNAME=`uname`
+
+#kiosk = "--kiosk"
+
+if [  $UNAME = "Linux" ] ; then
+  if command_exists chromium-browser ; then
+    chromium-browser $kiosk --allow-file-access-from-files file://`pwd`/viewer.html?game=$1\&start=yes
+  elif command_exists chrome-browser ; then
+    chrome-browser  $kiosk --allow-file-access-from-files file://`pwd`/viewer.html?game=$1\&start=yes
+  elif command_exists /opt/google/chrome/google-chrome ; then
+    /opt/google/chrome/google-chrome $kiosk --allow-file-access-from-files file://`pwd`/viewer.html?game=$1\&start=yes
+  elif command_exists firefox ; then
+    firefox file://`pwd`/viewer.html?game=$1\&start=yes
+  else
+    echo "Cannot find a browser"
+  fi
+elif [ $UNAME = "Darwin" ] ; then
+  open -a "Google Chrome" --args --allow-file-access-from-files file://`pwd`/viewer.html?game=$1\&start=yes
+else
+  echo "Unrecognized system"
+fi

package/assets/problems/games/the-walking-dead.pbm/ca/handler.yml

@@ -0,0 +1,6 @@
+handler: game
+game:
+  hide:
+    - Board.cc
+    - AIDummy.cc
+

package/assets/problems/games/the-walking-dead.pbm/ca/problem.ca.yml

@@ -0,0 +1,3 @@
+title: TheWalkingDead
+author: Albert Oliveras
+email: oliveras@cs.upc.edu

package/assets/prompts/creators/create-solution.tpl.txt

@@ -1,10 +1,17 @@
-Now, write a solution in {{proglang}} to solve this problem
-
-It must be written in an idiomatic way and only include relevant comments.
-The code must be efficient and handle all edge cases.
-The code must read from standard input and write to standard output.
-The code must be well written and easy to understand to novices.
-The code does not have to check the preconditions stated in the problem statement.
-Do not use any non-standard libraries.
+Now, write a solution in {{proglang}} to solve this problem.
+
+Take these instructions into account:
+
+- It must be written in an idiomatic way and only include relevant comments.
+
+- The code must be efficient and handle all edge cases.
+
+- The code must read from standard input and write to standard output.
+
+- The code must be well written and easy to understand to novices. It cannot use advanced constructs.
+
+- The code does not have to check the preconditions stated in the problem statement.
+
+- Do not use any non-standard libraries.
 
 {{proglangPrompt}}

package/assets/prompts/proglangs/cc.md

@@ -1,3 +1,7 @@
-Do not use fast input/output methods.
+# Additional guidelines for C++
 
-Add a `using namespace std;` declaration after the includes and do not use `std::` prefixes.
+- Do not use fast input/output methods.
+
+- Add a `using namespace std;` declaration after the include section and do not use `std::` prefixes.
+
+- Avoid the use of long long ints and use ints instead.

package/assets/prompts/proglangs/py.md

@@ -1,10 +1,14 @@
-Use f-strings for string formatting.
+# Additional guidelines for Python
 
-Use type hints for function definitions. Do not use old-style type hints such as `List[int]` with `List` imported from `typing`, but use modern syntax such as `list[int]`.
+- Use f-strings for string formatting when possible.
 
-Additionally, ensure that the generated Python3 code follows best practices, including proper indentation, use of functions, and adherence to PEP 8 style guidelines.
+- Use type hints for function definitions. Do not use old-style type hints such as `List[int]` with `List` imported from `typing`, but use modern syntax such as `list[int]`.
 
-Important: Do not use `input()`, `sys.stdin()`, or `EOFError`` to read input as data can be placed freely across many lines. Instead, use the yogi library:
+- Ensure that the generated Python3 code follows best practices, including proper indentation, use of functions, use of docstrings, and adherence to PEP 8 style guidelines.
+
+# Very important
+
+Do not use `input()`, `sys.stdin()`, or `EOFError` to read input as data can be placed freely across many lines. Instead, use the `yogi` library:
 
 `yogi` provides three functions for reading typed input:
 
@@ -24,7 +28,7 @@ x = scan(int)  # returns int or None
 while x is not None:
     s += x
     x = scan(int)  # returns int or None
-print(s)
+print(s) # prints the sum of all the integers in the input
 ```
 
 **`tokens(type)`** - Iterator that yields tokens of specified type until input ends. Raises exception on type mismatch.
@@ -34,7 +38,7 @@ from yogi import tokens
 s = 0
 for x in tokens(int):  # iterates over all integers in the input
     s += x
-print(s)
+print(s) # prints the sum of all the integers in the input
 ```
 
 In yogi functions, `type` can be `int`, `float`, or `str`.