|
Post by levievre on May 1, 2022 17:45:01 GMT 1
Everything is not about usefulness but I have a case where color setting is quite useful.
One of my customer is 82. He should be retired since a long time but still have a small business and use my app, among other things, to print invoices. Recently he asked me to change colors since he can't still read easily white text on lightgrey background. So I did reduce color #7 values. Now my old man is more than happy.
it's also a question of personnal preferences. Some of my customers use my app since a very long time (25 more years). They appreciate a change in appearance sometimes and they ask me to adjust colors to their personal taste.
If i could specify the colors for 4 or 5 schemes, it would be enough for me.
|
|
|
Post by whathim on May 4, 2022 21:41:17 GMT 1
I’ve commented before on my wish for colour palette setting in vDos. Here’s how I used the ability to set the colour pallet with my text editor program, “Open”, commented on above and elsewhere.
My editor program allows the user to set the foreground/background (i.e. ink and paper) colour of a file that is being viewed/edited. The program “remembers” what colour pairing was associated with particular file extensions so that when another file of that same type is later opened, the appropriate default colour is applied. Using the editor, I might set black on light-cyan for source code files (.bas, .cs, .for etc.), black on light-pink for .rc and .res files, black on light-green for .txt files and so on.
This was easy to set up under NTVDM. I would set the colour palette so that there were a range of light pastel shades that I could use as a “paper” colour, and black, to be used as the “ink” colour. Certain other colours would be set and reserved for compilation warning/error messages the editor might display. Sadly, with vDos I am stuck with the default palette so none of this is possible, or rather the ink/paper colour combinations available are virtually unusable.
|
|
|
Post by Jos on May 5, 2022 7:45:49 GMT 1
Still unsure if COLOR= will return. It would then only replace color scheme 9, a nostalgic green, already intended as a spare one. But you could then of course define and preselect that in config.txt.
If so, it will be in a silent final update to version 2022.05.01 next week.
Jos
|
|
|
Post by whathim on May 5, 2022 20:27:07 GMT 1
Actually, my preference would be a standard Windows colour selector dialog accessed from the right-click menu on the vDos console title bar. In other words, just like with a Windows command prompt console.
|
|
|
Post by Jos on May 5, 2022 20:53:38 GMT 1
That certainly won’t come. I’m not in the habit to extend (pollute) vDos with code/functionality only beneficial to one or two.
vDos is primary meant to extend the use of non-general DOS programs that have no (affordable/practical) Windows alternative. An eventual revival of COLORS= is all you might expect.
Seems to me there are plenty Windows alternatives for your DOS plain text editor program. I myself use Notepad++ for plain text.
Jos
|
|
|
Post by levievre on May 5, 2022 21:00:01 GMT 1
Since there are 16 colors to define, I still prefer COLOR= You can find good schemes here : www.w3schools.com/colors/default.asp. Look at color trends or color standards to built nice schemes. And it's easy, RGB values are indicated. I'm Ok whith a color scheme 9 only. Still I would prefer to be able to specify colors of every scheme except #0. Something like COLOR1=, COLOR2=, ... would be perfect Levievre
|
|
|
Post by whathim on May 5, 2022 21:19:16 GMT 1
Don’t get me wrong, Jos. I still think vDos is great for my purposes. I’m currently using my editor for various different types of source codes and compiling and intercepting compilation messages all from within the editor. It’s working beautifully and has required very little if any tweaks from what I had with NTVDM. And I do understand your caution regarding extending vDos.
|
|
|
Post by Jos on May 5, 2022 21:42:53 GMT 1
Don’t get me wrong either.
I haven’t done any DOS programming for a long time. If I recall correctly, also used Notepad++ then. File extension specific display (as syntax highlighting), capture compiler output. All you need to compile a (DOS) program.
Jos
|
|
|
Post by whathim on May 5, 2022 22:30:09 GMT 1
I don’t just do DOS programming. I do Windows SDK programming, c# .NET programming, html/Javascript and many other things – all from within my editor. I sort of have my whole development environment orchestrated from my editor. It would be a wrench to move to another platform – and I’m an old dog.
|
|
|
Post by levievre on May 6, 2022 8:19:30 GMT 1
Hi Jos,
About you remark above that you don't want to pollute Vdos with functionnality only beneficial to one or two. When I suggest a mod this is not for me only but for all the users of my app.
And In France,more than 100 small retail shops use my app. It's about 150 users maybe.
Thank you.
|
|
|
Post by Jos on May 6, 2022 8:42:56 GMT 1
How would those 150 users benefit from a Windows color selection dialog in vDos?
Jos
|
|
|
Post by levievre on May 6, 2022 9:19:48 GMT 1
I still maintain, help, setup, update my app for all my users.
They never have to install Vdos or change a line in autoexec.txt or config.txt since i do it when they ask.
All I need is COLOR= back. Of course, COLOR1=, COLOR2= would really be appreciated and could benefit to every one.
Levievre
|
|
|
Post by Jos on May 15, 2022 21:33:39 GMT 1
Still not convinced COLORS= to be useful, it is now even entirely dropped by the silent update of May 13th.
That will be in effect for a year or so. Further discussion won’t change that.
Jos
|
|
|
Post by levievre on May 16, 2022 10:04:45 GMT 1
Ok Jos. 2017 Vdos is still fine for me.
|
|