|
Space-Track.Org[^]
2021-05-09 02:04:00(UTC) at Lat:41.6, Long:350.7 - North Atlantic, just off Portugal
Margin of error? Um. Errr ... eh .... trivial, really ... +/- 60 minutes
So, that's pretty much anywhere within an 18,000 mile radius of Portugal then ... 
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Hmm ... UTC now is 22:10, let's hope for a big splash  (and not anything else) within a few hours ...
|
|
|
|
|
I beleive the Maldives never were under Portuguese rule... So the estimate was a bit off
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
|
|
|
|
|
That seems ... elaborate.
The question is, did they come up with the app before or after the launch?
Real programmers use butterflies
|
|
|
|
|
|
But your favorite one is missing! 🍺
|
|
|
|
|
Au contraire mon cher, c'est vin pour moi 
|
|
|
|
|
|
You need glasses? I will drink the content - then you can have the glasses! 
Get me coffee and no one gets hurt!
|
|
|
|
|
I love the sound of broken glass
|
|
|
|
|
Quote: Windows Forms succeeded Visual Basic 6 in 2002, just as WPF succeeded Windows Forms in 2006. WPF brought with it XAML: a declarative language for UI. Microsoft developers had never seen anything like XAML. Today, Xamarin and UWP bring XAML to iOS, Android, HoloLens, Surface Hub, Xbox, IoT and the modern desktop. In fact, XAML is now the technology building the Windows OS itself.
Developers around the world love XAML because it’s so productive and flexible. Microsoft engineers feel the same; we’re building our own apps and even Windows 10 with XAML. The future is bright, the tooling is powerful and the technology is more approachable than ever.
XAML - Custom XAML Controls | Microsoft Docs
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
|
|
|
|
|
The person who wrote that clearly consumed a glass of wine too many
|
|
|
|
|
I think it was something they were smoking.
It has a steeeeep learning curve but it's an awesome framework.
|
|
|
|
|
I made several WPF applications, but it always takes me way too long to complete them and figure things out, so no thanks no WPF / XAML for me I will stick with Winforms.
|
|
|
|
|
Understandable, I've started a few apps in WPF and gave up in desperation but I kept at it and am slowly learning...slowly! The hardest part for me has been the binding, it is so powerful but binding problems can sometimes be like chasing pointer problems.
|
|
|
|
|
I found building dynamic UI in Winforms was a lot easier than WPF; I built an industrial control UI interface that let the end user build their own screens for what they wanted to look at. Winforms let you use GDI+ for making custom graphics or controls, WPF took that away, and had you layer other shapes and items to a new control (annoying). WinUI gave us back the ability with Win2D NuGet package for DirectX drawing and was decent.
I worked with WPF for a couple years, and put out some big projects with it at my last job, but I just could never "like" it, after I left that place, I told myself never to work with it again.
I feel if WPF had been close to standard HTML5/CSS3 it would have been a home run. MS could have had their own "React native" type framework before React took off, and be able to bring in web UI designers into a familiar syntax.
|
|
|
|
|
For many applications, Windows Forms gets the job done. I see no reason to introduce the complications of XAML for these applications.
If the UI must be redesigned on alternate Tuesdays to pander to Marketing's latest craze, I can see the utility of XAML.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Same thought over here  , WinForms were added to .NET Core after solving some issues AFAIK, and ease of use and popularity are key factors, so it seems not wise to try to abandon this ...
|
|
|
|
|
I believe WinForms added to .Net Core to abandon .NET Framework.
|
|
|
|
|
XAML is as simple or as complex as you want. Its ability to "flow" content, can make ui building less painful / more enjoyable.
No one "thinks" in terms of Windows Forms designer code; it's mostly drag and drop.
It's easier to "visualize" in XAML (IMO); I never touch the designer.
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
|
|
|
|
|
Each to their own.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Gerry Schmitz wrote: t's easier to "visualize" in XAML (IMO); I never touch the designer.
Agreed. The WPF designer in Visual Studio has always been a bug-ridden mess, and the XAML it generates needs so much hand-tweaking it's not worth it. Expression Blend is utterly unusable with its gray-on-gray UI.
I code my XAML by hand.
Software Zen: delete this;
|
|
|
|
|
I think WinForms is the bug-ridden mess. WinForms is a code generator. I cannot count the times the generator has screwed up on complex forms. I have had to go back a day and start over. With WPF I can fix things on the fly. Also since I can hand tweak things I find myself tackling much harder UI problems with great success.
So many years of programming I have forgotten more languages than I know.
|
|
|
|
|
Yes, it's GUI building abilities closely mimics of those of HTML/CSS, a simple human grade alignment requires "tricks". It offers scalability with screen size, but like auto-scaled 16*16 icons, blows up on small.
|
|
|
|
|
Windows Forms has always seemed to me to be a .NET wrapper around ye olde message pump and GDI.
Back in 2008 we started a major new product development. Up to that time our UI's were implemented in C++ and MFC. As I saw it, we had three options: C++/MFC, WinForms/C#, and WPF/C#. One of the pain points in C++/MFC was how laborious it was to make a UI adapt to changing conditions, screen resolutions, and window sizes. WinForms didn't add anything appreciably new. WPF on the other hand assumed from the start that a UI should be adaptive. It also made commonplace UI elements (graphics on a button, for example) trivially easy.
We went with WPF/C#, and have only had one hiccup in the 13 years we've been working on this product. The WPF document and page navigation features were both unreliable and unbelievable memory hogs. Page navigation had incredible memory leaks; dozens of MB for the simplest pages.
Software Zen: delete this;
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
