[mikek]

Hi,do you get the same error if you enter an invalid username/password combination ?^__^Mike

[mikek]

Hi,When you say you started the opentele-server on port 8090, do you mean that you started it directly from the command line, or did you generate a war file that you added to tomcat?In either case a way to test the server setup is trying to access the server from a browser, I would first try it from the same machine as the server is installed on, when you have verified that the URL is correct, then try it from a browser on the mobile device - just to give an indication if the issue is with the client, the server or with routing between the Android device and the server.The opentele-server is the clinician server, a good login/password combination for the clinician interface is helleandersen/helleandersen1.If you can't login with admin/admin in the Android app, then it could be because you are using the html5 android app, instead of the native android app.  The admin/admin login is for the native android app.(There are three ways to access the citizen interface, through a browser (the html5 interface), through the android html app, and through the native android app.)For reference you can see how (or use, depending on your needs) the servers look on the following URL'shttp://opentele-citizen.4s-online.dk/ - The server the native Android app needs to connect tohttp://opentele-html.4s-online.dk/ - The html5 interface, that you can use directly from a browser, and from the html android clienthttp://opentele-server.4s-online.dk/ - The clinician interfaceI hope the above helps.^__^Mike

[mikek]

Please let us know if you need help with/guides to getting the issue into Jira or with the pull request.^__^Mike

[mikek]

Hi, That looks great (even I don't understand Spanish), and yes it would probably be a good idea to check the strings in context in the running app.  The opentele2 server has an editor to create questionnaires, if you go into the Administrator Menu and select "Questionnaires" then you can see the current questionnaires, you can then click on one and select "Edit", this is also the place to create new questionnaires.The sample/test questionnaires that you see when you run the software "out of the box" are defined in "opentele2-server/grails-app/conf/BootStrap.groovy"  There is a def called "doBootstrapForEnglishTest()"  this refers to another def called "createQuestionnairesForEnglishTest" where sample English questionnaires are defined.The way to choose which bootstrap is used to seed the database in the "environments" section of the init def (search for "def init = { servletContext ->" in the BootStrap.groovy file.  (There are three environments defined per default - "development", "performance" and "test" the first one is the default one that is used when you follow the instructions on the wiki on how to build the software, the last two are used for performance test and automated test).It would probably be a good idea if we here made the selection of which bootstrap to use, depending on the language selection (defaultLocale) in the config.groovy file - but lets treat that as a separate issue.I have created a Jira issue https://issuetracker4s.atlassian.net/browse/OT-118 to log this thought about automatic selection of language for the sample questionnaires.Now, about the missing translations for the auditlog - thank you for bringing this to our attention, I have created https://issuetracker4s.atlassian.net/browse/OT-119 to track this - If you have specific questions to translations of individual strings, then I might be able to help - otherwise we have to see if someone picks the bug up and solves it. ----Now after you are happy with the translations, and if you wish to contribute them to the OpenTele project, two things are needed to get them merged in - a Jira issue (Jira is our bug/feature tracker) and a pull request with your change that refers to the Jira issue.  You create an account in our Jira (if you don't already have one) by clicking on "Sign in" in the upper right corner, and then choosing "Create account".Please feel free to add any bugs/ideas for improvements into the Jira.  Questions about the source or how to use the software are best handled here on the forum.^__^Mike

[mikek]

You are welcome.  I think the application is somehow aware of the videconference – but I think you are right that it runs separately – there has been some worries about the privacy during the actual conference.If you look at http://4s-online.dk/wiki/lib/exe/fetch.php?media=opentele:opentele_fysisk_datamodel_2.0.2.pdf page 23, there is a datamodel for a videoconference.The text on the page says (roughly translated):Model for videoconferencesThe clinician can enter measurements or receive measurements from the users tablet during a video call.The data model contains a table that is used during setting up the call (pending_conference) and entities to register the conference it self and temporary registration of measurements taken during the conference.^__^Mike

[mikek]

Yes, you can change the default locale to something else than danish in “opentele-server/grails-app/conf/config.groovy”, search for “defaultLocale”.I think it should be enough to just create the *_sp.properties files and then rebuild the software.  You might not even need to create all of them, in order to see if it is working, then you just need to find the places where they are used.https://grails.github.io/grails-doc/2.4.3/guide/i18n.html might give some background info.Keep us updated with the progress.^__^Mike

[mikek]

Unfortunately the videoconferencing part of OpenTele has some lacks in the documentation – there is no opensource video integration, and there is no description (to my knowledge) of how to do it :'(However I have been told by the guys who made the interface (and an integration of a commercial video component) that the interfaces should be clean and it should be possible to integrate with other video components.Any enlightenment on this topic would be great  🙂^__^Mike

[mikek]

Hi, The OpenTele server 2, is currently available in English and Danish, the way you switch language is by appending ?lang=en to the URL of the server.----Ex.If you have the server installed locally, and want to run it in English, the url will be: http://127.0.0.1:8080/opentele-server/login/auth?lang=enFor running it in Danish:http://127.0.0.1:8080/opentele-server/login/auth?lang=da----We would be very happy if you would like to help with translating it into Spanish, you should be able to see all the strings in the "opentele2-server/grails-app/i18n" folder and the sub folders below.^__^Mike

[mikek]

Note that more information can be found on our wiki page: http://4s-online.dk/wiki/doku.php?id=opentele3:questionnaire_editor:requirements

[mikek]

Happy to help  🙂  You are right it will not work if you just copy that code for the WebkitActivity – I'm no JNI or Android expert, but I guess this is because when setting up the native calls we actually instantiates the activity object, but not with the correct arguments (for the constructor) or not in the correct context – hence when we try to launch the activity it doesn't actually show on the display.  There are other ways to use the JNI or initialize the activity object, but if you found a solution that works, then I'll not dig into it now.Let me know if I should search for a solution.^__^Mike

[mikek]

Sure, first you make a call from the onDestroy() function in the WebkitActivity back to the C++ code (through JNI), then you call the Qt function QCoreApplication::exit() from this native c++ function (the function you called from onDestroy())You can get inspired on making JNI calls from the PlatformWebBrowser constructor where the JNI function for the JS interface are defined.Let me know if you need more detailed info.^__^Mike

[mikek]

Hi, I'm assuming we are talking about the Android platform here, as the AndroidManifest.xml is mentioned in the question.Yes, the browser reloads when the orientation is changed, that is standard behavior for the browser.  And you are right that this could interfere with the reading of measurements, I have opened a Jira on this: https://issuetracker4s.atlassian.net/browse/SDC-26You should be able to lock the rotation in the demo app by adding an android:screenOrientation="landscape", but you need to ensure it's done in the webkit activity, like this:

Code:

                           

(This works on a Samsung S4, I haven't tested on other platforms)Changing it in the QML or in the qt part of the code will not affect the webkit browser (which is a native Android component in the demo application).^__^Mike

[Author]

Posts