Refactor code and add scrollbar

[hsbasu]

• Load css from css file instead of hard-coding it as python. Provides better readability in IDEs
• Remove eol spaces
• Fix inconsistent tab spacing
• Remove excutable permission from mousam.in, meson makes it excutable during install for all packaging methods

[hsbasu]

@amit9838 the snap file is available here.

[amit9838]

can you also attach .flatpak file

[hsbasu]

can you also attach .flatpack file

Flatpak does not generate a file. At least I couldn't find any. You can test using these commands:

flatpak-builder --user --install --force-clean builddir io.github.amit9838.mousam.json
flatpak run io.github.amit9838.mousam

[amit9838]

Can you try this.
https://unix.stackexchange.com/questions/695934/how-do-i-build-a-flatpak-package-file-from-a-flatpak-manifest

flatpak-builder build/ io.github.amit9838.mousam.json

flatpak build-export export build

flatpak build-bundle export mousam.flatpak io.github.amit9838.mousam.json

Above command will ganarate mousam.flatpak in the current dir (project dir)
can be installed using below command
flatpak install mousam.flatpak

Alternatively you can generate .flatpak package using gnome-builder.
Just follow the sequence

[hsbasu]

Can you try this. https://unix.stackexchange.com/questions/695934/how-do-i-build-a-flatpak-package-file-from-a-flatpak-manifest

flatpak-builder build/ io.github.amit9838.mousam.json

flatpak build-export export build

flatpak build-bundle export mousam.flatpak io.github.amit9838.mousam.json

Above command will ganarate mousam.flatpak in the current dir (project dir) can be installed using below command flatpak install mousam.flatpak

Alternatively you can generate .flatpak package using gnome-builder. Just follow the sequence

This is a better way. I think I'll create a bash script called test for local testing purpose.

[hsbasu]

@amit9838 Reverted back the call for css styles to main.py. Ready for squash and merge.

[amit9838]

can you attach .flatpak file, may be zip it first before uploading

[hsbasu]

mousam.flatpak.gz @amit9838

[amit9838]

Archive.zip
@hsbasu I'm attaching some ss here, with your codebase, and also by adding scroll_policy with diff screen sizes.
I think scroll is not going to work here.

[hsbasu]

Archive.zip @hsbasu I'm attaching some ss here, with your codebase, and also by adding scroll_policy with diff screen sizes. I think scroll is not going to work here.

Sorry I didn't get this. Where do you want me to attach the scroll bar?

[amit9838]

I mean simply adding the scrollbar is not the solution for this problem. We need to check what else we can do here.

[hsbasu]

On low res displays the part of the window is going out of display. It is impossible to view the outliers no matter how you move the window towards top or bottom or left or right. This happens because the cards are not rearranging and/or resizing itself. One temporary fix to view the unviewable parts is to add a scroll bar. For which even though only part of the app is visible, at least by scrolling other unviewable parts will be visible.

Edit: GTK is not known to be a resolution friendly ui framework. For the app to work on any display resolution you might consider flutter. Or rearrange and /or resize the cards and their widths so that full portion of the app is visible in the width direction.

[hsbasu]

@amit9838 can I suggest something? The discussions here are getting longer. Would you mind joining in Telegram if you use Telegram? Just ping me with id: hsbasu or the channel mamolinux

[amit9838]

On low res displays the part of the window is going out of display. It is impossible to view the outliers no matter how you move the window towards top or bottom or left or right. This happens because the cards are not rearranging and/or resizing itself. One temporary fix to view the unviewable parts is to add a scroll bar. For which even though only part of the app is visible, at least by scrolling other unviewable parts will be visible.

Edit: GTK is not known to be a resolution friendly ui framework. For the app to work on any display resolution you might consider flutter. Or rearrange and /or resize the cards and their widths so that full portion of the app is visible in the width direction.

Ya, Gtk sucks, but now it has improved a lot. So if we are going to build some complex ui, it can be hard to cover all the aspects. So i think it better to foucs on the core part first.
And for the current problem.
if you see number of user using 1366x768 displays are very rare, so for now lets keep it side we'll fix it in future.

[hsbasu]

On low res displays the part of the window is going out of display. It is impossible to view the outliers no matter how you move the window towards top or bottom or left or right. This happens because the cards are not rearranging and/or resizing itself. One temporary fix to view the unviewable parts is to add a scroll bar. For which even though only part of the app is visible, at least by scrolling other unviewable parts will be visible.
Edit: GTK is not known to be a resolution friendly ui framework. For the app to work on any display resolution you might consider flutter. Or rearrange and /or resize the cards and their widths so that full portion of the app is visible in the width direction.

Ya, Gtk sucks, but now it has improved a lot. So if we are going to build some complex ui, it can be hard to cover all the aspects. So i think it better to foucs on the core part first. And for the current problem. if you see number of user using 1366x768 displays are very rare, so for now lets keep it side we'll fix it in future.

Okay. I'll remove the scroll bar part as well.

[hsbasu]

@amit9838 Removed the scroll bar.