FMXInno - Windows Fluent Design Installer UI for Inno

[Jahan1373]

Originally Posted by BLACKFIRE69

oh boy, are you serious? sorry to say this but you need to have common sense. yes, indeed, texts with a font color close to white is difficult to see on a white background or vice versa. so what's the magic here?

Why is yellow a problem?
Why colors with a little white in them are not readable
Why do some greens have problems?
FF AD FF 2F
FF FF FF 00
You are the great designers of the forum
Why is there no such problem in similar facilities?

[BLACKFIRE69]

Originally Posted by Jahan1373

I mentioned the list of problematic colors, except for white and black, other colors have problems. I tested all the installed colors one by one.

- i mean colors that are close to the white color, not the exact white. colors like 'Aliceblue', 'AntiqueWhite', 'Azure', etc., that you marked are not very bright colors; they are very close to the white color.

Originally Posted by Jahan1373

But the manufacturer just says that I have to learn to design. You are a designer
If this problem is not solved, we will all face problems.

- no one will face any issue with colors except you.

Originally Posted by Jahan1373

Why should green have a problem with white, but the manufacturer does not agree

- green (FF 00 80 00) color is just fine.

[BLACKFIRE69]

Originally Posted by Jahan1373

Why is yellow a problem?
Why colors with a little white in them are not readable
Why do some greens have problems?
FF AD FF 2F
FF FF FF 00
You are the great designers of the forum
Why is there no such problem in similar facilities?

i can't believe this. there's no problem with the colors; the only thing is that some colors are hard to see on a white background. Please, grow up.


1. FF AD FF 2F
2. FF FF FF 00

.

[Jahan1373]

Originally Posted by BLACKFIRE69

i can't believe this. there's no problem with the colors; the only thing is that some colors are hard to see on a white background. Please, grow up.


1. FF AD FF 2F
2. FF FF FF 00

.

I'm glad I didn't grow up with a programmer.
That part should always be black to be readable
My problem was mostly only on Autoran's page. Thank you again. Good night my friend

[BLACKFIRE69]

Originally Posted by audiofeel

@BLACKFIRE69.A question about the Google translator. Why does he add extra characters to the translation? and the translation differs from the result of an online translator?

Here is my code.

StatusLB.Text(GoogleTranslate('Welcome to Installation', 'en', 'ru'));

And that's what happens online (not a single mistake in meaning).
Добро пожаловать в установку.

And that's what happens through the function.
Добро пожаловать%20to%20Установка

And another question.... how do I get the language code where the installation is running?

the decoding issue was fixed, but it seems like the translated output is incorrect. this is out of my hands because it's up to Google's APIs. we'll see what we can do about it.


.

[BLACKFIRE69]

Originally Posted by audiofeel

StatusLB.Text(GoogleTranslate('WelcomeToInstallation', 'en', 'en'));

yes it seems like it's working without spaces, (hey Google, what the f*ck? ),


but we cannot use it that way. i just updated the Google API, and now it works.


.

[BLACKFIRE69]

Originally Posted by audiofeel

Then one more counter question. how do I get the correct geocode from the system from where the installer is launched consisting of only two letters, that is, the language code, these functions, in my opinion, do not cause it, but only the full name of the country? = ISO-639

function GetUILanguage: Integer;
function wGetUserCountryName: WideString;
external 'wGetUserCountryName@files:FMXInno.dll stdcall delayload';

function wGetUserUILanguageISO639: WideString;

[BLACKFIRE69]

@Tihiy_Don,

- Updated FToggleCheckBox.FontColor method.

[Tihiy_Don]

Originally Posted by BLACKFIRE69

@Tihiy_Don,

- Updated FToggleCheckBox.FontColor method.

Thanks, everything is working as it should now.

[BLACKFIRE69]

The FMXInno Dev is getting new features daily. guys, i need your thoughts on the following specific features, as some of them are extra features and may not be necessary for every user in our FMXInno community. if you want these features in the final release, let me know.

1. Desktop Widgets:

* Similar to MacOS Sonoma, these widgets will be positioned on the active desktop,
  not on the installer interface.

-- Includes CPU / RAM / DISK / Network / Battery usage.
-- Temperature.

-- (The weather widget is currently in the development stage, not fully finished)

-- Clock (available in both Digital and Analog).
-- Image gallery slideshow.
-- Installation status: Remaining / Elapsed time, Installing speed, etc.
-- Users can create custom widgets as desired.
-- Fully customizable.

2. Co-Pilot sidebar Panel:

* Similar to Windows Co-pilot, Co-pilot sidebar will be shown in an extended space of 
  the installer on the left or right. meaning, the installer will automatically be 
  resized (expanded/collapsed) when the Co-pilot side-bar is activated/deactivated.

-- Powered by GPT-3.5 Turbo (paid users can use GPT-4 +).
-- DALL-E is not yet available (even for paid users).

-- Ability to define custom error codes or grammar queries for the corresponding
   installer. so, the Co-pilot will describe these errors or specific statuses and 
   recommend suggestions when the user asks about them.

-- By default, an animated image/button (like Apple's Siri) will indicate the 
   Co-pilot on the installer until the user changes it.

-- Fully customizable.

.

[Masquerade]

@Blackfire69
They look AWESOME. Such modern style features.

[Behnam2018]

Hi audiofeel Thank you very much for your 👌

[BLACKFIRE69]

FMXInno - Installer template

-- A common question that the FMXInno community always asks is whether there's a tutorial or guidance to create their own installer from scratch using FMXInno. however, there's currently no such tutorial because there're many areas to cover for beginners, making it a challenging task.

-- A possible and effective solution, i believe, is to provide a common template. this way, people can use it as a base and make changes on top of it until they gain enough experience to build their own installer.

-- Take the following provided script as the template; i've tried to keep everything simple and included average features to match modern styles. also, study the examples included in the attachment to the first post for more information.

-- If you've any questions or if anything is unclear, feel free to ask me or the FMXInno community. we'd be happy to help you.

Features:

* Splash: Static png
* Music: Equalizer
* Taskbar: Preview / Progress
* Buttons: Botva2-Like
* ProgressBar: DotGauge / Botva2-Like / ThinProgressBar

* Installer: Background image
* Browse Dir: Fluent UI
* Uninstaller: Background image

* Shortcut: Desktop / StartMenu
* ISArcEx: Srep+lolz

.

[BLACKFIRE69]

i've added two new functions to retrieve the build date of the FMXInno library. i hope they'll be helpful in some cases.

function wGetFMXInnoBuildDate: Integer;
procedure wGetFMXInnoBuildDateEx(var YearW, MonthW, DayW: Word);

1. Method - 01

function FMXInnoBuildDate_1: String;
var
  YearW, MonthW, DayW: Word;
begin
  wGetFMXInnoBuildDateEx(YearW, MonthW, DayW);

  Result := Format('Build Date:  %d-%d-%d', [YearW, MonthW, DayW]);
end;

2. Method - 02

function FMXInnoBuildDate_2: String;
var
  YearW, MonthW, DayW: Word;
  EncodedDate: Integer;
begin
  EncodedDate := wGetFMXInnoBuildDate;

  YearW   :=  EncodedDate shr 9;
  MonthW  := (EncodedDate shr 5) and $0F;
  DayW    :=  EncodedDate and $1F;

  Result := Format('Build Date:  %d-%d-%d', [YearW, MonthW, DayW]);
end;

.

[hitman797]

@BLACKFIRE69, can you add these two events to the form object.
FForm:

    procedure OnActivate(Event: TNotifyEvent);
    procedure OnDeactivate(Event: TNotifyEvent);