mfasda / indicocheckin Goto Github PK

default entries in server address and event ID fields

The manual search appears to be case sensitive, so that entries starting with small letters are put in at the end. The manual search window has to be case insensitive.

In case no webcam is found the application should still run via manual search.

Implement a find textfield inside the manual search dialog to find the registrant according to the last name.

• standard case: code is read successfully, person is not yet checked
  in and person has already paid
  --> no message box appears, but it beeps once, checks the person in
  and prints the ticket. If error while printing, you can click on the
  print button to retry printing.
• case: person has not yet paid
  --> it beeps twice, you can set person to paid and check him in and
  print the ticket
• case: ticket cannot be read, or person is already checked in, or
  other error
  --> three beeps, you can then search the person manually, or print
  the ticket again, if already checked in

--> so in standard case, for each person, only one click is needed,
namely to start the code reading

It would be nice that the admin can search the conference instead of putting in the conference ID by hand. Priorty for this task is lowest since this is an optional feature improving the handling instead of providing core functionality.

Implementation of correct handling of social events into the parser and the registrant class.

Before the program is ready to go, all debug statements have to be removed.

Implementation of a panel where users can search registrants according to the name without having the ticket at hand. The further logic is in the same way as for the usage with ticket.

Further information should be added to the registrant display:

• amount which is already paid
• number of participants in the conference dinner
• number of social events booked

If the payment status is true, then the entry in the display should appear in green, and if it is set to false, then the entry should appear in red. The same applies for the checkin status.

When the user clicks on the row for the social events, then a display should open with more details about the social events.

Tickets generation has to be implemented. This task consist of a class which produces the tickets and prints them, and the call to that inside the main GUI.

Implement put request for the checkin status into class IndicoAPIConnector in order to change the checkin status in the indico database.

Instead of using apikey and apisecret, use oauth in order to authenticate with the indico server. For this, we need from Indico a consumer key and a consumer token, and a set of URLs.

Registrants should be allowed to pay in cash at the conference desk. For this, the programm will have a payment function. The payment function consists of the following subtasks:

• Obtain total price to be paid from the single fields (conference fee, conference dinner, social events)
• Post the payment status to indico (setting paid to true and setting the amout_paid field)
• Update user information and enable buttons for checkin and ticket generation.

An info dialog with the copyright statement should be impemented.