User Tools

Site Tools


labs:e2d2

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
labs:e2d2 [2015/07/15 17:15]
ngw8 Added a bit more
labs:e2d2 [2015/07/15 17:33] (current)
ngw8 Added image
Line 1: Line 1:
-E2D2 began as a summer research project at the end of 2014, aiming to bring Expeditee to Android devices while also exploring the possibility of making Android as a whole more Expeditee-like. A bit more about the results of the summer project can be found at [[http://​www.nwatson.nz/​projects/​expeditee-android/​|nwatson.nz/​projects/​expeditee-android]].+====== E2D2 ====== 
 + 
 +//​Refactoring and restructuring Expeditee//​ 
 + 
 +{{:​labs:​e2d2-logo.png?​nolink|E2D2 Android app logo}} 
 + 
 +E2D2 began as a summer research project at the end of 2014, aiming to bring Expeditee to Android devices while also exploring the possibility of making Android as a whole more Expeditee-like. A bit more about the summer project can be found at [[http://​www.nwatson.nz/​projects/​expeditee-android/​|nwatson.nz/​projects/​expeditee-android]].
  
 One of the major issues that was faced during this project was determining the approach that should be taken in porting the Expeditee codebase to Android. While Expeditee is written in Java - the primary language for creating apps on Android - Android does not support any of the user interface code (i.e. the AWT and Swing libraries) required to run Expeditee. During the summer project, progress was made on solving this problem by re-writing a small portion of the Expeditee code base so that it's user interface and core logic were completely separate, allowing (in theory) the same core logic code to be used on both the Android and desktop versions. One of the major issues that was faced during this project was determining the approach that should be taken in porting the Expeditee codebase to Android. While Expeditee is written in Java - the primary language for creating apps on Android - Android does not support any of the user interface code (i.e. the AWT and Swing libraries) required to run Expeditee. During the summer project, progress was made on solving this problem by re-writing a small portion of the Expeditee code base so that it's user interface and core logic were completely separate, allowing (in theory) the same core logic code to be used on both the Android and desktop versions.
  
 The aim of the continued work on the project is to further explore the best approaches to take in restructuring Expeditee'​s code. The main target of such restructuring would be to have an Expeditee core that could be run on a range of systems, abstracting away things such as the user interface and potentially input, file handling, and other components that may differ between systems or need to be replaced in the future. Research will include looking at potential architecture patterns that could be used and approaches to refactoring the code. It is hoped that some of this will be able to be implemented as part of the project. The aim of the continued work on the project is to further explore the best approaches to take in restructuring Expeditee'​s code. The main target of such restructuring would be to have an Expeditee core that could be run on a range of systems, abstracting away things such as the user interface and potentially input, file handling, and other components that may differ between systems or need to be replaced in the future. Research will include looking at potential architecture patterns that could be used and approaches to refactoring the code. It is hoped that some of this will be able to be implemented as part of the project.
labs/e2d2.txt · Last modified: 2015/07/15 17:33 by ngw8