alex1001xela / mobilecomputing Goto Github PK

This would help us with having clear idea when should one ID be used, and when another one, just by looking at the class.

Stacktrace:

java.lang.NullPointerException: Attempt to invoke virtual method 'org.json.JSONObject
at com.wua.mc.webuntisapp.presenter.WebUntisService.getFilters()' on a null object reference
com.wua.mc.webuntisapp.presenter.CalendarPresenter.getFilters(CalendarPresenter.java:395)
com.wua.mc.webuntisapp.view.FieldOfStudyChooser.getFieldOfStudyConfirmationButton(FieldOfStudyChooser.java:47)
com.wua.mc.webuntisapp.view.MainActivity$1.onClick(MainActivity.java:85)
android.view.View.performClick(View.java:5265)
android.view.View$PerformClick.run(View.java:21534)
android.os.Handler.handleCallback(Handler.java:815)
android.os.Handler.dispatchMessage(Handler.java:104)
android.os.Looper.loop(Looper.java:207)
android.app.ActivityThread.main(ActivityThread.java:5728)
java.lang.reflect.Method.invoke(Native Method)
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:789)
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:679)

Also:

FATAL EXCEPTION: main Process: com.wua.mc.webuntisapp, PID: 25269 java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
at com.wua.mc.webuntisapp.model.DatabaseManager.saveEventDB(DatabaseManager.java:219)
com.wua.mc.webuntisapp.presenter.CalendarPresenter.addCourse(CalendarPresenter.java:213)
com.wua.mc.webuntisapp.view.CalendarView$8.onClick(CalendarView.java:565)
android.view.View$PerformClick.run(View.java:21534)
android.os.Handler.handleCallback(Handler.java:815)
android.os.Handler.dispatchMessage(Handler.java:104)
android.os.Looper.loop(Looper.java:207)
android.app.ActivityThread.main(ActivityThread.java:5728)
java.lang.reflect.Method.invoke(Native Method)
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:789)
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:679)

Changing days needs some time in the global calendar. This can be improved by getting the whole week instead of only the current day, and then switching between the in-memory days.

There is only the title of the subject but no other info.

Yeah, they look terrible.

Look at mock-up. The first step to personal events.

We need a better way to get events from the database, because right now it is just events with no relation to a course. We need some kind of inner select or something.

Stacktrace:

java.text.ParseException: Unparseable date: " March " (at offset 0)
android.icu.text.DateFormat.parse(DateFormat.java:683)
com.wua.mc.webuntisapp.view.CalendarView$GridCellAdapter.convertStringMonthToIntegerMonth(CalendarView.java:1546)
com.wua.mc.webuntisapp.view.CalendarView$GridCellAdapter.onClick(CalendarView.java:1496)
android.view.View.performClick(View.java:5265)
android.view.View$PerformClick.run(View.java:21534)
android.os.Handler.handleCallback(Handler.java:815)
android.os.Handler.dispatchMessage(Handler.java:104)
android.os.Looper.loop(Looper.java:207)
android.app.ActivityThread.main(ActivityThread.java:5728)
java.lang.reflect.Method.invoke(Native Method)
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:789)
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:679)

I am unsure about the precision in which events are represented on the calendar. I left it at that state back then in favour of more important topics.

As it is right now, with each call to the WebUntis Server we create a new session and destroy it on response, all automatically, meaning there are minimum 3 HTTP requests per action. This made it easier for us developers during uni-time, but is in principle inefficient. We need to switch to manual session management, this would reduce the HTTP requests by a lot.

They are not saved in the database yet

It changes the GUI and the memory, but the DB still contains the information.

There is still some bug when events are have overlapping hours, can't remember in which way. We need to create multiple events with separate lengths and similar timestamps to check how they position themselves.

It would be nice to get from the database the last chosen field of study.

It's quite confusing sometimes to remember when you can use a function.

The pop-up window is too large. Also a way to close it without tapping back < would be nice.

Sometimes only the events of the current week are shown, but if you jump to the next, nothing is shown.