I've released version 2.0.1 of Solid Shine UI, with a handful of various fixes and small changes.
Including a fix for ParticleEmitter that kept it from working at all, which I feel silly about since it was one of the big features of 2.0. Whoops!
github.com/JaykeBird/ss...
Okay, JaykeBird.com is now back online! It may go offline for a few minutes here and there over the next few hours while I'm fixing some other stuff, but that should only be for short periods of time.
Jaykebird.com will be down for a short bit while I work on applying some updates. I'll update when it's back up!
To be fair to ASP.NET and its design, I say that it was daunting and confusing at first, but I did also manage to build a whole website without a lot of the deeper knowledge, and it worked. So I mean, it is pretty accessible. And now I have more knowledge, and am excited to start doing more!
Every day I work more on my website, I learn more about ASP.NET Core, which is really exciting!
So much of this stuff was so daunting and confusing to me but I'm really starting to get a good handle of what all is going on here. So glad to expand my knowledge beyond just WPF/desktop app stuff.
Right now, definitely enjoying taking a break from working on this project lol. I have other projects I'm excited to get started on or to return to.
Haven't encountered or heard much of issues with SSUI 2.0 since its release, which is good. I do have some small (not urgent and not major) things I think I want to fix or improve, so a 2.0.1 will likely be on the way... probably sometime next month. 1.9.10.1 will also come around then.
This is the UI library I use for my own projects and my own things, so even if others don't use this, it's a big release and a big deal at least for me and what I'm doing.
Still, with me putting it out there, I'm hoping that others will find some use in what I've made too!
Changes for 2.0 include:
- a new SsuiTheme theming system
- fully rewritten spinner controls, PropertyList, and PositionSelect
- new ParticleEmitter control
- new BrushSerializer helper class
- all kinds of improvements to most of my controls across the board
That's just a brief list. It's a lot!
This has been something big that I've been working on here and there for years. As I've discussed previously, not everything I've wanted is included in here, but there's a lot that I got done and crammed into here.
Looking forward to now taking a bit of a break from this project now! Lol
Finally, after what feels like forever! Version 2.0 of Solid Shine UI has been released!
This is a C# WPF UI library with my own entire set of controls and a theming system and more. #dotnet #wpf
Check it out if you're interested. I'll update the readme and such later!
github.com/JaykeBird/ss...
Solid Shine UI 2.0 will be coming out this upcoming week, most likely on Friday.
I've done a decent amount of testing and a lot of it is pretty solid. Committed the last actual feature just a couple hours ago. Just have some bugs to fix (none major, but some are annoying) and it'll be ready!
Either way, I guess it's not a bad thing to want to bring the most polished experience when I can.
So I guess this is me saying I'll also be making a new 1.9 release around the same time that 2.0 also releases. I'll share more details when the time comes!
At some point, I will need to give up on continuing to support the 1.9 branch. I guess that day isn't today, and it likely won't be in the near future either, but at some point, some time, it will have to happen.
And then eventually after 3.0 comes, I'll have to stop supporting 2.x as well.
I think, for some reason, I'm also concerned about people having a difficult time transitioning to 2.0, despite the fact that:
1) while upgrading will require some code changes/fixes, the amount of work is somewhere between small and trivial
2) it's not like that many people are using it anyway
I know I've talked a lot in recent about leaving the 1.9 series "in the best state possible". To be honest, I'm not sure why I'm so focused on this. I know it's partly because I'm dropping older .NET Framework versions and I want to leave those on a high note, for the few-to-no people this affects.
I think clearly, I need to have a better process to test and check things, so I don't let things through the cracks like I've been doing.
I have the means to properly test stuff, I just have to go ahead and actually do it. So that's something I'll be improving my process on for future releases.
Since releasing SSUI 1.9.10, I've found 2 issues needing fixes (one of them was a regression I accidentally introduced because I didn't properly test the change afterwards). I've obviously fixed them for 2.0, but I still think I want to go back to fix these for the 1.9.x releases too.
So the list of items I have for Solid Shine UI 2.0 is now pretty short! I think I just need to find two solid evenings to get the rest of the items done. And then I'll just spend a bit of extra time testing things, just to make sure there aren't any other bugs/issues I've missed.
Some of the features I wanted for version 2.0 have been cut, sadly; instead, I will spend more time working on those to include in 2.1 and 2.2!
But in 2.0, there will be totally redesigned spinner controls, a new and very nice theming system, an upgraded PropertyList control, and more!
Official announcement: Solid Shine UI 2.0 will be released in February!
I've been working on this version for years now, and I'm glad it's almost at the finish line! I'm only confident in announcing this now because my to-do list is now very small, and then I need some time for debugging/testing.
"Transform serialization" sounds like the kind of technobabble one would say in a movie... And yet, this is what I find myself coding tonight lol.
To be more specific, I'm working with "affine transformation matrices", which sounds like even more technobabble that I honestly only half understand.
That final option, of just updating the child's values directly with no binding once the control's properties are changed, is what I had to do with TabControl in SSUI 1.9.9. I dislike this for being so against the WPF principle of separating appearance and behavior, but I may have to do it again. :(
Do I need to reapply the binding between the control and the child? Should I find the child via OnApplyTemplate and bind in there, rather than using TemplatedParent? Should I just manually update the child's values without a binding? These are all code-behind solutions, and should be unnecessary. :(
The situation is I have a control with a template. In that template is a child with a lot of its values bound to the TemplatedParent.
So then, when I bind a property on that control, updates to that binding should also trickle down to the child in the template... It does once, and then never again.
What's really frustrating is that it's specifically acting this way with this one control. All of the other controls I have are behaving correctly. And I'm not doing anything *that* different here.
I don't understand why it's not updating, it genuinely seems like it should be.
I'm having some real difficulties and issues debugging WPF bindings. :/
I guess it's what I get for kind of getting thick into the weeds about it, but it's frustrating trying to figure out why a binding works once and then stops updating. I don't think what I'm doing is that complicated.
I updated my website last night, now using .NET 10! And I've replaced using Google Recaptcha with now using Cloudflare's Turnstile system.
Planning on more stuff I wanna build on my website over the coming weeks and months!
Solid Shine UI 1.9.10 is released! Includes a few small features, and more bug fixes! Next up, 2.0 will be coming very soon!
Download this new version at github.com/JaykeBird/ss...
Learn more about Solid Shine UI at jaykebird.com/software/ssui
About done with Solid Shine UI 1.9.10. While scope creep is a perpetual issue with me lol, I've done a better job this time to keep my changes pretty focused to bug fixes and internal improvements. A few (very) small features made their way in though lol.
Planning to release this very, very soon.