What did we use before graphical user interfaces?
346754
text, or LEDs mostly, but some programs used the crude graphics of DOS.
2567
ELIZA ran on a mainframe computer in the sixties.\nSomeone duplicated it as a Java applet.....\nThis page contains a link to a zipped file and other information.....http://chayden.net/eliza/Eliza.html
717367
I don't know what IE is but wouldn't the toolbar be in a library that you just call or add in? If you are going to write then I assume that you have a compiler or a language in mind. And, if you do then you can read the help files or get a book on how to write the code in that language.  I haven't programmed for 10 or 15 years.
112698
A myth, mostly.  The idea is that the programmers anticipate all the various things the user will want to do, and make it easy to do them.  A truly user-friendly interface would name the menus something the user would recognize as being the place to find what he is trying to do, would put them all out there where he would be expected to look for them, etc.  It would also guard against accidently screwing up, by having "are you sure?" protection on things.\n\nHA!  I have yet to run a program I couldn't screw up, or rather screw up my document or my data in no time flat.  And I have yet to find anything useful in a "Help" menu.  Mostly the way I get by is lots of trial and lots of error, and bugging the people who know to tell me.\n\nOh, for the days of user manuals and tutorials!!!
861634
Well, you can use almost any programming language for the graphical part. But the base, the kernel, MUST be written in ASM. I even found an OS, developed by one of my friends, written in Fortran and Python. But people usually use C++ because it's kind of easier. You can try using anything(except the web-script ones like PHP, Perl, C#, VBscript...).
299050
Past - Really Big Calculators. Originally considered no more than a number cruncher, 'programs' were primarily business oriented. Accounting, Scientific, etc. At the time, only a handful of people on the planet ever considered they would be more than the 'science fiction' movies of the time portrayed them.\nPresent - Computer jargon is very much a part of our ordinary lives. Nearly every appliance in a modern house contains more computing power than that which ran the moonshot missions. A significant percentage of the world's populace could not conceive of a world without computers. More than business, computers are our entertainment, our transportation, communication, our virtual life.\nFuture - Further human integration. Smart Computers will run our everyday lives: feeding us, tools for work & play, our sole means of communication with those around us. Further progress for implants into humans will allow 'hands free' operation. No money, cards, phones, etc. will be required past the optics to access personal links to the worldwide net.\n\nIf we happen to survive that long.
1053985
This has to be really useful:  http://en.wikipedia.org/wiki/Computer\n\n(10 points 4 me? ;)  )
246272
View --> Toolbars\n\nThat will let you redisplay it.
326452
Just write the document to describe each item changed and or any changes in functionality. Then provide a screen shot (ALT + Print Screen) for each of the changed items.\nGood luck!
554808
In the same manner you used Microsoft 2002
504124
YABASIC (Yet Another BASIC).  They have versions for both Windows and UNIX environments.
420890
Microsoft Visio could work for that.  There are other programs that exist too.
384495
I'm not sure what you mean by layout, but for command-line interfaces (CLI), you should look at the man pages of Linux programs.\n\nType: man program (e.g., man grep)\n\nThis will give you an idea of what type of types of flags people are accustomed to (e.g., -r for recursive if your program does directory/file operations).\n\nAs for how this relates to HCI, well it's primarly an ease-of-use issue that you should consider. For command-line programs, the only consideration is to adopt tried-and-true flag-naming etc... because people are used to a certain convention or set of semantics (e.g., outputting to stdout so they can redirect the output to other programs). If you change things like that, it makes the learning curve steeper for intermediate/advanced users.\n\nIf you were just talking about a command-line interface like a console terminal, then definitely things such as: text autocompletion (via Tab), or defining your own autocompletion drop-down box as you type would be very useful for the user -- very much like when you type an address in your browser, it brings up a list of websites you've been to as you type. Again, that's going back to implementing what people are accustomed to and just making the entering of commands less time consuming/tedious.\n\nHope that helps.
1067081
tools\ninternet options\nclear history
959426
Writing is quicker than pointing and clicking.\nAlso a command line interface is easier to use from a script.
611983
That's me!\n\nAs you want to work with resource scripts in C++ anbd develop GUI's I must tell you first and foremost, you should MEMORIZE the function in the graphics.h file and their utilities and learn the use of initgraph() and SVGA.\nYou would probably not find the utility of MOUSE there, but I'll refer a good book - C 'Pearls' or you can mail me back to get the initmouse() function that basically uses DOS interrupts to generate the mouse cursor. The DOS interrupt number is 0x33 and there is no service number needed, just set the AX value in the INREGS register to 0 for init() and 1 for show() ..mouse functions. Experiment with different values to get more functions. Rem: values 0-9. Thus for all this get a grasp on assembly language with asm keyword. Also a must for this is dos.h, go through the help contents to learn intdosx() and intdos() functions.\n\nRemember for all this needs a good concept of DOS interrupt is needed.\n\nTo get a neat piano I designed in GUI or a few GUI DOS-based games mail me... till then happy C-ing!!
184095
when microsoft came about