MX-23 Raspberry Pi comes out of the garage

[dolphin_oracle]

Working on the flatpak stuff right now.

[Jerry3904]

OK.

[Jerry3904]

Two follow-up points:

1) I wasn't interested in changing the function of the "front-end," just its look--as I spelled out this morning a couple of posts back.
2) Are you talking about piwiz? If yes, I see a post on StackExchange where somebody asks himself how he would start it up automatically at next boot, and answers himself:

creating a file in /etc/xdg/autostart, the image comes with piwiz.desktop in that directory.

Is that of any relevance to your question?

[dolphin_oracle]

no, once we are logged in its too late. the usual pi startup happens before login and lets you choose a user name, etc... its how the current spin's user account in now "demo" rather than "raspberrypi"

for the record, working on the pi spin is very labor intensive, so if I take a suggestion wrong its because I just see more work for myself.

[Jerry3904]

That's how I understood it.

So maybe we should just stop for a while. We have a working alpha and we can always come back at some later point if still interested.

[dolphin_oracle]

here is a link to a biuld of mx-packageinstaller that should enable flatpaks on the arm64 arch. please test.

https://drive.google.com/file/d/1uQHhSP ... drive_link

[dolphin_oracle]

here is the code for the colors in the oobe:

Code: Select all

const bool defskin = (!getenv("QT_QPA_PLATFORMTHEME") && !getenv("XDG_CURRENT_DESKTOP"));
    if (defskin) {
        // The default style in the OOBE environment is hideous and unusable.
        QApplication::setStyle("cde"); // Qt docs say do this before the QApplication instance.
        QPalette pal;
        pal.setColor(QPalette::Window, Qt::black);
        pal.setColor(QPalette::WindowText, Qt::white);
        pal.setColor(QPalette::Base, Qt::black);
        pal.setColor(QPalette::AlternateBase, Qt::black);
        pal.setColor(QPalette::Text, Qt::white);
        pal.setColor(QPalette::Button, Qt::black);
        pal.setColor(QPalette::ButtonText, Qt::white);
        pal.setColor(QPalette::BrightText, Qt::white);
        pal.setColor(QPalette::Disabled, QPalette::Text, Qt::darkGray);
        pal.setColor(QPalette::Disabled, QPalette::WindowText, Qt::darkGray);
        pal.setColor(QPalette::Disabled, QPalette::ButtonText, Qt::darkGray);
        pal.setColor(QPalette::Highlight, Qt::lightGray);
        pal.setColor(QPalette::HighlightedText, Qt::black);
        pal.setColor(QPalette::ToolTipBase, Qt::black);
        pal.setColor(QPalette::ToolTipText, Qt::white);
        pal.setColor(QPalette::Link, Qt::cyan);
        QApplication::setPalette(pal); // Qt docs say do this after setting the style.
    }

as you can see its mostly white and blacks, with some darkgray thrown in for disabled items. I think the values are pretty self-explanatory, so feel free to suggest alternates.

[dolphin_oracle]

attached are the two translated raspi-config and rasp-documentation desktop files.

I presume at least the raspi-config one should depend on the raspi-config package. what about the rasp-documentation one?

and is "sudo raspi-config" correct? might be, but I'm not sure, raspberrypiOS does weird things with sudo.

[Jerry3904]

attached are the two translated raspi-config and rasp-documentation desktop files.

I presume at least the raspi-config one should depend on the raspi-config package. what about the rasp-documentation one?

and is "sudo raspi-config" correct? might be, but I'm not sure, raspberrypiOS does weird things with sudo.

raspi-documentation just launches a browser to the documentation website, and sudo raspi-config is correct, thanks.

[Jerry3904]

here is the code for the colors in the oobe:

Code: Select all

const bool defskin = (!getenv("QT_QPA_PLATFORMTHEME") && !getenv("XDG_CURRENT_DESKTOP"));
    if (defskin) {
        // The default style in the OOBE environment is hideous and unusable.
        QApplication::setStyle("cde"); // Qt docs say do this before the QApplication instance.
        QPalette pal;
        pal.setColor(QPalette::Window, Qt::black);
        pal.setColor(QPalette::WindowText, Qt::white);
        pal.setColor(QPalette::Base, Qt::black);
        pal.setColor(QPalette::AlternateBase, Qt::black);
        pal.setColor(QPalette::Text, Qt::white);
        pal.setColor(QPalette::Button, Qt::black);
        pal.setColor(QPalette::ButtonText, Qt::white);
        pal.setColor(QPalette::BrightText, Qt::white);
        pal.setColor(QPalette::Disabled, QPalette::Text, Qt::darkGray);
        pal.setColor(QPalette::Disabled, QPalette::WindowText, Qt::darkGray);
        pal.setColor(QPalette::Disabled, QPalette::ButtonText, Qt::darkGray);
        pal.setColor(QPalette::Highlight, Qt::lightGray);
        pal.setColor(QPalette::HighlightedText, Qt::black);
        pal.setColor(QPalette::ToolTipBase, Qt::black);
        pal.setColor(QPalette::ToolTipText, Qt::white);
        pal.setColor(QPalette::Link, Qt::cyan);
        QApplication::setPalette(pal); // Qt docs say do this after setting the style.
    }

as you can see its mostly white and blacks, with some darkgray thrown in for disabled items. I think the values are pretty self-explanatory, so feel free to suggest alternates.

Thanks for that challenging data, I will take a look. Just as a reminder: the only two issues Chris and I raised were %screen of window (=less than 100%) and image replacement of first screen (logo instead of spinner).