|
Sorry, but those buttons date the app to at least ten years ago, the title font even more like 30 years (I know because I was there). The icons are nice, but need more alpha channel to prevent jaggies.
|
|
|
|
|
I agree totally with this. Like it or not, the UI everyone understands looks like Word 2002. It's old. It's stodgy. But everyone can find commands in it. It operates as expected.
|
|
|
|
|
Nothing wrong with WinForms, and with just a little work using GDI+ they can look like modern UI, but with the reliability you expect from WinForms.
About 2 jobs ago, I worked on wrappers to update the 'feel' of the old WinForms controls. That was a fun project.
I've never liked WPF, it always seamed half baked and you couldn't get into doing manual drawing like you could with WinForms. UWP at least had the Win2D library that allowed you to write your own DirectX drawn controls.
|
|
|
|
|
What most people fail to understand is that XAML controls are inherently scalable, which is one reason that Visual Studio 2010 was rewritten in WPF. While you could certainly create your own controls in either WinForms or XAML, I’ve never seen custom controls implemented with accessibility or true internationalization in mind, though that is also a rarity with even HTML. I recently learned of margin-block and margin-inline and it has made me reevaluate all layout work I’ve ever done, AKA blown my mind.
Besides the skinning of controls, the one thing that constantly changes is the paradigm of UX…for better or for worse. Discoverability is horrible these days (Windows 8, swipe left/right, long “tap”) and seems to be overcome only by social reinforcement: old farts need not apply.
|
|
|
|
|
It's the next iteration of UWP (and XAML); which is better than WPF; which is better than Windows Forms.
The simple fact that Windows Forms doesn't support templating, puts it a generation behind the others.
The Win UI / UWP controls perform better than the corresponding WPF controls (says MS).
If you have no baggage, Win UI 3 seems like the logical choice.
If you're big on "spread sheet type data grids", you'll still need a "toolkit" for that (or roll your own). "Fluent design" apparently doesn't believe in them; and with listviews and templating, you don't need them either (IMO).
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it.
― Confucian Analects: Rules of Confucius about his food
|
|
|
|
|
Thanks, that's what I suspected. I think I will try it.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Gerry Schmitz wrote: The Win UI / UWP controls perform better than the corresponding WPF controls (says MS).
I wonder how much faster? Because WPF is appalling for adding lots of objects to a parent control, as can be seen at the beginning of the following video:
My new DynamicDataDisplay.Reloaded project - YouTube
|
|
|
|
|
The "other objects" are a result of the generic / standard templates for the various controls. There is no "button" per se; it's constructed from a rectangle and a border. Something that is "hidden" in Windows Forms, whereas in WPF / UWP you could say to use a circle and you get a round button; with one line / paramter.
I needed a row of toggle buttons to act like radio buttons (I didn't want "fish eyes"). Styling them as RB's made them act like RB's (but look like toggles); including syncing each other. One parameter.
WinUI is faster because it's (re)written in C++ (?) vs ? It's also decoupled from the OS.
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it.
― Confucian Analects: Rules of Confucius about his food
|
|
|
|
|
I am looing forward to utilizing "Dear ImGui" Its' text based demo programs are blazingly fast in responding to user actions As it used for game graphics I assume it is fast there also but my project will be mostly text so graphics speed does not concern me Thanks however for bringing "WinUI" to our attention I should probably look into it as well for that project I will probably choose the most responsive - Cheerio
|
|
|
|
|
Dear ImGui is not used for graphics, but is used with a GPU to render a UI.
|
|
|
|
|
Unless you use Uno-Platform. WinUI is Windows only.
WinUI also requires you to package your app in some new Win10+ app package (so thats a limitation if you target Win7/8).
Once Silverlight died, MS lost touch (completely) with portable UI (HTML/JS is a joke of a solution ppl are stuck with sadly [while WASM should have negated this already]). Everything in the UI space is constantly subject to die off because no one in the space seems to know how to engineer here. Its been baffling me for years now.
|
|
|
|
|
another elephanting UI approach from Microsoft? Oh, right, we need a new way to handle icons with rounded edges.
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
Maybe if they keep trying, they will eventually get it right.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
lol, right... shall I bring up COM, COM++, DCOM and activeX?
That was my introduction to Windows development. After suffering through that and then on over the years with MS, they just rename $hit for the sake of it.
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
Woo!
I'm about to achieve maximum hardware efficiency, using all the RAM and all the cores of my little device to render a page of an epub book. It will render the current page and the next page (or previous page if you're moving backward) so that you can flip pages while reading in a way that appears to be more responsive. Basically, I'll have the next page rendered so you can change pages as soon as you're done reading the page you're on.
This ESP32 device was never intended for something this intense. The minimum hardware requirements I've seen previously for an epub reader is 512 times the RAM (not a typo!) and at least 4x the CPU power of this device. If I'm being completely fair comparing a WROVER rather than a WROOM it's still 64 times the RAM for a traditional minimal epub reader.
The final frontier for me is CSS and code size. The former is doable if I'm willing to live with limitations. It will support just enough to render text for a book okay. The latter is doable I think, but if it's not I'm dead in the water. My code has to fit on the device.
Wish me luck.
Real programmers use butterflies
|
|
|
|
|
Good luck!
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
I've been working on a virtual memory system for embedded devices, although I've gotten side tracked by many other things, using static memory chips with SPI communication standard. The chip I'm using is a 64Mbit chip = 8MB. I've ordered a 4 MB chip from China so it may be a while,
Point is you might think about virtual memory/caching your pages? Just a thought. my 2 sense.
The less you need, the more you have.
Even a blind squirrel gets a nut...occasionally.
JaxCoder.com
|
|
|
|
|
I am caching them. I don't have anything as sophisticated as virtual memory but the onboard flash isn't particularly fast anyway, so I'd rather keep access to it explicit.
Edit: Adding an external SPI PSRAM module might not make sense as I'm not sure the ESP32 under Arduino can do 80MHz SPI comms and anything slower would be ugly.
Real programmers use butterflies
|
|
|
|
|
Just a thought!
I'm using an ATmega328P with 2K memory to test/develop my virtual memory. Not sure if it's going to be worth a plug but it's an exercise to learn more about the memory management on these little/marvelous devices.
The less you need, the more you have.
Even a blind squirrel gets a nut...occasionally.
JaxCoder.com
|
|
|
|
|
Wow, 2kB of RAM is barely enough to do SPI. How do you page? You must do like 512 byte pages at most!
Real programmers use butterflies
|
|
|
|
|
The SRAM has 32 bytes pages and I reserve (configurable) 100 bytes of memory above the stack. It's a work in progress and don't know if it will be useful for anything but by-god I'm going to do it. 
The less you need, the more you have.
Even a blind squirrel gets a nut...occasionally.
JaxCoder.com
|
|
|
|
|
Mike Hankey wrote: It's a work in progress and don't know if it will be useful for anything but by-god I'm going to do it.
I not only understand that sentiment, I can appreciate and respect it - a man after my own heart.
Real programmers use butterflies
|
|
|
|
|
Do I see the makings of an article here Mike ?
"I didn't mention the bats - he'd see them soon enough" - Hunter S Thompson - RIP
|
|
|
|
|
Hmm perhaps, I've already posted a short article on my site regarding memory management but I haven't finished the virtual memory stuff yet.
Frankly didn't think there would be any interest.
The less you need, the more you have.
Even a blind squirrel gets a nut...occasionally.
JaxCoder.com
|
|
|
|
|
I think there would be. I certainly would be interested. Anything that fancy running in 2kB sounds fascinating.
Real programmers use butterflies
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
