Conditions not entirely known, but these might be the reasons:

• Identical name to a current existing member
• Missing ID
• Out of range birthday
• Empty fields

E.g. in Germany we have two season halves, which have different configuration. The first half the wrestling styles are the opposite of the second half. So it would be good to:

• add a flag seasonPartition to LeagueWeightClass
• add a flag seasonPartition to TeamMatch
• on edit TeamMatch only show the correct weight classes.
• Check if generation of bouts is correct

• Server
• Client

• Edit for Bouts
• Info Section leading to Lineup Edit
• Lineup Edit: two buttons: Save Save & Generate with "Are you sure" dialog.
• Add participations to lineup without weight class

The policies for strict-origin-when-cross-origin are probably not in agreement to the WWW standard.

• Put Save and Generate in the overview
• Generating bouts, doesn't update the match (if changing participation, it still does not get updated)
• Generating doesn't consider season_partitions

Time is backwards in international bouts

• BRV: https://www.brv-ringen.de/index.php?option=com_wbw&view=wbw&Itemid=516&tk=dw&dwbid=1&op=da&opa=0&ops=counter&dwcid=4&dwnid=18&opv=lcl#top
  • Can it handle 'V' and 'O' actions.
  • How does this format handle semicolons
  • Ensure it correctly parses ÖÄÜ in names, etc.
  • Dart does not allow parsing all html escaped characters, see: dart-lang/sdk#13102
• https://uww.org/sites/default/files/media/document/wrestling_rules_1.pdf
• https://www.ringen.de/wp-content/uploads/2018/05/BL-Richtlinien-2018-2019-Mai-2018.pdf
• May also add other providers

Adapt Bout Results to:
https://github.com/Oberhauser-Dev/wrestling_scoreboard/blob/5f6112fac18d931c4ecfeca6da67ea381aa1be6a/wrestling_scoreboard_client/docs/score_sheets/uww-score-sheet-competition-2023.pdf

• PopScope

• Web (direct push of client/server to hoster)
• Snap
• Windows Store
• Android Play Store (fastlane?)
• iOS App Store (fastlane?)

When idling for a few seconds on a page, a notification pops up that the connection was lost. This is most likely connected the socket connection.

To be able to revert changes etc.

• For now we could do auto backup on the server, e.g. after every bout

Possibly if nested with KeyboardListener

Wrap releases and deployment inside a command line app, like extending https://pub.dev/packages/flutter_to_debian

Wrap all this inside an Github Action, like https://docs.github.com/en/actions/creating-actions/creating-a-composite-action

See: use rules like in https://github.com/flutter/gallery/tree/main/.github/workflows

• Fight to Bout
• Round to Period (this was already the case)
• Round describes the round of a tournament, e.g. Qualification rounds, Elimination rounds, Repechage rounds, Finals
• Tournament to Competition Einzelturnier, team competition is Mannschaftsturnier, team_match does not really have an alternative
• Participant to Athlete

See https://github.com/Oberhauser-Dev/wrestling_scoreboard/tree/main/wrestling_scoreboard_client/docs/wrestling_rules for more terms

Source: https://uww.org/sites/default/files/media/document/wrestling_rules_1.pdf

Tournament schedule naming convention

• Level 0: Fight order / Kampffolge → How the encounters are ordered within a tournament (day)
• Level 1: Cycle Z / Zyklus Z → General iteration number of the tournament
• Level 2: Age Group A / Altersklasse A
• Level 3: Weight Class W / Gewichtsklasse W
• Level 4: Round R / Runde R → Specific iteration number of the age group / weight class combination
• Level 5: Fight No. X / Kampf-Nr. X → Unique increment value

Example:

Kampffolge:
[...]
Zyklus 2
  B-Jugend - 130 kg - Runde 1
    Kampf-Nr. 54: Max Mustermann vs. Peter Pan
  E-Jugend - 21 kg - Runde 2
    Kampf-Nr. 55: Mustafa Jacobson vs. David Goliath
[...]

In this scenario, B-Jugend - 130 kg did skip the first cycle and had their first round during cycle 2. E-Jugend - 21 kg had their second round during the second cycle, so they are bit ahead.

Timestamps

Required UTC timestamps to be able to reliably track errors, stuck encounters or slow progression.

• Call Time / Aufrufzeit → When was the fight assigned to a mat
• Start Time / Startzeit → When was the timer started
• Finish Time / Abschlusszeit → When was the result confirmed or signed

Printing Status

Kinds of printing status per Age Group - Weight Class

• Call Checklist ( Announcer Table)
  • Has the fight been called, has the fight template been delivered to the table, has it been brought back
  • Not needed when the announcer works digitally
• Competition List (Fighter / Trainer Area)
  • How are the current standings per class
  • Not needed when all classes have digital displays or the results are live and online available
• Fight Templates (Referee Table)
  • Paper for tracking the individual fight progress. Points, fight duration, etc
  • Not needed when the table works digitally
• Certificate / Urkunde: When the class has finished, track whether or not a certificate has been printed

Whenever a new result comes in and/or a new round is paired, update the printing status for each kind whether or not a new version needs to be printed

• Round 0: Even before the first result comes in, we need a printout so that the participants know who they fight.
• Round N: Even after the last result came in, update the printouts so that everyone knows who won. Even if people have the tendency to rip off those papers and keep them rather than taking a photo... Put behind glass.
• Every incoming result would put require a reprint, so don't ask for new printouts until all fights of a class round have been received and the next round has been paired (if possible or necessary)

Time estimates / Tournament length prediction

• Rough total estimate
  • There might a good simple polynomial function for estimating how many fight are necessary depending on the class size M
  • E.g. (M-1)(M) / 2 in Round-Robin
• Detailed time planning
• When you plan the class sequence in detail for each cycle, you will usually only know about deterministic class rounds. Eg. Round-Robin (<= 6 members) or only the first two rounds in Double Elimination Pool System (>6 members). For Double Elemenation Pool System it would be necessary to introduce P placeholder rounds, where P is the maximum round number until it is guaranteed that only 3 members are left per pool (upper bound of P is Round-Robin).
• Double Elimination Pool System: Also add one more round for finals or two more rounds for cross-over finals.

• Team Match

If having a preselected league only allow to select teams, which are in that league. If no league is selected, show all teams.

Add version to database to properly handle migrations in the future.

Freistil

• bei Ablauf der Aktivitätszeit ein Punkt für Gegner (P1, soll das P geschrieben werden, wenn ja, davor oder danach?)
• wenn passiver Ringer Punkt macht, dann Aktivitätszeit beenden

Griechisch:

• Passivität gibt gleich 1 Punkt (P1)

• Dritte Passivität kein Punkt mehr (egal welcher Ringer), nur P

• d.h. keine Aktivitätzeit in Griechisch-Römisch möglich

• may add option to disable auto (smart) points in settings

• Who wins a bout proposal, z.B. TÜ

See: https://github.com/material-foundation/flutter-packages/blob/main/packages/google_fonts/example/lib/example_font_selection.dart

Also don't forget to download the default font and add the according licenses.

A team must be able to be part of multiple leagues rather a single one (n:n relationship).

There might be multiple leagues happening at once and a new season should not invalidate present data.

E.g. FC Bayern I (first team) might be part of Champions League 2022, Champions League 2023, 1. Bundesliga 2023 and 2. Bundesliga 2024.

Consequences:

• The assignment of a league in the team edit panel is not really needed. If the functionality shall remain, the assignment needs to be dedicated modifiable list rather than a drop-down.

See also: https://github.com/Oberhauser-Dev/naturfreunde_snow_sports_app/blob/main/lib/scenes/more/about.dart

• Adapt settings screen to vanilla layout
• Add Scaffold to More screen

Adding a new weight class does not refresh the parent league overview.

Or just save it in local program cache. Let's see if the upload specification actually needs it.

Managing match-ups is logically not dependent on a single team, therefor it should not be hidden under the team view for the league.

The classification points are updated, but not the FightResult and the match points

Adding a new weight team to a club does not refresh the club overview page.

This may occurs, if database has been reset, while client is connected.

The stacktrace would be needed to reproduce errors during production.

Blocked by dart-lang/shelf#2

Last name is shifted to the left compared to the first name because it is missing an icon.

Gender is shifted the right because it is a drop down menu.

Depending on the region, if it's a competition or a league bout, or if it's for adults or children, different points and actions may apply.

Hi,

could you integrate the BRV-API?

See Postman:
RingenAPI.postman_collection.json