The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
The VS example might work with menu options, but I don't see how it would work for code. Every programmer has his/her own way of pronouncing variables (e.g. es que ell vs. sequel for SQL), all of which would have to be taken into account.
You would also require localization even for things like pronouncing the alphabet. I remember a case where I had to spell out a word for a Frenchman, and he kept hearing my 'E' as 'I', because that's how it's pronounced in French.
As an experiment, I suggest that you sit with another programmer, and try to write and edit a program by dictation. I predict that you will find it an exercise in frustration.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
Hi, What you describe is functionality far beyond what i imagined anyone reading my little fiction would infer
i'm thinking more like an audio version of TypeScript ... something at a micro level compared to a general purpose speech recognition engine; imagine how tedious it would be to give such an engine unambiguous text for names, etc.
My intent in the original post ... in addition to having fun ... was to see if anyone had tried something similar; what better group to bounce ideas off of than this ?
The issue of saving time/typing drives me to write little "transformers" where input like this:
(JSOP didn't pick the image, i swear, it was just the first one with the overall color palette i was after that I found )
Well I figured out how to do it. I'm adding palette/CLUT/indexed-color support to GFX, and for these I will have a 3 color fixed palette that starts with white instead of black, to mirror how the e-ink stuff works.
Then, I use a nearest matching color algo during color the conversion process to get the values I want. If the thing supports things like gray shades I'll just add those to the palette.
Just like my other palette stuff.
That way the JPEG above won't render inverted and monochrome.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
Recently I installed Linux and had to use vi to edit some files. I hadn't used the godforsaken thing in about 30 years but managed to do what was needed without hopelessly corrupting those files. I now believe in muscle memory, since it is the only explanation for how I could insert, replace, cut, and paste text and quit with or without committing the changes.
In a Lounge post a couple of weeks ago, I asked about using Windows 10 to develop C++ for Linux. VS Code seemed to be a clear winner, so I'll likely switch to it someday. What's blocking me is builds, for which I use VS2017.
For WSL, MS recommends CMake. That looks to be about as fun as vi, so you'd think MS would provide a tool for converting VS project files to CMake. Think again.
But I did find a tool[^] that supposedly does it. What it generated seemed to do most of what was needed, but it failed on a shared properties file that controls various compiler and linker settings. So I'm stuck with VS2017 until this tool gets fixed or MS gets their act together. Porting to Linux isn't urgent, so I'd rather wait than struggle with CMake.