Hi, we are based in Oslo. Tomorrow at 11.30 am GMT+1 is fine.
The topics for the call from our side would mainly be figuring out how collaboration efforts could be implemented. Do you have an agenda that we can prepare a little for? Simen On Wed, Jan 20, 2016 at 1:35 PM, Vanya Seth <van...@thoughtworks.com> wrote: > Hi Araz and Simen > > Thanks for the response. Can we have a call tomorrow (Thursday)? > Theo (Product Owner) from client side would like to join the call. He's > based out of Berlin. So, 11.30 am GMT + 1 is ok for a call?? Am not sure > where you guys are currently placed. > If this time is not convenient please let me know a time that suits you. > > Regards > Vanya > > On Tue, Jan 19, 2016 at 8:50 PM, Simen Skogly Russnes < > simen.s.russ...@gmail.com> wrote: > >> Hi Vanya, >> >> glad to see you are interested in the apps and the SDK. Arranging a call >> would be great. Would you perhaps be available already this week? >> >> Regards, >> Simen >> >> On Tue, Jan 19, 2016 at 12:35 PM, Vanya Seth <van...@thoughtworks.com> >> wrote: >> >>> Hi Araz >>> >>> Thanks for the response. Really appreciate it. >>> Its good to know that the fixes will be out with the next DHIS release. >>> >>> But I am looking more from the aspect of collaboration wherein we can >>> share the load of fixing these issues. Can you let me know what is the >>> best way to take this forward? We are happy to jump on a call if required. >>> But given our Pilot (Evaluation ) timelines we would be keen to close >>> them in the next 2 weeks. >>> >>> FYI...As suggested by you we are right now working off the legacy >>> branch. (Sultan Ahamer from our team mailed regarding the failing build >>> earlier) >>> >>> *Details about the issue:* >>> >>> *I]* Period labels are overlapping (see this example: >>> In the DHIS Web App: >>> 2015-5-15 to 2015-5-21 >>> 2015-5-7 to 2015-5-14 >>> >>> (In the web app for a weekly dataset if you look at the date range, the >>> next week starts from the next day, where the previous week ends.) >>> >>> In the Android App: >>> 2015-5-14 to 2015-5-21 >>> 2015-5-7 to 2015-5-14 >>> (But in the Android app, the next week period label starts from the same >>> day where the previous week ends. For a field user this might be confusing >>> in terms of where to enter the data for the day which appears in both the >>> weeks.) See the screenshot below. The overlap has been highlighted in red. >>> [image: Inline image 1] >>> >>> Regards >>> Vanya >>> >>> On Tue, Jan 19, 2016 at 1:40 PM, Araz Abishov < >>> araz.abishov.g...@gmail.com> wrote: >>> >>>> Hello Vanya, >>>> >>>> It is really good to know that you are planning to start using android >>>> applications. I have answered some questions below: >>>> >>>> *[I] *We opened an issue in GitHub as well. But unfortunately no one >>>>> has responded yet. >>>>> https://github.com/dhis2/dhis2-android-datacapture/issues/12 >>>> >>>> This issue will be fixed in upcoming release. I have created a >>>> milestone (April 1 - release of DHIS2 2.23) and assigned bug to it. >>>> >>>> *[I]* A dropdown field allows text entry (manually from the keyboard). >>>>> Rather this field should not allow any data entry. >>>> >>>> This is more a design issue, now we picked up another approach, which >>>> eliminates this problem. >>>> >>>> *I]* Period labels are overlapping (see this example: >>>> >>>> Could you please explain the problem in more details? >>>> >>>> *[E]* If data is not synced (sync failed), if it’s easy to suggest an >>>>> action to the user (something like “Please try again later or restart >>>>> app”). >>>> >>>> Create new issue on GitHub: >>>> https://github.com/dhis2/dhis2-android-datacapture/issues/15 >>>> >>>> *[E]* A logout confirmation message ("Are you sure you want to log >>>>> out") is missing(although its present in the Event Capture app) >>>> >>>> Create new issue on GitHub: >>>> https://github.com/dhis2/dhis2-android-datacapture/issues/16 >>>> >>>> *Q] *Is there a limit on the number of columns that can be >>>>> accommodated in the mobile app? >>>> >>>> At the moment this number (4) is hardcoded into app. But we are working >>>> on more flexible solution which will allow to choose amount of columns to >>>> be show to user. >>>> >>>> *[Q] *Is there any upper limit on the time for which the device can be >>>>> offline? >>>> >>>> No, there is no time limit for being in offline mode. >>>> >>>> *[Q]*Is there any upper limit on the number of events that can show >>>>> up in the grid (for view purposes)? >>>> >>>> Initially event capture downloads 200 events from the server and then >>>> also shows all events which were created locally on device. The problem is >>>> that if you will have too many events, application will become slower. >>>> >>>> *[I]* If an event fails to sync, on clicking on the sync icon, the >>>>> full stack trace(exception) shows up. It's not a user friendly message. >>>>> >>>> >>>> But it is the only way at the moment we can get feedback from the users >>>> with sync errors. In new version, we are planning to change it to something >>>> more user friendly. >>>> >>>> *[I]*The spinner doesn't stop even if the device is offline. (Swiping >>>>> initiates a sync, but in offline conditions, it should raise a message) >>>> >>>> *[I] *While offline, when we attempt login the message that comes up >>>>> is not user friendly.And same holds true for the message which comes when >>>>> the app times out while trying to log in. >>>> >>>> https://github.com/dhis2/dhis2-android-eventcapture/issues/64 >>>> >>>> *[I] *There are no sync related notifications/messages (When we click >>>>> on the sync icon in offline as well as online mode) >>>> >>>> https://github.com/dhis2/dhis2-android-dashboard/issues/15 >>>> >>>> If you have any questions, do not hesitate to ask. >>>> >>>> Best regards, >>>> Araz >>>> >>>> >>>> On Mon, Jan 18, 2016 at 10:09 AM, Vanya Seth <van...@thoughtworks.com> >>>> wrote: >>>> >>>>> Hi Dhis-Devs >>>>> >>>>> We are looking at evaluating three Android Apps (Data capture, Event >>>>> Capture and Dashboards) in couple of months (around March end/Early April) >>>>> for MSF (OCA). >>>>> We have been playing around with the apps and there are quite a few >>>>> issues and enhancements that we might be interested in >>>>> . >>>>> It would be good if we could get some clarity on the roadmap and if at >>>>> all they are on the priority to be fixed/implemented (We are happy to fix >>>>> ourselves as well, but its good to know the agenda of the dev team). >>>>> >>>>> Here is a list of some issues/questions and enhancements that might >>>>> make sense. >>>>> *[Q] : Question* >>>>> *[I] : Issue* >>>>> *[E] : Enhancement* >>>>> >>>>> *Data Capture App:* >>>>> *1. [I] *We opened an issue in GitHub as well. But unfortunately no >>>>> one has responded yet. >>>>> https://github.com/dhis2/dhis2-android-datacapture/issues/12 >>>>> 2. *[I]* A dropdown field allows text entry (manually from the >>>>> keyboard). Rather this field should not allow any data entry. >>>>> 3. *[I]* Period labels are overlapping (see this example: >>>>> In the DHIS Web App: >>>>> 2015-5-15 to 2015-5-21 >>>>> 2015-5-7 to 2015-5-14 >>>>> >>>>> In the Android App: >>>>> 2015-5-14 to 2015-5-21 >>>>> 2015-5-7 to 2015-5-14 >>>>> >>>>> 4. *[E]* If data is not synced (sync failed), if it’s easy to suggest >>>>> an action to the user (something like “Please try again later or restart >>>>> app”). >>>>> 5. *[E]* A logout confirmation message ("Are you sure you want to log >>>>> out") is missing(although its present in the Event Capture app) >>>>> >>>>> >>>>> *Event Capture App* >>>>> *1. [Q] *Is there a limit on the number of columns that can be >>>>> accommodated in the mobile app? >>>>> 2. *[Q] *Is there any upper limit on the time for which the device >>>>> can be offline? >>>>> 3. *[Q]*Is there any upper limit on the number of events that can >>>>> show up in the grid (for view purposes)? >>>>> 4. *[I]* If an event fails to sync, on clicking on the sync icon, the >>>>> full stack trace(exception) shows up. It's not a user friendly message. >>>>> 5. *[I]*The spinner doesn't stop even if the device is offline. >>>>> (Swiping initiates a sync, but in offline conditions, it should raise a >>>>> message) >>>>> 6. *[I] *While offline, when we attempt login the message that comes >>>>> up is not user friendly.And same holds true for the message which comes >>>>> when the app times out while trying to log in. >>>>> >>>>> >>>>> *Dashboard App* >>>>> *1.[I] *There are no sync related notifications/messages (When we >>>>> click on the sync icon in offline as well as online mode) >>>>> >>>>> Regards >>>>> Vanya >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> With Regards >>>>> ThoughtWorks Technologies >>>>> Hyderabad >>>>> >>>>> --Stay Hungry Stay Foolish!! >>>>> >>>>> _______________________________________________ >>>>> Mailing list: https://launchpad.net/~dhis2-devs >>>>> Post to : dhis2-devs@lists.launchpad.net >>>>> Unsubscribe : https://launchpad.net/~dhis2-devs >>>>> More help : https://help.launchpad.net/ListHelp >>>>> >>>>> >>>> >>> >>> >>> -- >>> With Regards >>> ThoughtWorks Technologies >>> Hyderabad >>> >>> --Stay Hungry Stay Foolish!! >>> >>> _______________________________________________ >>> Mailing list: https://launchpad.net/~dhis2-devs >>> Post to : dhis2-devs@lists.launchpad.net >>> Unsubscribe : https://launchpad.net/~dhis2-devs >>> More help : https://help.launchpad.net/ListHelp >>> >>> >> > > > -- > With Regards > ThoughtWorks Technologies > Hyderabad > > --Stay Hungry Stay Foolish!! >
_______________________________________________ Mailing list: https://launchpad.net/~dhis2-devs Post to : dhis2-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp
