|
Part of the "fun" is the research.
https://www.vbforums.com/showthread.php?598418-Cutting-Stock-problem
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
|
Something along those lines would be a box cutter program.
When I go to ship something, a lot of the time I can't find a box that fits I end of creating one.
It would be nice to be able to enter dimensions, type, size, etc. of the box required and it spit out the cut pattern.
The most expensive tool is a cheap tool. Gareth Branwyn
JaxCoder.com
|
|
|
|
|
|
There are many CP articles / projects that can be used as template for an improved / extended version.
|
|
|
|
|
This was my source for learning VB.Net and how to connect to SQLite
Thanks
|
|
|
|
|
Here's a few that I use every day:
0: FTP client
1: IIS Log File Viewer
2: SQL Database Backup Tool with rotation and offsite options
One that I started and never finished was an MP3 catalog with album art from media player. It sort of works, but MP3 tags do not follow standards ...better to use the directory, but only because that's how my library is structured.
"Go forth into the source" - Neal Morse
"Hope is contagious"
|
|
|
|
|
kmoorevs wrote: an MP3 catalog with album art from media player. It sort of works, but MP3 tags do not follow standards ...better to use the directory, but only because that's how my library is structured Hmm. I wrote an app for myself that does this (and more), and even wrote a two part CP article, but never finished the article.
Software Zen: delete this;
|
|
|
|
|
A code generator that automatically generates a Winforms application from an SQLite database.
A diagramming application that generates database diagrams from an SQLite database.
|
|
|
|
|
The Simple Shelf Designer
I want to utilize about ninety cubic feet of space in my living area.
My dream: EL-Junk-O pile of cardboard boxes all gone; contents moved onto the neatly organized shelves.
Magic word: Simple. Everything I've seen so far would present me with an eighteen month learning curve.
|
|
|
|
|
a tiny source code version control system?
I did not see any such project on the Internet...
diligent hands rule....
|
|
|
|
|
Mercurial.
You can run it locally. It's small, and works well.
I needed something for work that stood INSIDE of a Control VCS I was not allowed to commit to until it was working (they did NOT understand how to branch). So I made my changes locally, and used mercurial on the same folders, ignore the other VCS folders. It saved my bacon a couple of times...
|
|
|
|
|
my proposal is desktop version, not distributed...
diligent hands rule....
|
|
|
|
|
Choroid wrote: Cutlist Optimizer - optiCutter[^] I read CULTIST Optimizer and wondered what the hell that was about
|
|
|
|
|
Sander Rossel wrote: CULTIST Optimizer Calculates efficient orbits for Moonies[^]?
Software Zen: delete this;
|
|
|
|
|
|
Perhaps a Cult List Optimizer It would make a great Halloween application
|
|
|
|
|
Whatever it is you decide to do, you'll have a lot more fun coding it in C# than VB. Just my $0.02
Paul Sanders.
If I had more time, I would have written a shorter letter - Blaise Pascal.
Some of my best work is in the undo buffer.
|
|
|
|
|
Very true. MS has not allowed VB to keep up with C#, unfortunately.
|
|
|
|
|
Oh, OK. Perhaps they want to wean people off it, long term.
Paul Sanders.
If I had more time, I would have written a shorter letter - Blaise Pascal.
Some of my best work is in the undo buffer.
|
|
|
|
|
I think that is the reason. But it is unfortunate. Having a slightly more productive language, that is as capable as C# (they both produce MSIL anyway), not saddled with the no-longer-necessary curly brackets and semicolons would be a good thing.
|
|
|
|
|
I guess. I like C# personally, because, speaking as a C++ programmer, it feels like home, but, like the OP, there's bound to be a lot of VB programmers out there still.
Paul Sanders.
If I had more time, I would have written a shorter letter - Blaise Pascal.
Some of my best work is in the undo buffer.
|
|
|
|
|
I program in C#, and have the past 20 years. Occasionally I have to do some maintenance or conversion on VB6 or VB.NET code.
But coming from languages like FORTRAN, COBOL, Clipper, and VB6, having to go backwards to fool with curly brackets and semicolons simply added incrementally to coding time. Fortunately, the VS IDE (copied from the VB6 IDE) had enough help for me to catch the syntax errors from a missing bracket or semicolon, rather than catch it at compile time.
Curly brackets and semicolons are a legacy from an ancient time when RAM was minimal, processors were slow, and such characters were used so the compiler did not have to infer lines and code blocks, which would have made compile time much longer. They provide no real value today, and haven’t for decades, but they do add to the comfort level for C++ and Java programmers working in .NET.
|
|
|
|
|
OK. Interesting. But doesn't each bracket and semi-colon take up an extra byte of RAM? 😁
Paul Sanders.
If I had more time, I would have written a shorter letter - Blaise Pascal.
Some of my best work is in the undo buffer.
modified 3-Aug-22 6:33am.
|
|
|
|
|
Not really during compile time. The compilers back then simply used them as delimiters to know when a line ended (semicolon) and the demarcation of code blocks for logic flow. They were not used for anything beyond that, and were a trifle compared to the characters in the line.
In a language like VB, the CRLF (absent a line continuation character) is used to denote the end of a line. Instead of brackets, VB uses key words (like End If) to denote logical blocks.
Developers who have known nothing but the C/C++/Java curly bracket syntax would likely not be comfortable with VB’s syntax, even though it is cleaner and appears more like natural writing than code with curly brackets and semicolons.
I adapted quickly enough to the more archaic pattern of curly brackets and semicolons, coming from the FORTRAN/COBOL/Clipper/VB syntax. Those coming from the other direction that I have known had more difficulty getting used to the cleaner syntax.
But C# developers today greatly outnumber VB developers, so MS rightly addresses that customer base by focusing on C# over VB.
|
|
|
|