Awful english grammatical errors removed
This commit is contained in:
parent
8e901e699f
commit
42471d1147
64
main.tex
64
main.tex
|
|
@ -127,17 +127,17 @@
|
|||
\begin{en}
|
||||
\section{General information about the work done}
|
||||
|
||||
Since 19 october 2017, I work with \textit{Agomir S.p.A.}\cite{agomir:website}
|
||||
Since 19 October 2017, I have been working with \textit{Agomir S.p.A.}\cite{agomir:website}
|
||||
(vendor and producer of software, networking solutions and services for small
|
||||
and mid-size
|
||||
industries) doing an extended school internship on a weekly basis (thursdays
|
||||
and fridays, in the afternoon). I am involved in developing accounting
|
||||
software, writing multiplatform smartphone applications (that work
|
||||
industries) doing an extended school internship on a weekly basis (Thursdays
|
||||
and Fridays, in the afternoon). I am involved in developing accounting
|
||||
software, writing multiplatform smartphone applications (which work
|
||||
with both Android and iOS) to be precise. In order to do this, I am using tools
|
||||
such as \textit{Ionic Framework}\cite{ionic:website} and \textit{Apache
|
||||
Cordova}\cite{cordova:website}.
|
||||
|
||||
This type of approach to the mobile world makes development more easy because
|
||||
This type of approach to the mobile world makes development easier because
|
||||
instead of using APIs and platform-dependent code it is possible to use
|
||||
well-known and standardized technologies such as HTML and Javascript.
|
||||
Naturally, these apps require more system resources and they generally are
|
||||
|
|
@ -180,12 +180,12 @@
|
|||
existing products from the company, to plan new projects, and for suggestions
|
||||
in general.
|
||||
|
||||
In spite of the lack of control I have in regard to the projects I work on, I
|
||||
Even though I do not have total control on the projects I work on, I
|
||||
am still responsible for defining development milestones and making
|
||||
time estimates for the completion of these.
|
||||
time estimates for their completion.
|
||||
|
||||
In order to increase the work force assigned to the development of mobile
|
||||
apps, I have managed training sessions for some employees in order to show
|
||||
apps, I have organised training sessions for some employees in order to show
|
||||
them how the tools that I use work.
|
||||
\end{en}
|
||||
|
||||
|
|
@ -227,9 +227,9 @@
|
|||
|
||||
\begin{description}
|
||||
\item[Customers' orders] for registering the products customers may order;
|
||||
\item[Customers and suppliers] for looking up record data of customers and
|
||||
\item[Customers and suppliers] for looking up data record of customers and
|
||||
suppliers;
|
||||
\item[Calendar] for viewing and editing events on the ERP calendar, syncable
|
||||
\item[Calendar] for viewing and editing events on the ERP calendar, synchronizable
|
||||
with \textit{Outlook};
|
||||
\item[Warehouses] for managing warehouses and inventories.
|
||||
\end{description}
|
||||
|
|
@ -237,12 +237,12 @@
|
|||
In addition to what specified above, users will be able to register working
|
||||
hours for business trips. This feature is already implemented in
|
||||
\textit{InteGRa.Service}, an app developed in a previous school internship
|
||||
period. The two apps can not be merged immediately due to relevant
|
||||
differencies in their respective architectures.
|
||||
period. The two apps cannot be merged immediately due to relevant
|
||||
differences in their respective architectures.
|
||||
|
||||
Finally, the app will be able to work (with limited functionalities) without
|
||||
a network link with \textit{InteGRa}, offering data syncronization when a
|
||||
connection will be avaliable.
|
||||
connection will be available.
|
||||
\end{en}
|
||||
|
||||
\begin{it}
|
||||
|
|
@ -304,7 +304,7 @@
|
|||
\end{itemize}
|
||||
\end{it}
|
||||
\begin{en}
|
||||
In the picture \ref{fig:itgmobliearch} is shown how the software components
|
||||
Picture \ref{fig:itgmobliearch} shows how the software components
|
||||
in the app interact with each other. This architecture was entirely realized
|
||||
by me, on the basis offered by the project \textit{InteGRa.Service}. Further
|
||||
information is given in the following list.
|
||||
|
|
@ -594,12 +594,12 @@ public abstract class ReadableRESTController<T extends Readable,
|
|||
classe ``entità'' \textit{T}, che a sua volta estende \textit{Readable}.
|
||||
\end{it}
|
||||
\begin{en}
|
||||
Even the listing \ref{lst:rdbrest-java} needs a brief explaination. The
|
||||
abstract class \textit{Readable}, used as constraint for the class first generic
|
||||
Even listing \ref{lst:rdbrest-java} needs a brief explanation. The
|
||||
abstract class \textit{Readable}, used as a constraint for the class first generic
|
||||
parameter, is the father of each ``entity'' class, while
|
||||
\textit{PrimaryKey<T>} is the father of the class that contains the primary
|
||||
key of \textit{T}. An instance the \textit{PrimaryKey<T>} child is embedded as
|
||||
an attribute in the ``entity'' class \textit{T}, which itself extends \textit{Readable}.
|
||||
key of \textit{T}. An instance of the \textit{PrimaryKey<T>} child is embedded as
|
||||
an attribute in the ``entity'' class \textit{T}, which extends \textit{Readable}.
|
||||
\end{en}
|
||||
|
||||
\begin{it}
|
||||
|
|
@ -681,7 +681,7 @@ public abstract class CRUDRESTController<T extends CRUDable, U extends
|
|||
\end{it}
|
||||
\begin{en}
|
||||
The \textit{CRUDable} class extends \textit{Readable} and offers
|
||||
some methods useful for object initialization based on input data given
|
||||
some useful methods for object initialization based on data input given
|
||||
as \textit{MultivaluedMap<String,String>}. Therefore, the ``entity''
|
||||
classes that extend \textit{CRUDable} can be used for read-write operations,
|
||||
e.g. the ones implemented in \textit{CRUDRESTController}.
|
||||
|
|
@ -840,11 +840,11 @@ public abstract class CRUDUtils {
|
|||
\begin{en}
|
||||
\subsubsection{\textit{restaurant} -- client side}
|
||||
The client portion of the \textit{restaurant} library is implemented with the
|
||||
\textit{TypeScript} progamming language, an extension of \textit{Javascript}
|
||||
\textit{TypeScript} programming language, an extension of \textit{Javascript}
|
||||
offering static typing, common OOP constructs and generics support. The
|
||||
following listings describes the \textit{RESTService} class interface, which
|
||||
contains some static methods useful to exchange data asyncronously with the
|
||||
server in the form of instances of ``entity'' classes, inheriters of the
|
||||
contains some static methods useful to exchange data asynchronously with the
|
||||
server in the form of instances of ``entity'' classes, inheritors of the
|
||||
abstract class \textit{Table}.
|
||||
\end{en}
|
||||
|
||||
|
|
@ -1070,8 +1070,8 @@ export class RESTService {
|
|||
\begin{en}
|
||||
The Gantt diagram in figure \ref{fig:ganttitgmob} was not followed: the
|
||||
project was not completed within the end of May. However, the most important
|
||||
piece of software that did have to be working by the deadline was finished:
|
||||
\textit{restaurant}, with the online/offline syncronization engine and the
|
||||
piece of software that had to be working by the deadline was finished:
|
||||
\textit{restaurant}, with the online/offline synchronization engine and the
|
||||
interface and implementation of the procedures needed for generating in an easy
|
||||
fashion new sections of the app.
|
||||
\end{en}
|
||||
|
|
@ -1122,7 +1122,7 @@ export class RESTService {
|
|||
\begin{en}
|
||||
\subsection{Project phases}
|
||||
|
||||
The project phases originally established, by which start and end dates are shown on
|
||||
The project phases originally established, by which start and end dates are shown in
|
||||
the diagram in figure \ref{fig:ganttitgmob}, are described below.
|
||||
|
||||
\begin{description}
|
||||
|
|
@ -1149,7 +1149,7 @@ export class RESTService {
|
|||
algorithms used inside the library, with improvement of the last ones.
|
||||
This phase is divided in:
|
||||
\begin{description}
|
||||
\item[Architecture revising] analisis of the protocol aimed to find weak
|
||||
\item[Architecture revising] analisys of the protocol aimed to find weak
|
||||
points and possible optimisations;
|
||||
\item[\textit{restaurant} testing] trial of the changes implemented before;
|
||||
\end{description}
|
||||
|
|
@ -1184,7 +1184,7 @@ wheel balancers. This application should work as a remote desktop client
|
|||
(as \textit{TeamViewer}\footnote{TeamViewer: \url{https://www.teamviewer.com}})
|
||||
for the PC mounted inside their main product, an automatic wheel balancer
|
||||
that works with cameras. The program should allow the user to interact with the
|
||||
wheel balancing software, without needing them to exit from the veichle.
|
||||
wheel balancing software, without needing them to exit from the vehicle.
|
||||
|
||||
Since this project was urgent for the customer, development on \textit{InteGRa
|
||||
Mobile} was stopped until the end of the extended school internship period.
|
||||
|
|
@ -1267,8 +1267,8 @@ Since this project was urgent for the customer, development on \textit{InteGRa
|
|||
tablet containing the mobile app. In particular, \textit{guacamole-common-js} is
|
||||
used in the mobile app (which is built with \textit{Apache Cordova}) in order to
|
||||
make a touchscreen interface for the interacting with the remote host, while
|
||||
\textit{guacamole-common}, bundled in a small Java Web Application, toghteter
|
||||
with \textit{guacamole-server} are installed on the PC.
|
||||
\textit{guacamole-common}, bundled in a small Java Web Application, together
|
||||
with \textit{guacamole-server} is installed on the PC.
|
||||
|
||||
In addition, the tablet and the PC can share additional information through a
|
||||
WebSocket created at the same time as the connection, which is needed by some
|
||||
|
|
@ -1303,7 +1303,7 @@ Since this project was urgent for the customer, development on \textit{InteGRa
|
|||
\def\ganttargosstima{Time estimates for future \ldots}
|
||||
\def\ganttargosimpl{Implementation of the \ldots}
|
||||
\def\ganttargoszoom{Keyboard opening with zoom \ldots}
|
||||
\def\ganttargosscroll{Two finger scroll}
|
||||
\def\ganttargosscroll{Two-finger scroll}
|
||||
\def\ganttargosconf{Settings page}
|
||||
\def\ganttargoskbd{Input through native iOS or \ldots}
|
||||
\def\ganttargosdemodef{Demo to the customer}
|
||||
|
|
@ -1403,7 +1403,7 @@ Since this project was urgent for the customer, development on \textit{InteGRa
|
|||
figure \ref{fig:ganttargos}, are listed below.
|
||||
|
||||
\begin{description}
|
||||
\item[Meeting with the customer] first information exchanged aimed to
|
||||
\item[Meeting with the customer] first information exchange aimed to
|
||||
establish the project targets;
|
||||
\item[Development of the first prototype] demonstration of
|
||||
\textit{guacamole} as an effective protocol through a prototype;
|
||||
|
|
@ -1418,7 +1418,7 @@ Since this project was urgent for the customer, development on \textit{InteGRa
|
|||
open a keyboard;
|
||||
\item[Input through native iOS or Android keyboard] substitution of the
|
||||
keyboard included with \textit{guacamole-common-js} with the native one;
|
||||
\item[Two finger scroll] support for vertical two finger scrolling;
|
||||
\item[Two-finger scroll] support for vertical two-finger scrolling;
|
||||
\item[Settings page] creation of a small configuration panel, needed to
|
||||
enter the PC's IP address and port number;
|
||||
\end{description}
|
||||
|
|
|
|||
Reference in New Issue