FMXInno - Windows Fluent Design Installer UI for Inno

[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.


.

[audiofeel]

Originally Posted by BLACKFIRE69

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.
.

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';

[audiofeel]

How did I understand that it is better to write the source text in UTF 8, that is, only Latin characters? Does he not understand ANSI , that is, the Cyrillic alphabet, for example?

[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;

[audiofeel]

Originally Posted by BLACKFIRE69

function wGetUserUILanguageISO639: WideString;

Everything is just fine. now you need to figure out the special characters, if they come across in the text, then it will all look like in this table

'              %27
(              %28
)              %29
*              %2A
+              %2B
,              %2C
-              %2D
.              %2E
/              %2F

https://www.degraeve.com/reference/urlencoding.php

[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.

[audiofeel]

Originally Posted by BLACKFIRE69

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.

.

Oh, and who is it that we have here nervously lit a cigarette on the sidelines? Manufacturers of third-party widgets for Windows... But seriously, I'm for any movement. There is one question left. Will national "GPT" be supported? Such as Yandex? This is all in the plane of inaccessibility in some countries of "Google GPT" (even via VPN). And all this will terribly slow down the popularity of these new introductions

[audiofeel]

Originally Posted by statics

Is there any way to include DSG compatibility in LizzardInstaller?
The changelog states that Cesar includes this module, but I can't find the scripts to use as a base

I found it on a flash drive. but the date is old. April 23rd.

[audiofeel]

A small example of the GUPTA script is stylized for Windows 8. Everything is as usual, the selection of components, folders, comparison of system requirements, a custom form of deletion.

[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;

.