Re: How to change my c++ program's icon?

On Sep 25, 6:25 am, Rainer Weikusat <rweiku...@xxxxxxxxxxx> wrote:
Ryan McCoskrie <ryan.mccosk...@xxxxxxxxxxxxxxx> writes:
Dos-Man 64 wrote:

[...]

Well, I am an excellent C programmer already.  Well, that's my opinion
anyway.  And I am familiar with shell scripting already.  Where I
struggle is in determining how X does some things differently than the
way Microsoft Windows was doing it.  It's the same general tasks that
are being performed; it's just a matter of the tasks being done
differently.

The reason that I said to look those up is because your dealing with a
different way of thinking about programming.
Embedding icons into executables is a cute idea but also kinda' silly
sounding. Why would you want that kind of a feature on a natively command
line operating system?

There is no such thing as 'a natively command-line operating system',
especially not insofar UNIX(*) or anything similar to it is concerned,
because any type of 'user interace' has always been something provided
by programs a user desires to run for some reason.


I think what he was implying is that it's easier and less complicated
to write console applications that run on a text-based shell than
graphical applications that run in a graphical shell. I would have
agreed years ago, however the ease of use for visual languages has in
some ways reversed the process. It's easier in my opinion to respond
to keypresses and mouse clicks in a visual basic app than it ever was
in a quickbasic program.


In fact, this
statement strongly resembles the backwards reasoning usually coming
from Microsoft-sycophants: The Windows-CLI is a largely undocumented
assortment of partially highly complex programs, eg bcdedit or netsh,
and lacks a lot of useful tools at the same time, which makes it
basically unusable for everyday tasks and (to the best of my
knowledge) nobody except maybe developers and really experienced
system administrators uses it for anything.


Yeah, if you actually want to write a console program with a "ui"
you're basically forced to write an ms-dos application using some
ancient language like turbo pascal, quickbasic, or visual basic. The
funny part about it is they were in a hurry to kill off DOS. It
certainly doesn't make sense to me to remove support for an older
application that was providing a service your newer platform doesn't
provide.


In contrast to this,
Linux-based systems usually provided an extended set of enhanced,
standardized UNIX(*)-tools which are useful to so-called 'end users'
and are actually being used alongside the nowadays usually 'primary'
GUI. That "Linux" has useful features Windows is lacking clearly
demonstrated that it is an inferior and outdated operating
environment! Especially taking into account that the basic principles
GUIs are built on are OLDER than any even remotely 'modern' set of
command-line tools ... ups ... forget about history! That's one of
those soft sciences you should despise!! Resitance is futile!!!


Basically, you have two lines of thought. On the left you have people
who believe that console applications provide some welcome simplicity
for a change, as well as not taxing system resources needlessly.
Microsoft are the leaders of the "anything a console app can do, a gui
app can do better crowd." What's disappointing to me is that they are
apparently still making people use the command line in recovery
situations. Why? Given the fact that these people almost never go
anywhere near a prompt, I would think that that would be the last
thing they would want to do in that situation. Talk about adding to
the frustration...
.

Relevant Pages

  • Re: [announcement] SYSAPI and SYSSVC for Windows
    ... Graphics on XP is managed by DirectX, GDI+, ... The Shell is handled by various components, ... and used by parts of the Windows Explorer and the Help subsystem. ... Microsoft seems to work on the next generation of graphical user ...
    (comp.lang.ada)
  • Re: help newbe with 8051 uC
    ... Actually, Microsoft isn't confused. ... Windows 2000 and up have both a DOS prompt and a Windows command prompt, and although the command languages are similar, the two are entirely distinct things. ... Basically, they wanted people who needed to use old DOS programs to be able to find a command shell, while hoping that everyone else would use point-and-drool windows for everything. ...
    (sci.electronics.design)
  • RE: SP2 Cant go to desktop
    ... Then click the "+" sign next to "Microsoft" ... Then click the "+" sign next to "Windows NT" ... At the list to the right, scroll down and find "Shell" ... Douglas Spear ...
    (microsoft.public.windowsupdate)
  • Re: Max line length in CMD shell??
    ... undocumented by Microsoft. ... Simple testing shows that the Windows NT command ... shell allows very long commands—in excess of 4,000 characters. ... The Windows NT Command Shell ...
    (microsoft.public.windowsxp.general)
  • SecurityFocus Microsoft Newsletter #176
    ... MICROSOFT VULNERABILITY SUMMARY ... Microsoft Windows XP HCP URI Handler Arbitrary Command Execu... ... PHPNuke Category Parameter SQL Injection Vulnerability ... Microsoft Baseline Security Analyzer Vulnerability Identific... ...
    (Focus-Microsoft)