Expand functionality to add Incident Logging Application about cargotracker

[glassfishrobot]

• Issue Imported From: javaee/cargotracker#15
• Original Issue Raised By:@glassfishrobot
• Original Issue Assigned To: @delabassee

[glassfishrobot]

@glassfishrobot Commented
Reported by reza_rahman

[glassfishrobot]

@glassfishrobot Commented
reza_rahman said:
Assigning to Bruno - many thanks!!

[glassfishrobot]

@glassfishrobot Commented
reza_rahman said:
One consideration is skipping the Java SE runtime and re-writing the incident logger to be an HTML 5/JavaScript application with off-line/sync capacities targeting mobile devices (but still usable on a desktop browser). The application would still communicate over REST with the backend.

Going this route, we would secure the application the same way we can secure the admin interface.

[glassfishrobot]

@glassfishrobot Commented
reza_rahman said:
Assigning to Vijay as discussed: https://java.net/projects/cargotracker/lists/users/archive/2013-08/message/15.

[glassfishrobot]

@glassfishrobot Commented
reza_rahman said:
Initial working version done by Vijay and reviewed. Additions to be done as discussed here: https://java.net/projects/cargotracker/lists/users/archive/2013-09/message/8. Specifically:

• Should we use jQuery, Bootstrap, Angular, etc to modernize the JavaScript/CSS?
• Is it possible to make the incident logger adaptive so that it can handle desktop browsers as well as mobile ones? I think that would make a pretty slick demo...
• Do you want to make the client-side validation a bit more robust - like some of the validations being done on the server side? Or should we keep the client side validation simple?
• Is it possible to make the form float horizontally on mobile devices? Currently there's a lot of blue "white space" towards the
  bottom that looks a little weird...
• Use the HTML 5 date/time widget instead of free text for the event time?
• Do additional REST services to get the location and voyage information? The location and voyage then could be a much more
  readable/usable drop down list. We could cache the locations/voyages so it's usable offline/does not degrade performance? We probably can't take that approach with tracking IDs since there might be too many of them (unless we look to implementing Google style intellisense).

[glassfishrobot]

@glassfishrobot Commented
reza_rahman said:
David has ported with over to JSF/the server side for now. Should revisit mobile specific use cases such as offline processing, sync and caching at a later point in time.

[glassfishrobot]

@glassfishrobot Commented
This issue was imported from java.net JIRA CARGOTRACKER-15

[thadumi]

An interesting point is your question about adding support for an offline mode. For now I'm tracking this in the issue #8 . So we can close this and open another one later.

@m-reza-rahman

[m-reza-rahman]

I think this is a very low priority issue that we can tackle after the initial Java EE 7, Jakarta EE 8 and Jakarta EE 9 issues. What David did with PrimeFaces Mobile is pretty decent.

Reza Rahman
Jakarta EE Ambassador, Author, Blogger, Speaker

Please note views expressed here are my own as an individual community member and do not reflect the views of my employer.