<commit_before>\todo{Skal bindes sammen med de tidligere afsnit hvor vi har snakket om website og om vi har fået implementeret det vi ville og evt hvad der er anderledes}As mentioned in \secref{sec:problemstatement}, the purpose of the website is to allow the exhibition managers to make a floor plan, booths, schedule and other concepts of an exhibition. We chose to design it as an (almost) one-page site. 
\todo{Beskrivelse af website. En gennemgang af det, hvad kan man med website. Mere beskrivelse af de forskellige tabs osv}
The website is built using HTML, PHP and jQuery. The main tab on the website is the "Map" tab, which is used for designing the floor plan. This tab is built using the Google Maps API. Using this tab the organizer can create a complete exhibition with booths etc.
After creating an exhibition the user can add feeds to the exhibition, using the "Feeds" tab. A schedule can be added using the the schedule tab.
It is also possible to load an existing exhibition from the database, for the loaded exhibition the floor plan will be shown but the user is unable to edit the floor plan in the current version.

The website uses the AJAX technology for form submit to make the website more user-friendly. The AJAX posts to PHP, which handles the database interaction. When connecting to the database we are using prepare statements, to make sure no malicious data is inserted into the database.

The design of the website is done using Twitter Bootstrap making it more slick, and uniform.
The main focus in the website is functionality and therefore the design and usability is not the main priority.




Flowchart diagram. \todo{Tænker flow chart skal være først}


Schedule - booth with same name, doesn't \todo{Doesn't?}<commit_msg>Added website text<commit_after>The website is build to allow exhibition managers to manage their exhibition, as stated in the problem statement\secref{sec:problemstatement}. All concepts of an exhibtion can be added from the website, this include feeds, schedule, booths, companies, categories and a floor plan.
The diffrent tabs manage diffrent concepts of an exhibiton:
Feeds: Here the manager can add a feed to a booth in the databse.
Company: Here the manager can add a company to the database, the company logo will also be uploaded to the server for futher use.
Category: In this tab the manager can add a category to the database for futher use.
Exhib: In the Exhib tab the manager can create a new empty exhibition.
Schedule: In the Schedule tab the manager can create a new schedule and add it to a booth in the database.
Map: The map tab is the heart of the website, here almost all the other concepts can be added, this include, making a new exhibition, complete with a floor plan, categories, companies, and booths. Previous created exhibitions can also be loaded for viewing or editing.

The problem statement\secref{sec:problemstatement} states that booths should be able to create feeds themself, this have not been used in the design of the website, but is possible with the integration of a login system on the website. This will also make sure managers only will be able to edit their own exhibitions.

The website is designed with the main focus on the "map" tab, this tab functions almost as a standalone one-page website, though the "feed" and "schdule" tab is also need to make a "complete" exhibition.

The website is built using HTML, PHP and jQuery. The "map" tab makes use of the Google Maps API, for giving a visual presentation when creating an exhibtion.
Here the user can place markers, which in turn make up the walkingpath of the exhibtion. The user can also place booths on the map, dragging a rectangle to the prefered position and then locking it in place. When the "booth" is locked a dialog appears and here the user can enter "Name", "Description", "Category" and "Company".

After creating an exhibition the user can add feeds to the exhibition, using the "Feeds" tab, feeds are bound to an existing booth from the database. A schedule can be added using the the schedule tab, here the user selects a "name", "booth", "start time" and "end time".
It is also possible to load an existing exhibition from the database, for the loaded exhibition the floor plan will be shown, this exhibition can then be edited and saved to the database, reflecting the changes the user has made.

The website uses the AJAX technology for form submit to make the website more user-friendly. The AJAX posts to PHP, which handles the database interaction. When connecting to the database we are using prepare statements, to make sure no malicious data is inserted into the database.

The design of the website is done using Twitter Bootstrap making it more slick, and uniform.
The main focus in the website is functionality and therefore the design and usability is not the main priority.




Flowchart diagram af map tabben.
{'fraction_non_alphanumeric': 0.034876606159494186, 'fraction_numerical': 0.0, 'mean_word_length': 4.4793296089385475, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5276955', 'n_tokens_mistral': 1181, 'n_tokens_neox': 1131, 'n_words': 820}