4 ms·
Pretty much the same for me. FoxPro followed dBase III Plus in my case and then on to Clipper 5.x. It was delightfully easy to build fully functioning text mod
by dardeaup 1y ago
Pretty much the same for me. FoxPro followed dBase III Plus in my case and then on to Clipper 5.x.
It was delightfully easy to build fully functioning text mode applications. I especially liked the picture clauses on form reads. When I later learned about curses it was a huge disappointment. curses/ncurses with tips from the xBase world would be great for those that need to write terminal applications.
- kragen 1y agoWhat were those like? I never used any xBase. How was it different?
- dardeaup 1y agoTo display text it was as simple as: @ row, col say "First Name:" to draw a box: @ top_row, top_left to bottom_row, bottom_right there was built-in support for menus. there were commands to save the screen to variable and then restore the screen. main_screen = savescreen restscreen(main_screen) Everything was really simple. Forms were super easy. There was a command of the form: @ row, col say "First name:" get first_name @ row+1, col say "Last name:" get last_name read
- kragen 1y agoInteresting. So you put a series of commands one after the other on the same line of code with no delimiters?
- dardeaup 1y agoNo, sorry, that was me not formatting properly with my comments. Each statement would be on a separate line: @ x, y say "First name" @ col2, y get first_name @ x, y+2 say "Last name" @ col2, y+2 get last_name read
- kragen 1y agoI see. So that would generate a form that you could tab around in and enter data into?
- mercurialuser 1y agoYes. Going back to the top or confirming tha data when exiting the last field was a setting. You may have multiple commands on one row but you have to separate them with a ;