add issues for the demo app #33

Closed fgardt closed 1 year ago

In GitLab by @Merseleo on Mar 6, 2023, 15:14

Description

As the library is implemented (at least a first version), it is helpful to test it with a demo app. Therefor

[x] consider the mock up (see here)
[x] write issues / tasks for the demo app
[x] link issues, i. e. determine which pages need to be created first and block other

In GitLab by @Merseleo on Mar 16, 2023, 18:53

marked this issue as blocked by #38

In GitLab by @Merseleo on Mar 24, 2023, 19:20

marked the checklist item consider the mock up (see here) as completed

In GitLab by @Merseleo on Mar 24, 2023, 19:38

Ideas for the several tasks:

[x] create home page (without boxes for sensors, only sections)
- [x] add settings navigation
- [x] add live view section
- [x] add sensors section
- [x] add devices section
[x] create live view page
- [x] create box (widget) for sensor
- [x] add boxes for sensors to page
[x] create statistics page (no favorites, list of all sensors)
- [x] add navigation to historic view pages
[x] create generic historic view page
- [x] add header with info overlay
- [x] add example section
- [x] add scrollable table of data
- [x] add time interval selector
- [x] add filter drop down
- [x] add graph view
[x] create settings page (only information, prepare navigation)
[x] create info page (static)
[x] create search page with search function
- [x] add information, whether sensors are available
- [x] add function to start and stop sensors
- [x] add favorites management
[x] create page (generic) for sensor settings (with information and apply button)
- [x] add unit selector
- [x] add precision selector
- [x] add time interval selector
[x] create the general import / export page (informations, drop-down menus, ...)
- [x] create the page with the time picker for the export time interval
- [x] create pages / overlays with file selectors

@Slartibartfass2 @fgardt Do you agree with this breakdown of the app or tasks? Or you should I break down the tasks in another way? (the order must be rethought, I know) Because I am uncertain (and don't have enough knowledge about app development), whether it is possible to develop this different parts of the app (completely) separate.

In GitLab by @Slartibartfass2 on Mar 25, 2023, 16:52

I like this page-by-page approach, because we can easily implement the pages separately.

We can implement the pages as kind of templates and later connect all the pages together as soon as they are merged into main and use the plugin methods to actually fill the pages.

Prior to this we should think about how we manage states and which widgets we can reuse to avoid duplicates.

In GitLab by @Slartibartfass2 on Mar 25, 2023, 16:56

What states do we need to store which aren't stored somehow in our plugin?

What I've come up with:

Favorites
settings of historic view maybe
not sure about how this works when the app is closed

Did you come up with something else?

In GitLab by @Merseleo on Mar 25, 2023, 17:18

No, so far I think this is the only state we don't store in the library. And I would say for the beginning we can delete the state, when the app is closed.

In GitLab by @Merseleo on Mar 25, 2023, 17:21

But I don't understand what you mean with "connect all pages together"? Why don't fill the pages immediately?

Do you have any idea about the state management and reuse of widgets?

All in all, this is no limitation for start writing down the issues, because they don't contain the way how to implement it, but only what needs to be implemented.

In GitLab by @Slartibartfass2 on Mar 25, 2023, 18:17

Sorry for the missunderstanding, by that I mean the navigation. Afaik we need the other Pages classes to make the navigation work.

Maybe we can create a empty page at the beginning so that the navigation can be implemented without waiting for all pages to be merged.

I don't know enough about state management, for me further investigation would be required. Some reusable widgets might be these Sensor Boxes and the sensor list elements where you can toggle a sensor on or off.

Yes we can start writing the issues.

Also what came to mind is that we should define a directory structure so that merging all the pages together won't be a tedious work.

In GitLab by @Slartibartfass2 on Mar 25, 2023, 18:23

I propose a pages and widget directory under lib.

Maybe only widgets which are used in different pages should be put into widgets and page specific widgets directly to the according pages subfolder.

graph TD
    A[lib] --> B[pages]
    B --> C[home]
    C --> CA(home_page.dart)
    C --> CB(home_page_specific_widget.dart)
    B --> E[live-view]
    E --> EA(live_view_page.dart)
    A --> D[widgets]
    D --> DA(sensor_box.dart)
    D --> DB(sensor_toggle_element.dart)

Thoughts?

In GitLab by @Merseleo on Mar 25, 2023, 18:53

Sound good!

In GitLab by @Merseleo on Mar 27, 2023, 15:32

unassigned @fgardt

In GitLab by @Merseleo on Mar 27, 2023, 15:38

marked this issue as related to #39

In GitLab by @Merseleo on Mar 27, 2023, 16:03

@Slartibartfass2 If you have time left, you could maybe "review" some of the issues and do a rough check, whether something is missing. If not, I suggest we add all these issues to the next sprint and close this issue.

In GitLab by @Merseleo on Mar 27, 2023, 16:03

marked the checklist item write issues / tasks for the demo app as completed

In GitLab by @Merseleo on Mar 27, 2023, 16:11

marked the checklist item link issues, i. e. determine which pages need to be created first and block other as completed

In GitLab by @Slartibartfass2 on Mar 28, 2023, 13:52

I checked them and they all look good to me. I propose to add the directory structure in advance, so that the Navigation can be implemented right away.

I also added some useful links.

In GitLab by @Slartibartfass2 on Mar 28, 2023, 13:52

unassigned @Slartibartfass2

In GitLab by @Slartibartfass2 on Mar 28, 2023, 21:53

mentioned in issue smart-sensing-library#64

uulm-smart-sensing / documentation

add issues for the demo app #33

Description