LeapIn.it uses a REST endpoint for access to the database. This is a design pattern for hypermedia systems, which advocates providing individual resources (e.g., people) with unique URLs, and using those URLs to exchange structured information. HTTP requests can be made to these URLs, where HTTP methods are used to instruct what should happen with attached data, and status codes… Read more →
The code for the prototype is available to download from our GitHub repository.
Throughout implementing the prototypes, we’ve employed a number of testing methodologies to ensure that the product is of a high quality. In this post, we’ll discuss four methodologies we have used: regression testing, code modularity, code quality checking and code metric monitoring. Regression testing After each significant change was made to the code, the prototype would be compiled into an… Read more →
During our development of the LeapIn.it prototype, we have used a number of design patterns, libraries and API’s. This post will give an overview of the most crucial of these. Server The server is responsible for creating a REST interface for database access. As mentioned in our post on architecture, we have chosen to use RedBeanPHP to communicate with the… Read more →
We have now implemented a prototype with most of the features we discussed in the design. The following video gives a demonstration of this prototype: This prototype is available here (use the username “test” and password “test”). Screenshots [portfolio_slideshow] Note: the names of rooms and users are chosen randomly by implementing a random words generator.
We have used Apache Cordove to produce a barcode scanner. In the following video, we’ll demonstrate how this will form part of LeapIn.it:
We have developed an initiate web interface for LeapIn.it. This following video gives a demonstration of how this can be used to navigate rich media: This prototype is available here (use the username “test” and password “test”). Screenshots [portfolio_slideshow]
In planning how we would implement a LeapIn.it prototype, we agree that we should use similar development environments to prevent any mistakes or unforeseen incompatibilities. We agreed that we would use the following tools: Git – allows us to collaborate and manage versions of code GitHub – a website where Git repositories can be stored centrally. This ensures our code is… Read more →