|
So, I have dusted off my project yet again. Written in FORTRAN my goal is to lift it to modern systems. I've asked various questions over the years, but I hope this might just be my last hurrah that pays for the sailboat I want and pay off my mortgage. I also want to pull in some coder whannabees from local high schools (but that is VERY tbd).
Digging into this - my experience says the biggest issue with the existing system is that it's a big blob. I'll leave it there. I don't want to get into too much detail and vector my question.
In doing my research, I know I want to use C# to implement the initial UI. What I've concluded is that C# is the tip of the Microsoft iceberg. A language is a language - you just need to get familiar with it's quirks. But underneath C# is the mass of .net. Just like mfc, com, com++, dcom, ActiveX and all of the other rot MS pukes out. Don't get me wrong, some of it is okay. But it seems C# is the trivial part.
Am I on the wrong trail, or have I got this right?
Charlie Gilley
“Microsoft is the virus..."
"the problem with socialism is that eventually you run out of other people's money"
|
|
|
|
|
Are you asking if you need to become familiar with the P-code that C# emits, in order to create your solution? I don't understand the question the way it is worded.
|
|
|
|
|
no. I do not want to even know about p-code. What I'm saying/asking/spewing is it seems C# is just the basic tool to get into the .net framework. The analogy I would make would be hey I want to write a C++ interface with MFC. I don't want to do it in win32.
Stage 1 is to learn pure C# and stage 2 is to embrace the .net framework.
If I have to go into p-code, I've done something wrong.
Charlie Gilley
“Microsoft is the virus..."
"the problem with socialism is that eventually you run out of other people's money"
|
|
|
|
|
That's not how I see it.
As a poor analogy, I might say that the language is the fuel for running a vehicle (a UI framework).
Learning to operate the vehicle is the important part.
|
|
|
|
|
everybody?
I hope that the users aren't now abandoning this place. 
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Yah, no one good or smart comes here any more. <==== (edit: This is a joke!)
I'm still here most days. 
Here's my TLDR;
My wife was downloading photos from iCloud (iphone) so she could print them.
Discovered that 9/10 photos she downloaded were downloaded as zip files.
Apparently a lot of her photos were on "live photo" which includes a "video" portion.
So, when you take that photo and download from iCloud you get a zip which contains the .MOV and the JPEG.
We just want the JPEG so she can print some pix.
I wrote a .NET Core console app that:
1) allows user to point at directory where all those zips (100 or more) are and will pull out every JPEG and save them all into <target> folder provided by user
2) Run another command on the app and it'll tell you if any of the images are duplicates.
I'm really excited by this little utility because it is really cool and has a lot of uses.
You can use it to tell you if you have any duplicate files. It runs SHA256 hash on every file and then tells you if any two files are dups. 
The CP Problem
See how excited I am to talk about this?
This would normally become a CP article. But  should I do now?
Bummer 
|
|
|
|
|
Sounds like a nifty utility! Does it also remove the duplicates?
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Richard Andrew x64 wrote: Does it also remove the duplicates?
Not yet, but I am going to add a switch the user can provide to do that too.
Oh, you can see the (very quickly written code) at my github: GitHub - raddevus/iPhotoGrabr: Unzips photos from iCloud downloads (.NET Core 8)[^]
Hope you can use it too.
I also build the EXE as a standalone for win10 (though I'm dev on Linux) to make it easier to use on my wife's win11 machine.
Take a look at the buildForWin10.sh (shell script) You can use the command in that file to build on Win10/11 too.
|
|
|
|
|
Two more things (cuz I'm so excited!).
1) I used an honest-to-goodness C# Tuple in that code and I think it actually makes sense in this case.*
2) I'm also planning on writing a GUI** for this code later so user can traverse through folders for choosing source & target folders.
* I've never had a terribly good reason to use a tuple before but I've seen a lot of examples that seemed to be using them for tuple-sake.
** I will use Photino[^] to build the GUI when I do this. It'll be a great use of Photino, I think.
|
|
|
|
|
still here but a lot of the originals are getting older and retiring. I don't see a lot of new blood coming in. Circle of life stuff.
It's actually a shame - but the core base of users here were actually quite experienced when Chris launched the site. I'd be interested in seeing the statistics. Now, what needs to happen is that new blood needs to be pulled in. And by new blood I mean this mid-tier coder grunts. I see a few from time to time. I do not mean the "will you help me do my homework types." Those just scare me. And now with AI rolling out built into tools, all I see is consulting money. 
Charlie Gilley
“Microsoft is the virus..."
"the problem with socialism is that eventually you run out of other people's money"
|
|
|
|
|
Sex appeal with the crowd, former royal has termite problems while travelling. (10)
|
|
|
|
|
Well done Pete -I was thinking of deputising for you today 
In a closed society where everybody's guilty, the only crime is getting caught. In a world of thieves, the only final sin is stupidity. - Hunter S Thompson - RIP
|
|
|
|
|
I pulled one from the back catalogue. There's every chance that you've seen this one before.
|
|
|
|
|
All I've got is itinerants
sex appeal = it
with the crowd = in
ex Royal = er
termites = ants
In a closed society where everybody's guilty, the only crime is getting caught. In a world of thieves, the only final sin is stupidity. - Hunter S Thompson - RIP
|
|
|
|
|
That was quick. Congratulations.
|
|
|
|
|
I think it should be itinerant for travelling or itinerants for travellers - just sayin
In a closed society where everybody's guilty, the only crime is getting caught. In a world of thieves, the only final sin is stupidity. - Hunter S Thompson - RIP
|
|
|
|
|
This is a Winforms app. With clicking a checkbox, user enables a feature in the Settings form. Somewhere else in a form a tab named "Alarms":
Option 1: which was visible but disabled, gets enabled.
Option 2: which was hidden, added to the TabControl again.
In terms of UI design decision, which method you prefer?
Personally, I like option 1.
What, you, the community think is a better option?
Behzad
|
|
|
|
|
neither option. You do not store data in a form ever. You store data in an object, e.g. a "settings" object. Both checkboxes link to one field of that object. Do not ask any follow-up here. This is strictly a non-programming forum. Find your language in a forum above.
"If we don't change direction, we'll end up where we're going"
|
|
|
|
|
Sorry, but I think you did not get the point. My question is not about storing data. It's about UI design.
Behzad
|
|
|
|
|
That's just trolling now.
|
|
|
|
|
I promised him that I'd help.
|
|
|
|
|
I apologize if I gave you the wrong impression.
|
|
|
|
|
There have been many takes on this particular subject in the design community over the years. The consensus seems to be, at the moment, if a user is never going to be able to use that field, you should hide it. If it can be used in certain circumstances, you should disable it.
|
|
|
|
|
I prefer 1. It provides more information.
|
|
|
|
|
I would prefer option 1.
I would be more concerned about having the checkbox in the Settings form and the item being enabled/disabled on a tab in another form. What is the user going to think when they are in the Alarms tab and see a disabled section? Probably 'why is this disabled, I want to edit it.' Try not to make the user navigate away to the Settings form. Does it make sense to have the checkbox (or a duplicate) on the Alarms tab? At the least you need some way to indicate to the user why they can not access those controls. Users do not read manuals.
Make things that the user is likely to do easy to do.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
