628
edits
Changes
Jump to navigation
Jump to search
Line 26:
Line 26: − + − Why use this? Can be a solution easily portable to android or to a school server.+ − Downsides:+ + + + + + + + + + + + + +
→Actual Implementation (JournalShare 2)
The client use a html page and javascript to request the data needed as json, and format it as needed.
The client use a html page and javascript to request the data needed as json, and format it as needed.
The activity starts the server only when is not joining another xo, if joining connect to the webserver through a
The activity starts the server only when is not joining another xo, if joining connect to the webserver through a StreamTube
Pros:
* Can be a solution easily portable to android or to a school server.
* A web view provide flexibility to experiment. Can be accessed using any browser pointing to http://0.0.0.0:2500/web/index.html to develop.
* Different messages needed by collaboration are easy to implement
Cons:
* We need a mechanism to notify to the clients they should update the view.
* A web view provide less control over the ui than the gtk controls.
Not implemented yet:
*
*
Known Bugs:
* When a user try to download, the ui is not responsive and do not show the alert until the download finish. The download manager is copied from Browse activity, but I don't know why is not working ok.
= More info =
= More info =