ProGUI V3 Alpha 4 Ready for testing!

[Skipper]

Hi Chris,

this seems to work just fine on a Win11/Xeon box, and as you documented: showing the Win10 GUI emulation.

[PrincieD]

Hi Chris,

this seems to work just fine on a Win11/Xeon box, and as you documented: showing the Win10 GUI emulation.

That's excellent, thanks Skipper!

[PrincieD]

Kind of wondering how best to solve an ease of use case. ProGUI V1xx used ToolBarImageButtonEx(ButtonID.l, Text$, *NormalImageID, *HotImageID, *DisabledImageID, Style.l). Where you would manually load in your images. Now it's all CSS .. ToolbarAddButton(name.s, text.s), Toolbar has a class and each button has a name so you edit the CSS for loading in an image...

[pjay]

Hi Chris,

Tested here (on Win 11 x64); Looked great, was smooth & reactive to all resizing I tried, great to see

Is the UI layout logic your own, or is there some example PB code on the forum for it?

[PrincieD]

Hi Chris,

Tested here (on Win 11 x64); Looked great, was smooth & reactive to all resizing I tried, great to see

Is the UI layout logic your own, or is there some example PB code on the forum for it?

That's great to hear pjay! The UI layout logic is all my own. There's a basic layout with absolute positioned widgets, a flex layout (with all the features of a CSS Flexbox and a grid layout (with all the features of a CSS Grid layout). The skinned window resizing uses my own custom double buffered "window" compositor which eliminates all of the jumping/jittering/tearing you would normally see when resizing a DirectX window (so good to hear that's all working smooth and reactive!).

[PrincieD]

Hi guys, got the little exe app icon working in the top left of the Titlebar widget now (for full window skinning). There's a new LoadImgResource(Path.s, *lpName, *lpType, Flags = #Null) command in the GFX API which will load an icon into an img from an exe/dll resource (group icons working only at the moment) - it mimicks the Win32 commands (as this will be Windows only). So an empty Path will use the the current process exe (Hmodule). And the CSS skin background property "url()" function now recognizes a "url('exe-icon')" path which will either use what ever exe icon you've specified in PB's compiler options or the default app icon from 'user32.dll'. So the Titlebar widget CSS currently looks like this:

Code: Select all

SkinSetValue("exe-icon", "", "", "background", "url('exe-icon') no-repeat center")

[PrincieD]

Hi guys!

Delays and delays! fixed a couple of rare crashes. And a bug with with how drop-shadows are calculated with full window skinning. So I'm getting the Windows 11 skin ready now

[le_magn]

Hi PrinceD, congratulations on all the work you're doing with ProGUI. I was wondering if you have a general idea of when the first release will be ready. Thanks.

[pjay]

The UI layout logic is all my own. There's a basic layout with absolute positioned widgets, a flex layout (with all the features of a CSS Flexbox and a grid layout (with all the features of a CSS Grid layout).

You've done a great job with it

[PrincieD]

Hi PrinceD, congratulations on all the work you're doing with ProGUI. I was wondering if you have a general idea of when the first release will be ready. Thanks.

Thanks le_magn I'll release another alpha in the next few days (just sorting the Windows 11 skin and how auto skin selection will work) and then the first beta will be released in 2 or 3 weeks where it will be on sale. Development should be quite rapid with the "pro" widgets now that the full window skinning code is pretty much working solidly (it's taken me months to get this working correctly but it's a solid foundation, hopefully )

The UI layout logic is all my own. There's a basic layout with absolute positioned widgets, a flex layout (with all the features of a CSS Flexbox and a grid layout (with all the features of a CSS Grid layout).

You've done a great job with it

Thanks pjay! a lot of work has gone into it

[PrincieD]

Windows 11 Skin WIP:



Still trying to nail the drop-shadow, could be a litte darker on the bottom edge. Bare in mind this is a worse case scenario on a pure white background.

Currently using 2 CSS box-shadow layers:

Code: Select all

SkinSetValue("window", "", "", "box-shadow", "0 0px 42px rgba(0, 0, 0, 0.179), 0 30px 66px rgba(0, 0, 0, 0.18)")

The trouble is Windows11 uses some weird inverse trapezoid drop-shadow that can't be replicated perfectly with CSS. I'm kind of thinking fuck it - you can't tell the difference unless you do a side by side comparisson on a pure white background.

[PrincieD]

I suppose the good thing is if you want more perfection you can edit the skin yourself lol

[PrincieD]

This is how it should look (ignore the window border color etc.. just the drop-shadow):

[PrincieD]

I think I might need a third CSS small drop-shadow layer just to make it "pop". Actually no, I'm not gunna spend anymore time on this - it's good enough (and can always be tweeked at a later date). Getting the next alpha released is more important

[PrincieD]

Alpha 4 release with a hard coded Windows 11 skin? I'ts still an alpha? .. yep sod it it's not perfect (plus the windows 11 skin in it's current state should work on Windows 10) - and look like windows 11. Yep sod it I'll get this ready tomorrow