|
If me I'd question if this a complication that actually needs handling or just a programming challenge I want to figure out.
Real world: what application this on, why would there not be enough screen space in current era. If was user input box on very narrow component, well the problem is flipped why user inputting into narrow viewed space, why cant space be increased.
if label - again flip word. having it increase height of space might not be desirable, so leaves truncation "." "..." as an option.
Put generically: figure out if this a problem that needs solving or if asking the wrong question.
|
|
|
|
|
I mean that's fair, but here's the thing: I don't know the screen size and it may be as small as 300px across. It's an e-reader
300px is not practical for an e-reader, I know - but it's more about me not knowing the functional design specs of the hardware yet. I'm coding defensively in light of lack of solid specs yet.
We simply can't know the specs yet, but it will probably be about 600px across like the nook but there may be a smaller version that's more pocketable if that's practical. Still, if they zoom in, or if the title (H1 tag) is long it could still be a problem.
Real programmers use butterflies
|
|
|
|
|
It sounds like you are leaning toward a hard break at the display margin.
Instead of using a hyphen, how about another pair of symbols?
I am thinking of the proof readers notation when two words are supposed to be joined. It is like a subscripted “u” that connects the words. Draw half of it on the break, and the other half on the continuation. Or use an ellipsis at both the break and the continuation.
Or just a random hyphen. Don’t worry about being correct for a word like that.
It will likely never happen.
|
|
|
|
|
|
You might consider "soft hyphens" - Cheerio
|
|
|
|
|
I have since found something called the Unicode Line Breaking algorithm and I've decided to go that route.
Real programmers use butterflies
|
|
|
|
|
Anyone here working on a desktop application using the new WinUI API?
I'm going to be starting a new personal project and I'm considering all of the available UX platforms. I'd like to be able to eventually publish this project as a commercial app, so I want to choose a UI platform that is relevant and modern-looking. I haven't yet delved into the WinUI and I'm wondering if it's worth the effort.
Build desktop Windows apps with the Windows App SDK - Windows apps | Microsoft Docs[^]
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Richard Andrew x64 wrote: I'm going to be starting a new personal project and I'm considering all of the available UX platforms. I'd like to be able to eventually publish this project as a commercial app, so I want to choose a UI platform that is relevant and modern-looking.
"Modern looking"? As opposed to "accesible", recognizable and configurable?
Comctls32 always worked. WinForms.
That UI is recognizable, exists in multiple platforms and is cheap to maintain.
Bastard Programmer from Hell 
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
This wouldn't be a line-of-business app. This would have to appeal to consumers.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Richard Andrew x64 wrote: This wouldn't be a line-of-business app. This would have to appeal to consumers.
Especially then, you want a UI that's recognizable, predictable and tested.
WinForms is vastly underappreciated. High-contrast schemes for visually impaired controlled by system settings.
Ofcourse that doesn't appeal, does it? You need something that screams "untested" with animations.
Bastard Programmer from Hell
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
Eddy Vluggen wrote: You need something that screams "untested" with animations.
Exactly.
Seriously though, I'm not against using Winforms, it's what I know best. It's just that it doesn't look modern. And appearances mean everything to commercial success.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Yeah, must look new, instead of tested and trustworthy 
So do the WPF thingy? Make your buttons animated. Throw out decades of research.
Bastard Programmer from Hell
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
Come on now. WPF is far more than how you describe it. I can't remember the last WPF app that had animated buttons. I've since moved on to HTML5 but I am still impressed with the comprehensiveness of WPF.
And it's the same low-level APIs at the end of the day - WPF is just an abstraction (and it's been around a LONG time).
|
|
|
|
|
There are a number of excellent component vendors e.g. DevExpress and Telerik who make WinForms apps look sensational.
Garry Lowther
CEO and Founder
TriSys Business Software
Cambridge, England
www.trisys.co.uk
|
|
|
|
|
We use DevExpress with WinForms for our commercial desktop app. It's style controller is great for giving a modern look. However, DevExpress has the issue of it can do anything - if you set the properties just right. We spend more time getting the exact combination of properties to achieve the desired effect than anything else when using DevExpress. That said, their online support is excellent and free. They will frequently give you code samples of how to make something happen with their tools.
As for the style controller, we have a master base form that all other forms inherit. This is used to set the style for all components recursively. Then, in child forms' constructors, we just call the method base.SetStyle().
Bond
Keep all things as simple as possible, but no simpler. -said someone, somewhere
|
|
|
|
|
The image below corresponds to a software I made exclusively using Winforms. I designed my own controls for Buttons (Gradients, 2 lines of text with different fonts and colors), DataGridView, Labels (Gradients Horizontal and vertical text [Up and Down]), Closable Tab Well, and some others. Usually Nobody recognizes it as Winforms, but it works exactly as what it is. Old reliable WINFORMS.
OneDrive[^]
So you can see that it is possible to make "Modern Looking" software in this easy-to-work-with GUI.
I hope you can see it, because I never posted any images in CP before  
|
|
|
|
|
|
That's awesome! I don't have the graphics skills to do that.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
I can give you the controls so, if you want to work with them you are very welcome without any royalties. I don't have manual or help, but I think with a little effort you can master the possibilities. Usually they are grouped under "GV Options" in properties.
Some times, I want to write an article in CP about these controls, but it is a looooooong task. The controls I've designed are: (some are Spanish names  )
BotonGradiente => (The buttons you can see in the graphic) 3 colors for gradients in any direction and percent's, 2 text lines with different fonts and colors, shadow for the texts (any color), Icon,...
BotonMenu => Is a button with a little arrow used to show a ContextMenuStrip. Similar to BotonGradiente.
GradientLabel => 2 colors, Linear or Tubular gradient, horizontal or vertical gradient, Hor. or Vert. text (Up and Down)
Linea => (line) Draws a line of any pixels width, including gradient colors that change direction if the line is horizontal or vertical.
Conmutador => (Switch) Is an On / Off button with a behavior similar to checkbox, but fancy with different buttons and gradients, with configurable texts for ON and OFF
Check and Radio => The same controls used by Winforms but with the ability to use icons for Checked / Unchecked states.
ClosableTab => Same TabControl but with gradients and font for the tabs, for the background of the tab well, ability to close a tab (and hide this if you need) Color and shadow for the tabs.
MultiColumnCombo => This control is based in the work of kennedy_franklin which has an article in CP about it.
Progreso => Is a progress bar with linear and tubular gradient, and also show or hides the percent value.
Boton => Is another button that lets you to choose 3 state images: normal; pressed; disabled.
TitlePanel => It is like the one you can see in the graphic. A Panel with a title bar included (Is a gradientLabel so has the same properties). The title can be horizontal or vertical (left side) the panel area can have a 2 gradient and optionally the panel is collapsible and grows to its contents when it or one of its controls received the focus and collapses when lost it.
Fecha => DateTime Calendar control. Derived from DateTimePicker but when you enter the date with the keyboard, the cursor jumps automatically to the next fiels : yyyy -> mm -> dd and then to yyyy again.
GVGrid => It is a DataGridView Control but with the possibility to change the direction of the cursor when you leave a cell pressing ENTER to down or Left. It also has a Calendar Column and the possibility to sort by several columns Ascending or Descending independently (Sorting is based on the work of PTA_UK)
|
|
|
|
|
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.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
