Hi all,

I am planning the next version of oTree. Would be interested to hear people's feature requests, ideas, or general topics about use cases that we should enable better.

Thank you,
Chris

It would be nice if dependencies such as starlette could be upgraded to the latest version so that this package is usable in combination with other python libraries. In my case I would like to install a package that requires fastapi. The version of starlette that is currently in the requirements of otree is 0.14.1 which is almost 5 years old. 

Further, there seem to be some security vulnerabilities with versions older than 0.40.0 of starlette: https://nvd.nist.gov/vuln/detail/CVE-2024-47874

Hi Chris

I had a project where I could have used a live_method on a WaitPage, which is not yet supported. 
It would be nice if that could be added.

Also: +1 to the dependencies upgrade! 
(In my case the dependencies with alter_ego cause conflicts)

Best,
Daniel

Thank you for your continued efforts! Here are some feature requests that have been made several times already:

It would be nice if features such as the focus detection on wait pages that wait for participants to group could be turned off. I.e., allow participants to be matched although they do not currently have the tab in focus. This could be an option in settings or in the group by arrival time method.

Server-side triggered live methods on schedules would be nice. I.e., send a message to the clients via websockets every x seconds. 

Have special pages for instructions that allow going back and forth between them.

Waitpages that can be left if waiting takes too long.

Allow custom views, routes, and websocket consumers to be defined.

Hi Chris,
I would be much interested in ChristianK's suggestion about Server-side triggered live methods on schedules (sending a message every x seconds to (a group of) participants .
Thank you for your work and time.
Best,
Rudy

Hi Chris,
First of all, thanks for the effort you’re putting into oTree. Two suggestions from my side:

1. Native support for checkboxes / multiple-choice with multiple selection.
2. REST API access to SESSION_FIELDS.

Best,
Michael

Hi Chris -

Currently, custom_export reports default to the same filename as regular output reports - it would be a nice ease-of-use upgrade to have them default to have "_custom" in the default filename (or something similar) to help quickly differentiate them from the normal reports.

Thanks,
--Chris

Thanks both for the suggestions! @Chris, check out oTree 6.0 which was just released. It uses separate filenames and also provides a REST API to automatically download data exports.

Hey Chris, 
one more thing came to mind that would be especially useful for international studies with multiple languages:
Would it be possible to make LANGUAGE_CODE a session variable? That way, you wouldn’t need to start a separate server for each language, which would simplify things quite a bit.

Thanks for your effort.

Best, 
Michael