[Suggestion] UI Changes about diskusage HOT 7 OPEN

from diskusage.

Oh i was talking specifically about UI-changes, those should not break anything.

Though i probably will not find time to implement anything major.

I know this deviates from the toppic, but isnt dropping support for android 5&6 fine? Those are nearly ten years old, and with android 7 you have to use SAF anyway.

from diskusage.

from diskusage.

What i imagine is this:

However, experimenting with the codebase, i found that this is not a trivial task. From what i see, this requires re-implementing the full user interface code, replacing all current activities with one new one. In addition to that, it also requires a more strict decoupling between the UI, the renderer and the filesystem structure.

While that is a huge task, that might ease maintenance in the future. It also allows us to experiment with different visualizations, because we just need to create a new visualization, instead of working around the current implementation.

What do you think, is this something i should move forward with? If i do, i will probably create a huge PR that replaces the old UI with the new one.

from diskusage.

from diskusage.

Do you want to replace the current UI or add another representation?

With UI i meant everything that is not a graph ;) I have experimented a bit and could make a different graph work (as a prototype), but my goal is to replicate the current version in terms of feature and looks, but in decoupled.

So for now i am going to keep the original renderer, but rework it so it works standalone, so that it becomes possible to add more, replace or change the graph without breaking the rest of the application.

from diskusage.

from diskusage.